Asaf Fulks on Nostr: Migrated both my nodes from Knots to Core. When I wrote the consensus change ...
Migrated both my nodes from Knots to Core.
When I wrote the consensus change checklist, I scored BIP-110 against my own 20 criteria and it didn't clear the bar. The framework is supposed to be neutral — a tool, not a verdict. But I was still running the client that's now packaged as the activation vehicle for that exact proposal.
Running BIP-110-bundled software while publishing analytical work arguing the proposal doesn't meet activation criteria is a contradiction I couldn't keep ignoring.
This isn't anti-Knots. Knots is legitimate software and the mempool policy work is real. What changed is the product — the codebase now ships activation code by default, opt-in to enable but present in the binary. My response to the package changing isn't a referendum on the client.
For anyone wondering: Core lets you configure mempool policy in bitcoin.conf. You don't need Knots to filter your own node. The defaults differ; the knobs are still there.
Migration was clean — moved chainstate between app data dirs on Umbrel, no IBD. 875G chain intact, ~15 minutes per node.
The checklist applies to me too. That's the whole point of writing one.
Published at
2026-05-17 03:21:22 UTCEvent JSON
{
"id": "e6f1d8ebb9c16ca6adf105628da438a0c9e3c7b99af703292ea637fb3bfe5bbf",
"pubkey": "16579aad0b011338505d607a73ab322ad6a426f7697c3e0e007e0625896ab92f",
"created_at": 1778988082,
"kind": 1,
"tags": [
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://offchain.pub/"
],
[
"r",
"wss://profiles.nostr1.com/"
],
[
"r",
"wss://nostr-pub.wellorder.net/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://eden.nostr.land/"
],
[
"client",
"Primal Web"
]
],
"content": "Migrated both my nodes from Knots to Core.\n\nWhen I wrote the consensus change checklist, I scored BIP-110 against my own 20 criteria and it didn't clear the bar. The framework is supposed to be neutral — a tool, not a verdict. But I was still running the client that's now packaged as the activation vehicle for that exact proposal.\n\nRunning BIP-110-bundled software while publishing analytical work arguing the proposal doesn't meet activation criteria is a contradiction I couldn't keep ignoring.\n\nThis isn't anti-Knots. Knots is legitimate software and the mempool policy work is real. What changed is the product — the codebase now ships activation code by default, opt-in to enable but present in the binary. My response to the package changing isn't a referendum on the client.\n\nFor anyone wondering: Core lets you configure mempool policy in bitcoin.conf. You don't need Knots to filter your own node. The defaults differ; the knobs are still there.\n\nMigration was clean — moved chainstate between app data dirs on Umbrel, no IBD. 875G chain intact, ~15 minutes per node.\n\nThe checklist applies to me too. That's the whole point of writing one.",
"sig": "ecaf2fd8e1c6e2526f4a7bc5b4b9efbe67dac200ffcd8d6d022876226fb1e6f12eac79e6257ed00f5ce8c519c2d551449f9712a7a6a08625803aab3c168d797e"
}
