What is SegWit? An introduction to Bitcoin's clever on-chain scaling approach

When Satoshi Nakamoto designed Bitcoin, he established a fundamental constraint: each block should not exceed one million bytes in capacity. While this limitation was sufficient during Bitcoin's early days when it served a niche market, the growing popularity of Bitcoin created significant network congestion. The Bitcoin network generates a new block approximately every ten minutes, and due to the one-million-byte capacity limit, each block can contain only a limited number of transactions—typically no more than a few dozen. This translates to an average processing rate of seven transactions per second. During periods of high network activity, tens of thousands of transactions can accumulate in the backlog, causing transaction fees to surge to tens of dollars and processing times to extend to several days. The cryptocurrency community urgently needed an efficient technical solution to address these challenges, enabling faster transaction processing and lower fees for users. This solution emerged in the form of Segregated Witness, commonly known as SegWit.

Introducing SegWit

Segregated Witness (SegWit) technology was proposed in 2015 by Bitcoin developer Pieter Wuille along with other Bitcoin Core contributors as a comprehensive solution to Bitcoin's transaction processing speed limitations. The technology was officially implemented through a soft fork on the Bitcoin network in 2017, successfully increasing the information processing capacity of a single Bitcoin block by 1.7 times. This represented a significant milestone in Bitcoin's evolution without requiring a contentious hard fork that would split the network.

The adoption of SegWit has spread beyond Bitcoin to other major cryptocurrencies, including Litecoin and Bitcoin Cash. The implementation of SegWit brings three primary benefits to these networks: expanded block capacity, increased transaction speed, and optimized transaction scalability. These improvements have made SegWit an essential component of modern blockchain infrastructure, demonstrating the power of innovative solutions to address scalability challenges while maintaining backward compatibility with existing systems.

The technical principles of SegWit

To understand SegWit's innovation, it's essential to examine the structure of Bitcoin transaction information. Every Bitcoin transaction consists of two distinct components: basic transaction data and witness data. The transaction data records critical information such as account balances and transfer amounts, while the witness data contains signature information that verifies the user's identity and authorization to spend the funds.

From a practical standpoint, users primarily care about the core asset-related information, such as account balances and transaction amounts. The identity verification data, while necessary for security, doesn't need to occupy premium space within the transaction structure. In simple terms, the recipient of a transfer only needs to confirm that the assets are available and properly authorized; they don't necessarily need immediate access to detailed signature information from the sender.

However, in Bitcoin's original transaction structure, the witness data—particularly signature information—occupies a substantial amount of storage space, accounting for up to 65% of a transaction block's capacity. This inefficient use of space directly impacts transfer efficiency and increases packaging costs for miners. SegWit addresses this issue through an elegant solution: it extracts the witness data from the transaction information and stores it separately in a different structure. This separation allows the network to process more transactions within the same block size limit, effectively increasing throughput without changing the fundamental one-megabyte block size constraint. By segregating witness data, SegWit optimizes the use of available block space, significantly improving transaction speed and reducing costs.

The main advantages of SegWit

SegWit delivers several significant advantages that have transformed Bitcoin's operational efficiency. The first major benefit is increased block capacity. Statistical analysis reveals that signature information can occupy up to 65% of the space in a Bitcoin transaction block. By implementing SegWit, this previously occupied storage space is effectively released, allowing blocks to process substantially more transaction information. This optimization means that while the nominal block size limit remains at one megabyte, the effective capacity for transaction data increases significantly.

The second advantage is a faster transaction rate, which operates on principles similar to Ethereum's layer-2 scaling solutions. Bitcoin data is processed in layers to achieve higher transaction throughput. After adopting SegWit, the Bitcoin transaction system can concentrate more computing power and larger storage capacity on processing actual transaction information. With the burden of signature data reduced, the network's transactions per second (TPS) rate increases substantially. Data demonstrates that after adopting SegWit, the average cost per transaction has been significantly reduced, making Bitcoin more practical for everyday transactions.

The third significant advantage relates to Bitcoin's Lightning Network compatibility. The Lightning Network represents a widely discussed Bitcoin layer-2 protocol expansion solution, designed to solve scalability problems through off-chain processing. The Lightning Network creates an additional layer of network infrastructure on top of the Bitcoin blockchain, establishing payment channels that enable quick and smooth completion of large transfer transactions even under extreme circumstances. While the Lightning Network handles off-chain data processing, SegWit efficiently processes the highest-priority data on-chain, creating a complementary relationship that relieves pressure on the main blockchain and indirectly facilitates Lightning Network implementation.

An additional security benefit emerges from SegWit's technical framework: transaction data and signature data are completely separated throughout the entire transaction processing system. Since the user's signature data is excluded from the transaction identifier calculation, the possibility of transaction malleability—where transaction information could be tampered with before confirmation—is eliminated. This improvement ensures that incorrect information cannot be permanently recorded on-chain and provides positive benefits for the expansion and application of transaction information repair programs. Furthermore, SegWit laid the groundwork for Bitcoin ordinals by expanding the limit on arbitrary data that can be placed in a transaction. When combined with the 2021 Taproot upgrade, which created systems for easier storage of arbitrary witness data and further expanded data limits, these improvements enabled the creation of Bitcoin ordinals and non-fungible tokens inscribed on individual satoshis.

