Activation Threshold

The activation threshold is the proportion of blocks that must signal support for a proposed soft fork before it locks in and becomes enforced. It is the central tuning parameter of miner-activated deployments: set it high and you demand near-universal readiness before changing the rules; set it lower and you risk activating a change that a meaningful minority of the network has not adopted. Every consensus upgrade that has used miner signaling — from CSV to SegWit to Taproot — lived or died by whether signaling crossed this line inside its window.

The classic 95% figure

Under BIP9 version bits, signaling is measured over each 2,016-block difficulty period. On mainnet the historical threshold has been 1,916 blocks out of 2,016, which is 95%. A miner signals by setting the deployment's assigned bit in the block header version field of the blocks it produces. If enough blocks in a single retarget window carry the bit, the deployment moves from "started" to "locked in," then becomes active after one more full period — a built-in grace window that gives laggards a final chance to upgrade before the new rules are enforced. Testnet uses a relaxed 1,512 of 2,016 (75%) to make experimentation easier. If the timeout height or date passes without the threshold being met, the deployment simply fails and the bit is freed for reuse.

Why the number is political, not just technical

A high threshold protects against activating a contentious change: at 95%, a change only activates when hashpower is almost unanimously ready, which minimizes the chance that a large chunk of miners keeps building blocks that violate the new rules. But the same math hands a small slice of hashpower an effective veto — roughly 5% of blocks withheld from signaling is enough to stall a deployment indefinitely. That is precisely the dynamic that stalled SegWit through 2016–2017 and motivated the user-activated response. Later deployments experimented with the parameters: Taproot's "Speedy Trial" paired a 90% threshold with a deliberately short signaling window to force a quick yes-or-no answer, and it locked in within weeks. The choice of threshold encodes a judgment about how much consensus is "enough," and about who gets to say no.

The post-SegWit years also produced BIP8, a deployment variant that can be configured to activate at the end of its window even if signaling never reaches the threshold — converting the miner veto into a mere scheduling delay. Whether that switch should ever be flipped, and who legitimately decides, remains one of the livelier arguments in Bitcoin's activation politics. That is the deeper lesson of the parameter: threshold design is governance design, and every number encodes a theory of who Bitcoin answers to.

Signaling is readiness, not voting

A subtlety worth internalizing: version-bit signaling is formally a readiness mechanism, not a ballot. A miner setting the bit is asserting "my infrastructure will enforce these rules," so that the network can coordinate a safe activation moment. In practice the line blurs — withholding a signal is an easy way to express opposition — but the protocol's designers were explicit that economic nodes, not hashpower, are the ultimate arbiters of consensus rules. That is why the threshold debate connects directly to sovereignty: if you run your own node, an activation only binds you when your software enforces it, regardless of what percentage of hashrate signaled. Miners coordinate the timing; users define the rules.

For a home miner or a pool-pointed Bitaxe, activation thresholds are mostly invisible — your pool sets the version bits in the work it hands you. But they matter when you choose where to point your hashrate: during a contentious deployment, the pool you mine with is signaling (or not) on your behalf. The activation threshold is the linchpin of a miner-activated soft fork; when miners stall below it, the network may turn to a user-activated soft fork to force the question, as it famously did with BIP148 during the SegWit standoff. Understanding both paths is understanding who actually governs Bitcoin.