SegWit (Segregated Witness)

💡 The Plain-English Definition

SegWit — Segregated Witness — was a major Bitcoin protocol upgrade, activated in August 2017, that fixed a critical bug called transaction malleability, reduced effective transaction sizes to lower fees, and made the Lightning Network possible.

🤔 But Why Though?

Transaction malleability was a long-standing bug in Bitcoin’s original design. The transaction ID — each transaction’s unique identifier — was calculated from all the transaction data, including the signature. The problem was that a third party could tweak a signature slightly, without invalidating it, and thereby change the transaction ID. That broke any protocol that needed to refer to an unconfirmed transaction by its ID: if the ID changed before the transaction confirmed, the reference no longer pointed anywhere. The Lightning Network — Bitcoin’s second layer for fast, cheap off-chain payments — was directly blocked by this, because its payment channels rely on referring to unconfirmed transactions reliably.

SegWit fixed this by segregating — separating — the witness data (the signatures and other validation information) from the transaction data used to compute the transaction ID. The ID is now calculated from the transaction without its signatures, so signatures can no longer change it. With that, Lightning became buildable.

The fee reduction came as a byproduct of a new measurement. SegWit introduced “block weight” as the unit, where signature data (now in the witness section) counts as only a quarter of the weight of other data. That discount encourages people to use SegWit transactions and lets a block effectively carry more of them — SegWit transactions are typically 40–60% cheaper than equivalent legacy ones.

SegWit activated as a soft fork — a backward-compatible upgrade, where old nodes still accept the new blocks — after a long and politically bitter period known as the block size wars, a years-long argument over how Bitcoin should scale that ultimately resolved in SegWit’s favour.

🌍 The Real-World Analogy

Think of transaction malleability like a postal system where the parcel’s tracking number is printed on its wrapping paper rather than on an internal label. If someone rewrapped the parcel in transit, the tracking number changed, even though the contents were identical. SegWit moved the tracking number to an internal label that can’t be changed without invalidating the parcel — so references to parcels in transit stay reliable.