How SegWit is applied

For ordinary users, SegWit technology provides three main practical benefits. First, it offers enhanced safety through higher security compared to traditional addresses. Second, it enables faster transactions through expandable block capacity and quicker transaction verification. Third, it reduces costs, with transaction fees significantly lower than those associated with ordinary wallet addresses. These benefits translate into tangible improvements in the user experience when conducting Bitcoin transactions.

The application of SegWit technology for ordinary users is straightforward: by using a SegWit-compatible wallet address to receive Bitcoin transfers, users automatically enjoy all the benefits described above. Historical data has shown that Bitcoin's SegWit utilization rate has consistently increased over time, and current adoption rates continue to rise, demonstrating widespread acceptance of this technology.

Bitcoin address formats are currently divided into four main types, each with distinct characteristics. The Legacy (P2PKH) format, with addresses starting with "1," represents Bitcoin's original address format, which remains in use today. P2PKH stands for Pay To PubKey Hash, meaning payment to a public key hash. An example of this format is: 1Fh7ajXabJBpZPZw8bjD3QU4CuQ3pRty9u.

The Nested (P2SH) format, with addresses starting with "3," serves as a multi-signature address format. P2SH stands for Pay-to-Script-Hash, which uses redemption scripts and redemption script hashes for Bitcoin transaction inputs and outputs. Its address structure is similar to P2PKH, but it supports more complex functions than traditional addresses. P2SH script functions are most commonly used with multi-signature addresses, which can specify multiple digital signatures to authorize transactions. For example, an address starting with "3" might be controlled by three people, requiring any two of them to agree before initiating a transfer. An example of this format is: 3EktnHQD7RiAE6uzMj2ZifT9YgRrkSgzQX.

The Nested SegWit (P2SH) format, also with addresses starting with "3," represents a SegWit-compatible address. Because it uses the P2SH packaging method, the SegWit-compatible address also starts with "3," making it recognizable by older nodes that haven't upgraded to full SegWit support. An example is: 3KF9nXowQ4asSGxRRzeiTpDjMuwM2nypAN. Users don't need to distinguish whether an address starting with "3" is a multi-signature address or a SegWit-compatible address; they only need to know that addresses starting with "3" are widely supported and can send Bitcoin to addresses starting with "1" and "bc1."

The Native SegWit (Bech32) format, with addresses starting with "bc1," represents the native SegWit address format. Bech32-encoded addresses were specifically developed for SegWit and defined in BIP173 at the end of 2017. One of the main features of this format is case insensitivity—addresses contain only numbers 0-9 and lowercase letters a-z—which effectively avoids confusion and improves readability during input. An example is: bc1qf3uwcxaz779nxedw0wry89v9cjh9w2xylnmqc3.

The Bech32 format uses Base32 encoding instead of the traditional Base58, requiring fewer characters in the address and making calculations more convenient and efficient. Data can also be stored more compactly in QR codes. Bech32 provides higher security through better-optimized checksum error detection codes, minimizing the chance of invalid addresses. Since Bech32 addresses are natively compatible with SegWit, no additional space is required to embed SegWit addresses into P2SH addresses, resulting in lower transaction fees. Native SegWit addresses offer several advantages over older Base58 addresses, including smaller QR codes, better error detection, enhanced security, and case insensitivity. The exclusive use of lowercase letters makes them easier to read and understand when typing.

Native P2WPKH and Native P2WSH addresses, both starting with "bc1q," represent version 0 native SegWit addresses. For P2WPKH (Pay-to-Witness-Public-Key-Hash) addresses, the length is fixed at 42 characters, as shown in this example: bc1qmgjswfb6eXcmuJgLxvMxAo1tth2QCyyPYt8shz. For P2WSH (Pay-to-Witness-Script-Hash) addresses, the length is fixed at 62 characters, as demonstrated by: bc1q09zjqeetautmyzrxn9d2pu5c5glv6zcmj3qx5axrltslu90p88pqykxdv4wj. P2WPKH is typically used for ordinary addresses, while P2WSH is commonly used for multi-signature addresses.

In 2019, a potential issue with Bech32 addresses was discovered: if the last character of a Bech32 address is "p," and one or more "q" characters are accidentally entered afterward, the address can still pass checksum verification without triggering an input error prompt. This could potentially allow Bitcoins to be sent to an incorrect address, making them unspendable. Fortunately, since Bech32 is only used for native SegWit addresses, which have strict length limits of either 20 or 32 bytes, typing extra characters would exceed these length limits, causing the wallet to recognize the problem and refuse to send the transaction.

