We literally can’t. If BIP110 were implemented, the technique shown by the Bitmex Research article would still work. And there is no limit to similar techniques for any other bit of Bitcoin data structures. The more restrictions placed, the more insidious the data injection techniques will become. And the more difficult it will be to build needed layer 2 & 3 technologies on Bitcoin.

It is not FUD to say that arbitrary changes to data limits and relay policies are likely to break L2/3 technologies. Lookup “Lightning network ephemeral anchors” for a pertinent example.

Reply to this note

Please Login to reply.

Discussion

Thats complete BS.

First of all Bitcoin is not "data". Bitcoin is P2P ecash - Freedom Money.

Second, BIP110 will contain the major issues with spam. If we reduce it with 90%, that will still be good.

Third, there are other solutions to contain spam.

Is “P2P ecash” made of wood? Glass? No, it is made of bits of data. Fundamentally, the Bitcoin blockchain is data. It represents financial transactions, contracts, identity, and unfortunately, spam.

Being made of data, there is no way to police what every bit of data represents at a macro level, in the external world. Proof of this is here, if you care about the truth.

https://www.bitmex.com/blog/the-unstoppable-jpg-in-private-keys

wrong, there is a way

https://bip110.org/

There is also a Cat that chases spam using the spammers own rules.

BIPS are discussed/assessed here:

https://github.com/bitcoin/bips