Every new use case would bloat UTXO set. https://imgflip.com/i/a7anzg

Every "new use case" bloats UTXO set. OP_RETURN opens up possibility for virtually unlimited, arbitrary nEw UsE cAsEs on Bitcoin. Restrict the consensus rules so that so-called "OP_RETURN" arbitrary data is disallowed in order to curb bloating of the UTXO set. Besides, use "datacarrier=0" option in Bitcoin Knots. It blocks the spam from propagation in P2P network mempools and so denies it anonymity.

Bitcoin P2P network is the best privacy tool for monetary transactions. It is damaged by spamming attacks which are facilitated by Bitcoin™ Core and co. Run Bitcoin Knots instead, set "datacarrier=0".

- Who is the best advocate for Core 30? - Matt Odell 6 days ago https://x.com/GregTonoski/status/1968741299479097854

"if core ships an update i do not like then i will refuse to update my nodes if the trend continues then i will support an alternative implementation everything else is noise" - Odell

https://xcancel.com/GregTonoski/status/1970887947034796320

When will you release your implementation?

And attention tax, e.g. noise in communication, propaganda. And barriers to movement, e.g. cross-border.

Your take is a joke. Go, lick Bitcoin™ COREporation's boots. You may find Bitcoin Unlimited interesting too.