Why it exists
BIP 141 defines Segregated Witness, or SegWit. It places unlocking witness data in a transaction structure that is committed to separately, while keeping inputs and outputs in the traditional transaction identifier. This addresses important transaction-malleability problems and introduces versioned witness programs for future upgrades.
How it works
A transaction has a txid calculated without its witness and a wtxid that includes the witness. Blocks commit to witness data through a commitment in the coinbase transaction. Witness data is still validated and recorded; it has not disappeared from Bitcoin or become private.
Block capacity is measured in weight: non-witness bytes count four units each and witness bytes one. The limit is four million weight units. Version-0 witness programs define public-key-hash and script-hash spending, with BIP 143 providing their signature-message rules. Native witness address encodings are defined separately.
A practical example
Consider a transaction whose stripped form is 100 bytes and whose additional witness serialization is 200 bytes. Its weight is 100 × 4 + 200 = 600 weight units, or 150 virtual bytes. At 10 sats per virtual byte, the illustrative fee is 1,500 sats. The transaction occupies 300 serialized bytes, showing why raw bytes and fee-estimation size are different quantities.
What to keep in mind
SegWit does not remove fees or make every transaction identifier immune to every possible change. Its malleability benefits depend on the inputs and signing conditions. Wallets must also distinguish a witness script, its address encoding and the account derivation used to find it.
Status & implementation
SegWit is an activated consensus upgrade. Bitcoin Core records implementation from 0.13.0, mainnet deployment definitions in 0.13.1, and buried activation handling since 0.19.0.
Specification status: Deployed · Sources checked 13 November 2026
