<oembed><type>rich</type><version>1.0</version><title>Derek Ross wrote</title><author_name>Derek Ross (npub18a…tp424)</author_name><author_url>https://yabu.me/npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Bitcoin Core vs Knots and BIP-110.&#xA;&#xA;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&#39;t open.&#xA;&#xA;With Bitcoin Core&#39;s default mempool policy change, they changed the default value for transaction relay/filtering rules. I&#39;m not a fan of that. I believe it&#39;s a dumb call, sets a bad precedent, but in the grand scheme of things, it&#39;s still just a default config value. You can change it back. Your node, your rules. Right? That&#39;s the whole point of running your own node. You choose which transactions to relay and accept.&#xA;&#xA;BIP-110 is fundamentally different. It&#39;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&#39;s not a simple &#34;change the default and move on&#34; situation that some think. It&#39;s actually enshrining censorship into the protocol&#39;s DNA. That&#39;s a MAJOR shift in thinking and functionality.&#xA;&#xA;The distinction matters:&#xA;&#xA;• Core default change: Bad precedent, opt-out available → annoying but not catastrophic&#xA;• BIP-110: Structural censorship of legitimate transactions → attack on Bitcoin&#39;s core value proposition.</html></oembed>