SegWit, the UASF and SegWit2x
Segregated Witness as a soft fork via BIP 9 (95% of miners), then — when miners stalled — a user-activated deadline (BIP 148) and a miner-side bridge (BIP 91).
SegWit + UASF · Core developers, Shaolin Fry, many node runners
Fix malleability and add capacity by soft fork. If miners won't signal, reject their blocks from 1 August 2017 (BIP 148).
Miners and the New York Agreement
Withhold signalling as leverage; activate SegWit only as part of “SegWit2x”, with a 2 MB hard fork about 90 days later.
It put the question “who activates soft forks?” to a live test, with a chain-split threat from users (BIP 148) and a hard-fork threat from businesses and miners (SegWit2x).
BIP 91 locked in on 21 July and activated on 26 July 2017; SegWit locked in at block 479,808 (9 Aug) and activated at block 481,824 (24 Aug 2017). Bitcoin Cash split on 1 August. The 2 MB half (SegWit2x) was suspended on 8 November 2017.
- 15 Nov 2016The BIP 9 SegWit deployment (bit 1, 95% threshold) opens; it times out on 15 Nov 2017. [1]
- 25 Feb 2017shaolinfry proposes user-activated soft forks: a flag day enforced by nodes, not a miner vote. [1]
- 26 Feb 2017Jameson Lopp asks how a flag day behaves if most miners resist. [1]
- 12 Mar 2017BIP 148 is assigned: from 1 August 2017, nodes reject blocks that do not signal for SegWit. [1]
- 22 May 2017James Hilliard proposes BIP 91 — SegWit at 80% on bit 4, to meet the BIP 148 date without a split; Matt Corallo backs it. [1] [2] [3]
- 24 Aug 2017SegWit activates at block 481,824. [1]
“As such, soft forks rules are actually always enforced by the nodes, not the miners.”
bitcoin-dev · 25 Feb 2017 · source
“Secondly, miner signalling has a natural veto which allows a small percentage of hashrate to veto node activation of the upgrade for everyone.”
bitcoin-dev · 25 Feb 2017 · source
“If the flag day soft fork is activated with only a minority of hashrate support + safely opted-out hashrate, isn't it possible for the rest of miners to coordinate orphaning any soft fork compatible blocks to kill the soft fork chain?”
bitcoin-dev · 26 Feb 2017 · source
“The goal here is to minimize chain split risk and network disruption while maximizing backwards compatibility and still providing for rapid activation of segwit at the 80% threshold using bit 4.”
bitcoin-dev · 22 May 2017 · source
“Given the overwhelming support for SegWit across the ecosystem of businesses and users, this seems reasonable to me.”
bitcoin-dev · 22 May 2017 · source
- S15 E50: Murch on what the UASF did▶ listen at 1:36:12timestamp transcript-derived, pending a listen
- S15 E39: Pete Rizzo on the economic majority▶ listen at 55:49timestamp transcript-derived, pending a listen
- S16 E60: Jonathan Bier — the SegWit2x cancellation and the BCH price spike▶ listen at 2:01:14timestamp transcript-derived, pending a listen
- S17 E43: Mike Belshe on the New York Agreement▶ listen at 1:13:17timestamp transcript-derived, pending a listen
- S15 E14: Nicolas Dorier on opposing SegWit2x▶ listen at 25:42timestamp transcript-derived, pending a listen