Logo

nixb.org

Powered by Jekyll — Theme by AA_𒀀𒀀

20 August 2026

Mempool Policy vs. Consensus Reality: An Autopsy of BIP-110 and the Knots Split

by Andre Amorim

✍️ Human Authored — Written, researched, and edited by AA.

The events of August 2026 surrounding BIP-110 and the Bitcoin Knots RDTS chain split offer a critical case study in the sociotechnical mechanics of decentralized consensus.

What originated as an engineering effort to restrict arbitrary data payloads (such as Ordinals and Runes) escalated into an attempted network upgrade that abruptly stalled at block 961,632.

To evaluate this event objectively, we must strip away social media polemics and analyze the fundamental difference between Local Mempool Policy and Global Consensus Rules.

1. Local Policy vs. Global Consensus: The Boundary

In Bitcoin, every full node operator possesses sovereign control over their local mempool:

However, mempool policy only governs unconfirmed transactions floating across the P2P network. Once a miner includes a transaction into a block that adheres to Bitcoin’s strict consensus rules (valid signatures, valid UTXO inputs, valid Proof-of-Work), your node must either accept that block or split from the network.

BIP-110 attempted to convert what was historically a mempool filtering policy into an active consensus-invalidating rule.

2. The Mechanics of the Split: Why the Chain Stalled

BIP-110 was designed with an activation threshold requiring 55% miner signaling via version bits. In practice, miner support reached only approximately 2.53%.

Despite failing to achieve anywhere near the required signaling threshold:

  1. On August 8, 2026, at block height 961,632, nodes running Knots-RDTS began enforcing the new rules, rejecting all valid mainnet blocks that lacked upgrade signaling.
  2. This partitioned the Knots-RDTS nodes onto an isolated minority fork.
  3. Because difficulty adjustment on Bitcoin recalculates only once every 2,016 blocks (~2 weeks under normal hashrate), a chain operating with only 2.5% of total hashpower experiences extreme block intervals—hours or days per block.
  4. The minority chain produced only a handful of blocks before effectively freezing due to hashrate starvation. Major infrastructure providers subsequently deprecated the RDTS builds as un-synchronizable.

3. The Hard Fork Dilemma: Changing the Proof-of-Work

Following the chain stall, discussions among BIP-110 proponents pivoted toward proposing an intentional Hard Fork with an altered Proof-of-Work algorithm (shifting from SHA-256d to BLAKE2b).

From a scientific and systems engineering standpoint, this pivot introduces major sociotechnical trade-offs:

4. The Engineering Takeaway

The failure of BIP-110 reinforces a foundational principle of distributed systems: Consensus cannot be declared unilaterally; it is an emergent equilibrium.

Node sovereignty gives you the absolute right to validate rules locally, inspect source code, and run declarative environments. But attempts to impose restrictive consensus rules without broad ecosystem coordination inevitably isolate the minority into an unsustainable fork.

True sovereignty is found not in splitting the ledger, but in building reproducible, transparent tools, like declarative Nix environments, that empower individuals to inspect, verify, and understand the protocol from first principles.

References:

#Bitcoin #Consensus #Knots #BIP110 #Governance #HardFork
← Back to Articles