Bitcoin Core vs Knots and BIP-110.

Derek Ross

npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424

hex

543d7e602bf4433bb3fb7cfa3c20b9f22e3de0ad38524b0c32d91d33c4e40cc6

nevent

nevent1qqs9g0t7vq4lgsemk0ahe73uyzulyt3auzkns5jtpsedj8fncnjqe3sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqzn565u

Kind-1 (TextNote)

2026-07-19T04:42:28Z

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.

原始 JSON

{
  "kind": 1,
  "id": "543d7e602bf4433bb3fb7cfa3c20b9f22e3de0ad38524b0c32d91d33c4e40cc6",
  "pubkey": "3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
  "created_at": 1784436148,
  "tags": [
    [
      "alt",
      "A short note: Bitcoin Core vs Knots and BIP-110.\n\nEssentially, o..."
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "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.",
  "sig": "37708d34e69f7286a13d81caebed5f65c3b87fc0460c82690e4c8b78077d6bebd26a201f9cb050814e694194e7c848e02f386b58137c3440802e5156415dddc6"
}