A draft specification for Schnorr signatures was posted to the bitcoin-dev mailing list, starting a focused push toward a more efficient signature scheme than ECDSA. Schnorr would later become a key building block for Taproot, helping enable signature aggregation and other efficiency gains.
A consolidated Taproot proposal was shared on the bitcoin-dev mailing list. The concept aimed to improve privacy and efficiency by letting many complex spending conditions look like simple spends on-chain unless a more complex path is needed.
The core Taproot-related specifications were formalized as BIP340 (Schnorr signatures), BIP341 (Taproot spending rules), and BIP342 (Tapscript). This turned earlier concepts into concrete consensus-rule documents that could be reviewed, tested, and eventually deployed as a soft fork (a backward-compatible upgrade).
Taproot’s implementation was merged into the Bitcoin Core codebase. This was a major step because it moved Taproot from a design and review phase toward being something that could be shipped in releases and activated by the network.
Developers, users, and other stakeholders began regular discussions in the dedicated `##taproot-activation` IRC channel. These meetings helped narrow disagreements about how to activate Taproot safely, not whether Taproot was desirable.
A proposed activation approach called “Speedy Trial” became a focal point in community deliberation. It was designed to quickly test whether miners were ready to signal support while still leaving time for node operators and businesses to upgrade before enforcement.
Nodes began tracking miner signaling for Taproot during the first difficulty period after the configured start time. This started the real-world test of whether miners would quickly coordinate to meet the 90% threshold required for lock-in.
Bitcoin Core 0.21.1 was released with the Taproot activation logic and parameters. The release used a Speedy Trial signaling window, with Taproot set to activate at block 709,632 if miners reached the signaling threshold in time.
During Speedy Trial, miner signaling exceeded the required 90% threshold within a 2,016-block difficulty period, causing Taproot to “lock in.” Lock-in meant activation became scheduled and predictable, giving the broader ecosystem time to finish upgrading before enforcement began.
At block height 709,632, upgraded nodes began enforcing the new Taproot consensus rules. From this point on, Taproot outputs and spending paths became valid under the network’s rules, enabling Schnorr signatures and the new Tapscript behavior for applicable transactions.
After activation, attention moved from consensus changes to adoption work: wallets, custodians, and services needed to add support for Taproot addresses and spending. This stage mattered because the upgrade’s privacy and efficiency benefits depend on real usage, not just activation.
By the end of 2021, Taproot was widely treated as the completed, current-generation soft fork, combining Schnorr (BIP340), Taproot rules (BIP341), and Tapscript (BIP342). It also left a lasting process legacy: structured review plus intensive activation-method deliberation (like Speedy Trial) became a reference point for planning future Bitcoin upgrades.
Taproot proposal, community deliberation, and activation (2017–2021)