
Segregated Witness (SegWit) is a significant technical upgrade to the Bitcoin blockchain that was officially activated in August 2017. It restructures blocks by separating transaction signatures (witness data) from transaction data, storing them in a separate data structure. This innovative design effectively solves the transaction malleability issue in the Bitcoin network, increases block capacity, optimizes network performance, and lays the foundation for second-layer scaling solutions such as the Lightning Network.
The concept of Segregated Witness was first proposed by Bitcoin Core developer Pieter Wuille in December 2015 at the Scaling Bitcoin workshop in Hong Kong. At that time, the Bitcoin network was facing serious scalability issues, with the 1MB block size limit causing transaction congestion and rising fees. Additionally, the transaction malleability vulnerability allowed transaction IDs to be modified before confirmation, hindering the development of more advanced payment channels.
Amid intense debate within the Bitcoin community about how to solve the scaling problem, SegWit was proposed as a soft fork upgrade that could increase effective block capacity without breaking consensus while also fixing transaction malleability. After approximately a year and a half of development and testing, SegWit was finally implemented through BIP (Bitcoin Improvement Proposal) 141, successfully activating in August 2017 after reaching the required threshold.
The core mechanism of SegWit involves restructuring transactions, specifically:
Data Separation - The "witness" (signatures and scripts) data is separated from the main transaction data and placed in a separate "witness" structure.
Weight Calculation Adjustment - When calculating block size, witness data is given a reduced weight of only 0.25 "weight units" per byte, while non-witness data remains at 1 unit. This allows blocks to contain more transactions, effectively increasing the block size limit to approximately 4MB.
New Address Format - A new address format (Bech32 addresses beginning with "bc1") was introduced specifically designed for SegWit transactions, providing better error detection and shorter QR codes.
Transaction ID Calculation Change - Signature data is no longer included when calculating transaction IDs (txid), thus eliminating the transaction malleability issue and ensuring transaction IDs remain unchanged after broadcast.
Technically, SegWit introduces new version rules for Bitcoin's script system, marking old format transactions with version 0 and SegWit transactions with version 1, ensuring backward compatibility so that non-upgraded nodes can still validate the blockchain.
Despite the many benefits of SegWit, its implementation faced several risks and challenges:
Adoption Rate Issues - As an optional feature, SegWit required active support from wallets and exchanges to maximize its benefits, leading to relatively slow initial adoption.
Technical Complexity - Implementing SegWit required significant modifications to wallet software, increasing the burden on developers and the potential for errors.
Community Division - The activation of SegWit caused serious divisions within the Bitcoin community, eventually leading to a blockchain fork that created Bitcoin Cash.
Security Considerations - The new script verification rules and address format required rigorous testing to prevent new vulnerabilities and security issues.
Network Transition Period - Before the complete transition to SegWit across the network, compatibility with both transaction types needed to be maintained, increasing network complexity.
Nevertheless, the successful activation of SegWit is widely considered an important milestone in Bitcoin's technical evolution, demonstrating how major upgrades to a blockchain can be implemented through a soft fork.
SegWit represents a crucial milestone in Bitcoin's technical development, solving pressing technical issues while laying groundwork for future innovations. By fixing transaction malleability, SegWit enabled second-layer scaling solutions like the Lightning Network, providing a path for Bitcoin's long-term scalability. Simultaneously, its soft fork implementation highlighted the complexities of blockchain governance and technical upgrades, as well as the challenges of reaching consensus in decentralized systems. Over time, SegWit has become widely accepted and standardized within the Bitcoin network, proving its technical value and design rationality.
Share