To address this Bech32 limitation, a new standard called Bech32m was proposed and documented in BIP0350. Bech32m implements a simple but effective change: an extra digit is added to the Bech32 checksum formula to ensure that any additional characters will generate an invalid checksum. This new standard applies only to Taproot addresses and future address formats, while existing native SegWit addresses continue to use the original Bech32 format, as they're already protected by their 20 or 32-byte length limits.

The P2TR (Bech32m) format, with addresses starting with "bc1p," represents Taproot addresses used for version 1 native SegWit implementations. An example is: bc1pqs7w62shf5ee3qz5jaywle85jmg8suehwhOawnqxevre9k7zvqdz2mOn. For version 0 native SegWit addresses, the previous Bech32 format continues to be used, while native SegWit addresses with version 1 or higher utilize the new Bech32m format. Taproot addresses, which always start with "bc1p," support advanced features including BTC NFT holding and Ordinals NFT functionality.

The subtle differences between addresses

When examining the practical differences between various address formats, several important distinctions emerge regarding transaction fees and functionality. SegWit-compatible addresses beginning with "3" offer approximately 24% savings in transfer fees compared to traditional addresses starting with "1." Native SegWit addresses beginning with "bc1" provide even greater savings, reducing transfer fees by approximately 35% compared to traditional addresses starting with "1."

The most significant fee savings occur when comparing native SegWit addresses (those starting with "bc1" and certain addresses starting with "3") to multi-signature addresses (which also start with "3"). In this comparison, native SegWit addresses can save up to 70% on transfer fees, representing a substantial cost reduction for users who conduct frequent transactions. Taproot addresses, which support BTC NFT holding and Ordinals NFT functionality, maintain transfer fees similar to addresses beginning with "3," making them cost-effective for users interested in Bitcoin's expanding ecosystem of digital collectibles and tokens.

These fee differences reflect the varying amounts of block space required by different address types. Traditional addresses require more space due to their inefficient data structure, while native SegWit addresses optimize space usage by segregating witness data. The substantial fee savings offered by native SegWit addresses make them the preferred choice for users who prioritize cost-effectiveness, while Taproot addresses offer additional functionality for users interested in advanced Bitcoin features without significantly increasing costs.

Conclusion

Segregated Witness represents a pivotal development in Bitcoin's evolution, successfully addressing critical scalability challenges while maintaining backward compatibility with the existing network. By separating witness data from transaction data, SegWit effectively increases the number of transactions that can be processed per block, reduces transaction fees, and improves overall network efficiency. The technology has achieved widespread adoption, with utilization rates continuing to grow as more users recognize its benefits.

SegWit's importance extends beyond immediate scalability improvements. It addresses the rare but significant exploit related to transaction malleability, enhancing the security and reliability of Bitcoin transactions. Furthermore, SegWit adds greater programmability to Bitcoin, creating the foundation for additional scaling solutions such as the Lightning Network and enabling innovations like Bitcoin ordinals and NFTs through subsequent upgrades like Taproot.

For ordinary users, SegWit delivers tangible benefits in three key areas: enhanced safety through improved security mechanisms, faster transaction processing through optimized block capacity utilization, and reduced costs through lower transaction fees. The variety of SegWit-compatible address formats—from Nested SegWit addresses starting with "3" to native SegWit addresses starting with "bc1" and Taproot addresses starting with "bc1p"—provides users with options that balance compatibility, efficiency, and advanced functionality.

Modern cryptocurrency wallets and major trading platforms have fully integrated SegWit support across multiple cryptocurrencies including Bitcoin, Litecoin, and Bitcoin Cash. These implementations optimize user experience, reduce usage fees, and increase transfer speeds. The comprehensive support for Taproot addresses further enables users to participate in Bitcoin's expanding ecosystem of ordinals, BRC-20 tokens, and NFTs. As Bitcoin continues to evolve, SegWit stands as a testament to the community's ability to implement significant improvements through consensus-driven soft forks, demonstrating that innovative solutions can address scalability challenges without compromising the network's fundamental principles of decentralization and security. The adoption of native SegWit addresses in particular represents a crucial step forward in Bitcoin's ongoing development, offering users the optimal combination of efficiency, security, and cost-effectiveness for their cryptocurrency transactions.

FAQ

What is a native SegWit?

Native SegWit is an advanced Bitcoin address format using 'bech32'. It optimizes the SegWit protocol, reducing fees and improving transaction speed.

Can I send Bitcoin to Native SegWit?

Yes, you can send Bitcoin to a Native SegWit address. Use your wallet to transfer from your current account to a new SegWit address. Always verify the address before sending.

Is BTC SegWit the same as Bitcoin?

No, BTC SegWit is not the same as Bitcoin. It's an upgraded address format for Bitcoin, offering lower transaction fees and improved scalability.

Is native SegWit good?

Yes, native SegWit is good. It offers cheaper transactions, improved efficiency, and wide support. It's ideal for peer-to-peer transfers and remains a solid choice for Bitcoin users.