Buy Event Ticket Consensus MIami 2026 - 20% Paris Blockchain Week - 15% OFF

What is SegWit (Segregated Witness)

SegWit (Segregated Witness) is a protocol upgrade to Bitcoin that was activated in August 2017  the most significant change to Bitcoin's transaction format since its launch. SegWit addressed Bitcoin's scalability limitations, fixed a critical security vulnerability called transaction malleability, and laid the technical groundwork for the Lightning Network.

THE PROBLEM SEGWIT SOLVED

Bitcoin's original transaction format embedded witness data (digital signatures) within the transaction data counted toward the 1MB block size limit. 

  • This created two problems: Efficiency: Signature data represents 60-65% of most Bitcoin transactions but provided no additional information that mining nodes needed for UTXO tracking. The block weight limit was effectively being consumed by data that could be handled differently. 

  • Transaction Malleability: The original transaction format allowed third parties to slightly modify the transaction's signature data (without invalidating the signature) before confirmation  changing the transaction's TXID (hash identifier). This malleability prevented reliable transaction chaining and was a prerequisite obstacle to the Lightning Network.

HOW SEGWIT WORKS

SegWit restructures transactions to separate ("segregate") witness data (signatures) from the transaction data counted in the base block weight. Witness data is stored in a separate data structure and counted at a discounted weight (1/4 of normal transaction weight) rather than full weight. Effect a SegWit block can contain significantly more transaction data than a 1MB legacy block  effectively equivalent to 1.7-2.5MB in transaction capacity.

THE TRANSACTION MALLEABILITY FIX

By moving signature data outside the transaction data that determines the TXID, SegWit made it impossible to alter the transaction ID without invalidating the signature. This fix was a prerequisite for the Lightning Network  which requires reliable transaction IDs for payment channel commitment transactions.

BECH32 ADDRESSES

SegWit introduced native SegWit addresses in Bech32 format starting with "bc1" (for example, bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq). These addresses are lower fee than legacy P2PKH (starting with 1) or P2SH-SegWit (starting with 3) addresses. Most wallets now generate native SegWit addresses by default.

Terms in addition to the SegWit (Segregated Witness)

Scroll to Top