{"type":"rich","version":"1.0","title":"Asaf Fulks wrote","author_name":"Asaf Fulks (npub1ze…4n8ys)","author_url":"https://nostr.now/npub1zete4tgtqyfns5zavpa882ej9tt2gfhhd97rursq0crztzt2hyhsk4n8ys","provider_name":"njump","provider_url":"https://nostr.now","html":"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."}