{"type":"rich","version":"1.0","title":"Derek Ross wrote","author_name":"Derek Ross (npub18a…tp424)","author_url":"https://yabu.me/npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424","provider_name":"njump","provider_url":"https://yabu.me","html":"Bitcoin Core vs Knots and BIP-110.\n\nEssentially, 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.\n\nWith 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.\n\nBIP-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.\n\nThe distinction matters:\n\n• Core default change: Bad precedent, opt-out available → annoying but not catastrophic\n• BIP-110: Structural censorship of legitimate transactions → attack on Bitcoin's core value proposition."}