Bitcoin's BIP-110 Consensus Cleanup faces miner resistance amid quantum threat
In brief
- BIP-110 needs 55% miner support to lock in; currently at 0.89% as of July 25.
- Consensus Cleanup bundles four unpatched bugs including timewarp flaw and signature operation limits.
- Jameson Lopp opposes BIP-110, co-authored alternative BIP-361 post-quantum migration plan.
- Bitcoin Inquisition activated OP_TEMPLATEHASH on signet July 27 for covenant primitives.
- Prolonged delay risks converting known weaknesses into accumulated technical debt.
The four bugs and the timewarp threat
Consensus Cleanup combines four protocol repairs in BIP-54, a specification Antoine Poinsot and Matt Corallo completed in May. The most dangerous is the timewarp flaw. The timewarp flaw gives majority hash power a route to drive mining difficulty toward its minimum within 38 days, pulling the network into a state where blocks arrive in seconds instead of minutes.
Specially crafted blocks can take several minutes on high-end hardware and hours on weaker machines, straining node operators and risking consensus splits. The repair is straightforward: lock difficulty adjustments to the block timestamp, preventing the exploit.
Two other fixes address validation burden. BIP-54 caps signature operations per transaction, cutting the worst-case validation burden by a factor of 40. It also invalidates a 64-byte transaction form that miners have treated as nonstandard since 2019 and that Bitcoin last recorded on-chain in 2016.
The fourth repair targets a rarely exercised code path in the script interpreter. Bitcoin Inquisition has run the Consensus Cleanup rules on its experimental signet since February, allowing developers to stress-test the changes before mainnet.
Covenants, quantum, and developer division
The proposal bundles more than bug fixes. Bitcoin Inquisition activated BIP-446's OP_TEMPLATEHASH on July 27 at signet block 314,928. The opcode lets a Tapscript commit to the exact transaction that can spend an output, giving wallets and second-layer systems a covenant primitive.
This matters for vault design. A vault uses that primitive via a first transaction that announces an attempted withdrawal and creates a delay during which the owner can redirect funds or block the thief's payout. Current constructions can use presigned transactions and destroyed signing keys, an operational model that becomes fragile across large balances and long storage periods. OP_TEMPLATEHASH removes that fragility.
Yet Jameson Lopp frames the agenda differently. "Jameson Lopp has framed Consensus Cleanup, covenants, and quantum preparation as Bitcoin's next agenda." But Lopp opposes BIP-110 and co-authored BIP-361, a draft plan for post-quantum migration. The division signals that developers aren't unified on sequencing or scope.
The maintenance test
"Consensus Cleanup gives Bitcoin a maintenance test with defined faults and measurable remedies, allowing approval to demonstrate that the network can process defensive protocol work through ordinary review." That framing matters. Approval would show that Bitcoin can fix known bugs through standard governance, not ad-hoc patches or contentious forks.
Miner hesitation (0.89% support) suggests the economic incentives aren't aligned yet. Miners don't directly benefit from bug fixes or quantum prep. They benefit from transaction volume and fee revenue. Cleanup offers neither.
"Prolonged delay would convert known weaknesses into accumulated technical debt." The window closes if support doesn't reach 55% in the current 2,016-block period. After that, BIP-110 enters mandatory signaling, where miners must actively reject it—a higher bar than passive non-support.
Bitcoin's next move turns on whether developers can convince miners that defensive maintenance is worth their hash power. The clock is running.
