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 (the unique identifier for each transaction) was calculated from all the transaction data, including the signature. The problem: signatures could be subtly modified by third parties without invalidating them, which changed the transaction ID. This created a serious issue for any protocol that needed to reference an unconfirmed transaction by ID — if the ID changed before confirmation, the reference broke. The Lightning Network (Bitcoin’s second-layer payment system for fast, cheap off-chain payments) was directly blocked by this bug: its channel mechanics required reliably referencing unconfirmed transactions.

SegWit fixed this by segregating (separating) the witness data (the signatures and other validation information) from the transaction data used to calculate the transaction ID. The ID is now calculated from transaction data without signatures — signatures can no longer affect it. Lightning became buildable. The fee reduction came as a byproduct of a new measurement system. SegWit introduced “block weight” as the new unit, where signature data (now in the witness section) counts at one quarter of the weight of other data. This discount incentivises the adoption of SegWit transactions and allows blocks to effectively carry more transaction data — SegWit transactions are typically 40–60% cheaper than equivalent legacy transactions. SegWit activated as a soft fork (a backward-compatible upgrade where old nodes still accept new blocks) after a prolonged and politically contentious period known as the block size wars — a years-long debate about Bitcoin’s scalability path that ultimately resolved in SegWit’s favour.

🌍 The Real-World Analogy

Think of transaction malleability like a postal system where the parcel tracking number was printed on the parcel’s 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 — fixing the system so references to parcels in transit remain reliable.