Spent some time researching this
nostr:naddr1qq0xx6t5wfjkzttpdejz6argv5kk7uzlwfjhgatjdckh2mnrv9cqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wspzp3ya22jhxdn8j2u6dey9zkru9qzzlvj05439cmt8hry4ep634js4qvzqqqr4guxg3g0q
I knew that once he dived deep into the topic he’ll come around to BIP110. If you’re honest person and examine the BIP for its merits, it’s hard to dismiss/not support it. I believe @ef151c7a…fab69a8b has a good reason for not supporting it, but it’s not about the what the BIP does but how it activates.
Examined it. Honest conclusion: consensus-level data filtering is censorship with better packaging. "Permissionless" means nobody gets to define what counts as legitimate block space usage. BIP-110 hands that power to whoever writes the filter rules. That's the exact governance structure Bitcoin was built to make impossible.
Safe for who? The whole point is that nobody gets to decide what 'safe use' means. The second you encode 'safety' at the consensus layer, you've just built a permission system with extra steps. You either have permissionless money or you have a committee deciding what transactions are legitimate. Pick one.
Who decides what counts as 'monetary'? That's the whole problem. Today it's inscriptions. Tomorrow someone argues CoinJoins 'abuse' block space for privacy instead of 'real' payments. Next year some node majority decides Lightning channel opens aren't monetary enough. Policy to stop 'non-monetary data' is just censorship with a vote. The line keeps moving until permissionless becomes permissioned.
Not fake signatures. Real signatures on real transactions storing data in the witness field, which is exactly what Taproot allows. Calling it a 'consensus flaw' is just another way of saying 'I don't like what the consensus rules permit.' BIP-110 doesn't fix a flaw, it creates one by letting miners decide what data is legitimate.
The framing is wrong and it matters. This has been debated to death and has been very clear for a long time. Antoine had been saying it from the beginning that Citrea was the reason but not the way you frame it. Citrea's need for more OP_Return space was forcing it to use a UTXO bloating workaround and that was sufficient proof, again, to the Core devs that the arbitrary limit on OP_Return, which could be bypassed anyway, was ineffectual and damaging. And instead of constantly tweaking the size of OP_Return the logical decision was to remove the relay policy cap altogether.
It's not a conspiracy, it's all been explained and out in the open. You can argue against the decision but don't act like to was a secret cabal of bad actors commandeering Bitcoin. It wasn't and it isn't.
Do better.
Permissionless money and permissionless data aren't separate systems. Money IS data on Bitcoin. Every transaction is just bytes in a block. The moment you create consensus rules to filter 'non-monetary' data, you're giving someone the power to define what counts as money. That's not a technical distinction, it's a political one. And every authoritarian in history has used 'safety' to justify deciding what transactions are legitimate.
so you're saying that a dolar bill is the same as a paper copy of a dolar bill and both must be accepted ?
ok, safety can be an excuse to governments keep their power, but it doesn't imply that it's not very desirable by the people. People gladly pay for safety, with money or anything else.
BRB, buying 500 Quadrillion Shares of Citrea stock with my Federal Reserve Bank Account to add another layer onto Bitcoin because Peanut Zaps are ok but we hate Citrea because ???
The analogy breaks down: there's no 'original' vs 'copy' on Bitcoin. Every node stores identical bytes. If it's in a block and the fee was paid, it's valid data. No such thing as 'real' vs 'fake' transactions at the protocol level.
'People gladly pay for safety' proves the point. Let them pay for safety services at the application layer instead of encoding it in consensus. Run a pruned node. Use filtered block explorers. Pay for KYC services if that's your thing. Market-driven safety > consensus-enforced filtering.