What it proposed
Activate Taproot (BIPs 340–342), which almost nobody opposed — but argue fiercely about how: BIP 8 with lockinontimeout=true, or a miner vote that could simply fail.
LOT=true · BIP 8, BIP 343 client
Make signalling mandatory at the end so miners cannot veto an upgrade users want (the lesson many drew from 2017).
VS
LOT=false / Speedy Trial · Bitcoin Core
Never force a chain split: give miners a short, 90% window and try again later if it fails.
Why it blew up
Taproot itself was uncontroversial; the activation method became a proxy fight over the lessons of the UASF.
Outcome
Bitcoin Core 0.21.1 shipped Speedy Trial (bit 2, 90%). Taproot locked in at block 687,285 (12 Jun 2021) and activated at block 709,632 (14 Nov 2021). BIP 343 was Closed on 1 June 2026, “no longer relevant”.
Timeline
- 28 Feb 2021Luke Dashjr argues LOT=false would reintroduce the miner veto of 2017. [1]
- 6 Mar 2021David Harding writes up “Speedy Trial”: 90% signalling over about three months, then fail or activate later. [1]
- 6 Mar 2021Matt Corallo doubts it keeps nodes together; Keagan McClelland says many LOT=true supporters will switch to it. [1] [2]
- Nov 2021Taproot activates at block 709,632, the min_activation_height in BIP 341. [1] [2]
In their own words
“As we saw in 2017 with BIP 9, coordinating activation by miner signal alone, despite its potential benefits, also leaves open the door to a miner veto.”
bitcoin-dev · 28 Feb 2021 · source
“Stop soon: if the lockin threshold isn't reached within approximately three months, the activation attempt fails.”
bitcoin-dev · 6 Mar 2021 · source
“My understanding of the goal of this proposal, itself, was to keep the community together by proposing a solution that was palatable to all.”
bitcoin-dev · 6 Mar 2021 · source
“The assumption of malice on the part of those of us supporting a UASF is tragic and frankly ridiculous.”
bitcoin-dev · 6 Mar 2021 · source
In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
- S15 E50: Vlad on the Speedy Trial backlash▶ listen at 38:53timestamp transcript-derived, pending a listen
- S15 E50: Murch on Taproot and inscriptions▶ listen at 53:56timestamp transcript-derived, pending a listen
- S15 E50: Murch on “Taproot caused ordinals”▶ listen at 54:45timestamp transcript-derived, pending a listen
Sources: BIP 341, “Taproot: SegWit version 1 spending rules”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 343, “Mandatory activation of taproot deployment”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 8, “Version bits with lock-in by height”, bitcoin/bips (commit a7f9132, 2026-11-17) · bitcoin-dev, Matt Corallo, “Re: Taproot activation proposal “Speedy Trial”” (6 Mar 2021), b10c mirror · bitcoin-dev, David A. Harding, “Taproot activation proposal “Speedy Trial”” (6 Mar 2021), b10c mirror · bitcoin-dev, Keagan McClelland, “Re: Taproot activation proposal “Speedy Trial”” (6 Mar 2021), b10c mirror · bitcoin-dev, Luke Dashjr, “LOT=False is dangerous and shouldn't be used” (28 Feb 2021), b10c mirror · mempool.space, block 709,632 · Bitcoin: All the Hard Forks and Soft Forks (BTCTKVR: Forks!) · Bitcoin Core 0.21.1 release notes (Taproot activation parameters) · Bitcoin Core PR #21377, “Speedy trial support for versionbits” (ajtowns; opened 6 Mar 2021, merged 15 Apr 2021)