SegWit (Segregated Witness, BIP 141)
The main BIP for Segregated Witness, which separates witness data, fixes malleability, and effectively boosts block capacity.
SegWit (Segregated Witness) is the soft fork that activated on Bitcoin on August 24, 2017, at block 481,824, defined in BIP-141. It restructured how Bitcoin transactions store signature data, solving multiple problems at once.
The core change: signature data ("witness data") was moved out of the main transaction body into a separate structure that's still in the block but that old nodes never download, so it doesn't count against the 1 MB block-size limit they still enforce. For upgraded nodes, blocks were redefined in terms of weight units, with a maximum of 4 million weight units per block. Witness data costs 1 weight unit per byte; non-witness data costs 4. This roughly doubled capacity - to about 1.6 to 2 MB of typical transactions - without a hard fork.
What SegWit fixed:
- Transaction malleability. Pre-SegWit, the txid was computed over the full transaction including signatures, which were malleable. Third parties could change a tx's appearance (and its txid) without invalidating it. This broke unconfirmed-transaction chains and made layer-2 protocols nearly impossible to build safely. SegWit excludes witness data from the txid computation, so once every input is signed, nobody else can change the txid.
- Block capacity. The limit went from 1 MB to nearly 4 MB in the extreme case, which works out to about 1.6 to 2 MB for a typical mix of transactions.
- Future upgrades. SegWit put a version byte in front of every witness program and reserved versions 1 to 16 for future script systems, which is how Taproot was added later as a clean soft fork.
The 2017 activation was politically explosive - it came out of the multi-year block size war between people who wanted bigger raw block size and people who wanted layer-2 scaling. The bigger-block side forked off as Bitcoin Cash on August 1, 2017, three weeks before SegWit went live. The remaining Bitcoin community kept SegWit and the layered-scaling roadmap, and the Lightning Network - which depends on stable txids - could now be built on top.
Initial adoption was eased by P2SH-wrapped variants - P2SH-P2WPKH and P2SH-P2WSH - that let receivers collect SegWit benefits behind a familiar 3... address senders already knew how to handle. Native SegWit (bc1q...) came next: Bitcoin Core made bech32 its wallet default in 0.20.0 (June 2020), and the wrapped variants became a compatibility fallback.
By October 2026, more than 95% of payments spend SegWit outputs. Pre-SegWit legacy outputs still exist but are a shrinking share.
Key takeaways
- Moves witness data out of the transaction id's hash; it stays in the block
- Resolves malleability, boosts capacity
- Enables layer-2 solutions like Lightning
Related chapters
On the mailing list
BIP 141 came up in 48 threads on bitcoin-dev between January 2016 and October 2026. Read them in the archive.
The topic timeline: Segregated witness (186 threads).
Sources (6)
- BIP 141 - Segregated Witness (Consensus layer): block weight is base size * 3 + total size, capped at 4,000,000, where base size is what a non-upgraded node sees; txid stays the double SHA256 of the serialization without witness data, so nonintentional malleability becomes impossible once all inputs are signed; witness versions 1 to 16 are reserved for future extensions; fixing malleability enables trust-free chains of unconfirmed transactions
- Bitcoin Core - Segregated Witness Benefits (January 26, 2016): old nodes only download the witness-stripped block and enforce the 1 MB limit on that; segwit raises the limit to nearly 4 MB, with an effective limit closer to 1.6 to 2 MB
- mempool.space - block 481,824 (01:57 UTC, August 24, 2017), the first block under SegWit rules
- Bitcoin Cash UAHF technical specification: activation time 1501590000 (12:20 UTC, August 1, 2017); the fork block must be larger than 1,000,000 bytes
- Bitcoin Core 0.20.0 release notes (June 3, 2020): the wallet now uses bech32 addresses by default over RPC and creates native segwit change outputs
- mainnet.observer - SegWit spending payments chart (0xB10C, the open-source successor to transactionfee.info): 96.5% of payments spent SegWit outputs over the 30 days to October 13, 2026, computed from the site's date.csv, payments_sum.csv and payments_segwit_spending_tx_sum.csv
External references (5)
Related terms (13)
Published . Revised . No corrections logged for this page.
Edit this page on GitHub