Spam is flooding Bitcoin with useless transactions. This clogs the network, makes fees expensive, and pushes real payments out. Spam wastes resources and harms #Bitcoin 's usefulness as money.

Spammers say "spam is subjective" and "a valid transaction is valid." But spam has clear traits: it wastes space inefficiently and exploits #Bitcoin functions in malicious ways. High fees also don't justify spam, since demand should drive fees up, not attacks.

Spammers claim #Bitcoin can thrive with greedy miners only caring about money. But miners need Bitcoin to stay useful long-term to profit. If spam ruins Bitcoin's utility as money, that hurts miners too. Letting spam dominate blocks devalues #Bitcoin.

Some say you can't fight spam, but that's false. Bitcoin users have coordinated to fight spam before. Updating filters and getting miners on board sends a message about undesirable activity.

Making payments cheaper doesn't justify spam either. Cheaper fees reduce miner income, same as spam filters. But efficiency improves network value, benefiting miners long run. Spam to push scaling changes also dangerously rushes upgrades without proper testing.

"Satoshi embedded data on-chain, so spam is allowed." But Satoshi didn't bloat or exploit #Bitcoin . Reasonable data inclusion doesn't equal endorsing spam attacks on the network. What matters is intent and responsible use of resources.

"High fees will stop spam eventually." No - spammers currently pay the highest fees. They'll keep raising budgets to clog the chain. Real demand should drive fee prices, not attacks. Relying solely on pricing spam out fails to address the root problem.

"Everything is good for #Bitcoin." Not true - #Bitcoin has flaws and vulnerabilities like any system. Attacks can impair functionality. Defenses are needed to protect network reliability and user experience. This requires proactive effort from Bitcoiners.

You can fight spam by running updated node software (i.e. #BitcoinKnots or Ordirespector) , setting policies against spammy transaction types, asking developers for better defaults and UI controls, pointing hash rate at filtered mining pools like OCEAN MINING and staying vocal about protecting #Bitcoin .

#Bitcoin once had strict anti-spam rules that got relaxed over time. Spam isn't new - previous incidents led to things like Blockchain DNS and Counterparty flooding the network. But coordinated action reined these in. With motivation, spam can be mitigated again.

For more information, check out below website

https://wtfhappenedinfeb2023.com/

cc nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub10vlhsqm4qar0g42p8g3plqyktmktd8hnprew45w638xzezgja95qapsp42 nostr:npub1au23c73cpaq2whtazjf6cdrmvam6nkd4lg928nwmgl78374kn29sq9t53j

Reply to this note

Please Login to reply.

Discussion

“Real demand should drive fee prices”

Dude there is so much cope in this post it’s unreal.

You’re either for open systems or you’re not. Clearly, you’re not.

Don’t like it? Get core devs to change the BTC architecture and everyone to run updates nodes.

Unreal.

A lot of people say “it’s a valid #bitcoin transaction” so we can’t discriminate …

I say it’s an exploit of a bug that was introduced long after satoshi left us with his original design for the monetary network.

I heard the validity argument too, just recently again. It's illogical. Every spam email is a valid email, otherwise it wouldn't exist. Spam is subjective and the overwhelming amount of people see inscriptions as such, apart from the exploit they are utilizing.

Validity in itself on some network level is not an argument. Bitcoin is an object made for humans, it would be nothing and mean nothing without us subjects. Its purpose and impact are entirely subjective, so already subjectively we can dismiss the inscription spam run by some scammers trying to extract value from gamblers who give zero fucks about the environment they are gambling in or network they are gambling on. They move to the next new thing as soon as it arrives and we never hear from them again.

Inscriptions and oridnals have nothing to do with Bitcoin.

Ultimately the people who produce something of value and sell it for Bitcoin are those who have the final say.

If they only accept UTXOs in clean blocks the problem solves itself.

As much as i might agree that inscriptions are spam and should be blocked, the reality is that there's no way to actually enforce this. Even if we used mempool filtering, inscribers would simply send their txs direct to the miners (who are happy to take the fees) or they can use obfuscation techniques like Inviscriptions ( https://conduition.io/bitcoin/inviscriptions/ ) to bypass the filtering in an endless cat & mouse game.

Simply cap the amount of arbitrary data that can be included in a transaction to a few bytes. People would still be able to inscribe (just as they could from day 1 as with satoshis original “chancellor on the brink of bailouts for banks” ) but with that change no one would be able to fill entire blocks with one or two txns. It’s just a bug from Segwit that needs to be patched.

I agree that inscribers would go out of the band and pay mining pools (not miners) to inscribe SPAM but that's what needs to happen first so, we can identify and expose those bad actors (mining pools in this case) and we could put social pressure on miners to mine with pools like Ocean.

Keep in mind that when it comes to inscribe arb data, there will always be cat and mouse game and I think node runners will have to be very adaptive when it comes to adjusting their filters.

Every software will always have some bug(s), no matter how much you optimize it so, you always have to play cat and mouse game to keep optimizing that software. Same applies to #bitcoin.

Nobody is perfect in the world (not even #bitcoin) so, it's our responsibility to do everything to protect the HEALTH of the #bitcoin network.

Moreover, this is also lesson learned that we need to be super slow when it comes to upcoming changes (or improvements) to the #bitcoin network and we need to be super diligent in identifying second order effects of changes/improvements.

Or you could use Monero. Mordinals are against privacy and so devs got rid of it to preserve the monetary use case.