Bitcoin miners supplied the decisive signal for Taproot at block 687,284 on June 12, 2021, reaching the threshold required to lock in the network’s most substantial consensus upgrade since Segregated Witness.
The block brought the number of Taproot-signaling blocks in the relevant 2,016-block difficulty period to 1,815. That was the threshold encoded for the deployment. Pieter Wuille, a Taproot specification co-author, reported on June 12 that reaching 1,815 made lock-in guaranteed absent a very deep blockchain reorganization.
The distinction between threshold attainment, lock-in and activation matters. Taproot’s new rules did not become active at block 687,284. The threshold made the forthcoming state transition effectively inevitable under the prevailing chain, while activation remained programmed for block 709,632, then expected in November 2021.
How Speedy Trial reached its decision
Bitcoin Core 0.21.1 implemented a modified version-bits process called Speedy Trial. Miners could signal readiness through bit 2 in a block’s version field. If at least 1,815 blocks in one 2,016-block retarget period signaled before the deployment timeout, Taproot would lock in and later activate at the specified minimum height.
This was a block-based measurement window, not a poll conducted during the UTC calendar day of June 12. The 1,815 figure accumulated across the then-current difficulty period. Block 687,284 was consequential because its signal brought the running count to the required threshold; it did not represent 1,815 votes cast on June 12 alone.
Miner signaling also should not be interpreted as a shareholder vote or proof of unanimous agreement among every Bitcoin user. It indicated sufficient readiness among the miners producing blocks under the activation mechanism. Full economic enforcement would depend on node operators running software that recognized the tightened consensus rules.
Bitcoin Core therefore encouraged users, businesses and miners to upgrade before block 709,632. Older software could continue following the chain because Taproot was designed as a soft fork, but an older node would not independently apply the new rules governing version-one witness programs.
What Taproot was designed to change
Taproot joined three related specifications. BIP 340 defined Schnorr signatures for Bitcoin’s secp256k1 curve. BIP 341 defined Taproot outputs and their spending rules. BIP 342 supplied the associated Tapscript validation language.
A Taproot output can be spent through a public-key path or through a committed script path. When participants cooperate through the key path, unused alternative spending conditions need not be revealed on-chain. When a script path is required, the spender can reveal the selected condition and its authentication path instead of exposing every committed alternative.
Those properties were intended to make some complex arrangements more compact and less distinguishable from simpler payments. Schnorr signatures also created a cleaner foundation for multiparty constructions and batch-verification efficiencies.
The benefits were conditional, however. Taproot did not make every Bitcoin transaction private, reduce every user’s fee or immediately deliver new wallet features. Actual gains would depend on compatible wallets, services and higher-layer protocols adopting the new output and signature formats after activation.
Why June 12 mattered
By June 12, Taproot had moved from a debated software proposal to a consensus change with an effectively secured activation path. That transition gave exchanges, custodians, wallet developers, miners and node operators a defined implementation deadline.
It also demonstrated that Bitcoin could coordinate a backward-compatible consensus change without creating a new asset or changing its monetary schedule. The milestone established technical readiness under the chosen activation mechanism; it did not establish future usage, market demand or measurable privacy improvements.
Later confirmation
Bitcoin Optech reported on June 16, 2021, that the Taproot soft fork had locked in and reiterated that the rules would become safe to use after block 709,632. That later confirmation clarifies the completed state transition without changing what block 687,284 established on June 12.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.

