Calling BIP-110 "censorship" is acting in bad faith. Bitcoin limited OP_RETURN to 83 Bytes for more than a decade. BIP-110 limits big data spam abuse of Bitcoin, it enforces OP_RETURN to 83 Bytes again. Derek is calling Bitcoin from 2014 until 2023 censorship ... that is strange. image
Derek Ross's avatar Derek Ross
Bitcoin Core vs Knots and BIP-110. Essentially, one is a config knob you can turn back. The other removes the knob entirely and replaces it with a locked box you can't open. With Bitcoin Core's default mempool policy change, they changed the default value for transaction relay/filtering rules. I'm not a fan of that. I believe it's a dumb call, sets a bad precedent, but in the grand scheme of things, it's still just a default config value. You can change it back. Your node, your rules. Right? That's the whole point of running your own node. You choose which transactions to relay and accept. BIP-110 is fundamentally different. It's a consensus level change that would let miners censor transactions at the block level by enabling selective transaction inclusion based on policy rules baked into validation itself. It's not a simple "change the default and move on" situation that some think. It's actually enshrining censorship into the protocol's DNA. That's a MAJOR shift in thinking and functionality. The distinction matters: • Core default change: Bad precedent, opt-out available → annoying but not catastrophic • BIP-110: Structural censorship of legitimate transactions → attack on Bitcoin's core value proposition.
View quoted note →

Replies (6)