SegWit, short for Segregated Witness, is one of the most important upgrades in Bitcoin’s history. Activated on the Bitcoin network in 2017, SegWit changed how certain transaction data is structured and counted when determining block capacity.
The upgrade was designed to address several limitations of the original Bitcoin transaction format, particularly transaction malleability, limited block capacity, and inefficient use of block space. It also created a more suitable foundation for technologies such as the Lightning Network.
If you are learning how Bitcoin works, understanding SegWit is important because it connects several areas of the Bitcoin ecosystem, including transaction fees, scalability, wallet addresses, transaction IDs, and second-layer payment systems.
What Is SegWit?
SegWit means Segregated Witness.
The basic idea is to separate a portion of transaction data called the witness from the transaction data that determines which Bitcoin outputs are being spent and where the new outputs are going.
In traditional Bitcoin transactions, signatures are included directly within the transaction serialization. SegWit introduced a separate witness structure for this information.
This change had several important consequences:
- It reduced the impact of transaction malleability.
- It changed how Bitcoin measures block capacity.
- It allowed witness data to receive a different weight in block calculations.
- It improved the efficiency of many Bitcoin transactions.
- It helped make payment-channel systems such as Lightning more practical.
- It introduced new transaction and address formats.
SegWit was implemented as a soft fork, meaning that the upgrade was designed to remain compatible with older Bitcoin software while introducing new consensus rules.
Why Did Bitcoin Need SegWit?
Bitcoin’s original transaction design had several limitations that became increasingly important as network usage grew.
The most important issues included:
- Transaction malleability
- Limited block capacity
- Increasing competition for block space
- Transaction fee pressure
- Difficulties building some advanced payment protocols
- Limited flexibility for future script upgrades
SegWit did not solve every Bitcoin scalability problem. Instead, it changed the transaction structure and block accounting rules in ways that improved Bitcoin’s efficiency and enabled further development.
How Does SegWit Work?
To understand SegWit, it helps to divide a Bitcoin transaction into two conceptual parts.
1. Transaction data
This includes information such as:
- Inputs
- Outputs
- Amounts
- Previous transaction references
- Other transaction fields
2. Witness data
The witness contains information required to prove that a transaction is valid, including signatures for supported SegWit transaction types.
SegWit separates this witness information from the traditional transaction structure.
Bitcoin therefore introduced two related identifiers:
- txid — the traditional transaction ID
- wtxid — the transaction identifier that includes witness data
This distinction is important because the signature information no longer affects the traditional transaction ID in the same way it did before SegWit.
How SegWit Fixes Bitcoin Transaction Malleability
One of SegWit’s most important achievements was addressing transaction malleability.
Transaction malleability refers to the ability to modify certain parts of a valid Bitcoin transaction without changing what the transaction actually does.
For example, a transaction’s signature-related data could potentially be modified in a way that caused the transaction’s txid to change while the transaction’s inputs and outputs remained effectively the same.
This created problems for applications that depended on an unconfirmed transaction’s exact transaction ID.
Bitcoin’s developer documentation describes why this becomes particularly problematic when another transaction spends an output before the original transaction has been confirmed.
Why was this a problem?
Imagine:
- Alice creates Transaction A.
- Transaction A has not yet been confirmed.
- Bob creates Transaction B that spends an output from Transaction A.
- The transaction ID of Transaction A changes because of malleability.
- Transaction B may no longer reference the transaction as expected.
This made certain types of advanced Bitcoin applications more difficult to build safely.
How SegWit helps
SegWit moves the relevant signature information into the witness structure.
As a result, for supported SegWit transactions, changes to the witness do not alter the traditional transaction ID in the same way.
This substantially reduces the transaction-malleability problem that affected the pre-SegWit transaction format.
How SegWit Improves Bitcoin Block Capacity
One common misconception is that SegWit simply increased Bitcoin’s block size from 1 MB to 4 MB.
That is not an accurate way to describe the upgrade.
SegWit changed Bitcoin’s block-capacity calculation from a simple byte-size limit to a block-weight system.
Under BIP 141, block weight is calculated as:
Block Weight = Base Size × 3 + Total Size
The maximum block weight introduced by SegWit is 4,000,000 weight units.
This allows witness data to receive a different weight from the transaction data that makes up the base block.
The practical result is that Bitcoin can fit more transaction activity into the block than would have been possible under the old 1 MB block-size rule, particularly when transactions use SegWit efficiently.
Therefore, it is better to say that SegWit increased effective block capacity through a new block-weight calculation, rather than saying that Bitcoin simply changed to 4 MB blocks.
What Is Bitcoin Block Weight?
Bitcoin block weight is a measurement introduced with SegWit.
It takes into account both:
- The transaction data without witness information
- The complete transaction data including witness information
The calculation is:
Weight = Base Size × 3 + Total Size
This gives non-witness data more weight while discounting witness data relative to the old byte-for-byte model.
For example, if a transaction contains a significant amount of witness information, that witness information contributes less to the overall weight than equivalent base transaction data.
This provides a mechanism for increasing effective transaction capacity without simply quadrupling the traditional block-size limit.
How SegWit Affects Bitcoin Transaction Fees
Bitcoin transaction fees are largely influenced by the amount of block space a transaction consumes and the level of demand for that space.
SegWit can reduce the effective weight of supported transactions because witness data receives a discount in the block-weight calculation.
That means users can potentially pay less for a SegWit transaction than they would for an equivalent transaction using an older transaction format, depending on network conditions.
However, SegWit does not guarantee low Bitcoin fees.
Actual fees depend on factors such as:
- Network congestion
- Transaction size or weight
- Fee rate
- Wallet fee estimation
- Transaction type
- Current demand for block space
So the correct way to describe SegWit’s fee benefit is that it can make supported transactions more block-space efficient, which can reduce the fee required for a given transaction when compared with an otherwise similar legacy transaction.
How SegWit Helps Bitcoin Scale
Bitcoin has a finite amount of block space.
When more users compete for that space, transaction fees can increase and confirmation times can become less predictable.
SegWit improves scalability in several ways.
More efficient use of block space
Witness data receives a lower weight than traditional transaction data.
Better transaction structure
Separating witness data creates a cleaner distinction between transaction effects and validation information.
Reduced transaction malleability
Reducing transaction malleability makes certain multi-transaction and off-chain protocols easier to construct.
Foundation for second-layer technologies
SegWit’s transaction structure helped make payment-channel systems such as Lightning more practical.
However, SegWit should not be described as a complete solution to Bitcoin’s scalability challenge. It improved Bitcoin’s base-layer efficiency and enabled additional technologies, but Bitcoin still has fundamental throughput constraints.
SegWit and the Lightning Network
The relationship between SegWit and the Lightning Network is particularly important.
Lightning is a second-layer payment system designed to allow users to conduct transactions without recording every payment directly on the Bitcoin blockchain.
For payment-channel systems, transaction malleability can create serious complications.
SegWit’s reduction of transaction malleability enabled more reliable construction of unconfirmed transaction dependency chains, which is an important building block for payment-channel protocols such as Lightning. Bitcoin’s BIP 141 explicitly identifies this relationship.
This does not mean that SegWit itself is the Lightning Network.
Instead:
SegWit is a Bitcoin protocol upgrade, while Lightning is a separate layer built on top of Bitcoin.
SegWit helped provide technical conditions that made Lightning development more practical.
SegWit Addresses: What Are They?
SegWit also introduced new ways of representing Bitcoin payment destinations.
Before SegWit, many Bitcoin users were familiar with traditional legacy addresses.
SegWit introduced native witness programs and new address formats designed to work with them.
One important address format associated with native SegWit is Bech32.
You may encounter Bitcoin addresses beginning with:
bc1
These are commonly associated with SegWit address formats.
There are also SegWit transactions wrapped inside the older P2SH structure, which helped provide compatibility during the transition to SegWit.
Common Bitcoin address categories
| Type | General description |
|---|---|
| Legacy | Older Bitcoin transaction format |
| P2SH-wrapped SegWit | SegWit functionality represented through a P2SH address |
| Native SegWit | SegWit transaction using a native witness program |
| Bech32 | Address encoding commonly used for native SegWit |
BIP 141 defines the underlying witness-program structure, while Bitcoin’s address-related BIPs define formats used to represent those programs.
If your wallet supports multiple Bitcoin address types, it is important to make sure the sender and recipient support the address format being used.
SegWit vs Legacy Bitcoin Transactions
Here is a simplified comparison:
| Feature | Legacy Bitcoin | SegWit Bitcoin |
|---|---|---|
| Witness data | Part of traditional transaction structure | Separated into witness structure |
| Transaction malleability | More exposed to certain malleability issues | Greatly reduced for supported transactions |
| Block capacity calculation | Traditional byte-size model | Block-weight model |
| Witness discount | No | Yes |
| Transaction efficiency | Generally less efficient | Generally more efficient |
| Native SegWit addresses | No | Yes |
| Bech32 addresses | No | Yes |
| Lightning foundation | More difficult | Better suited |
| Transaction IDs | Traditional txid | txid plus wtxid distinction |
The important point is that SegWit is not simply a new address format. It is a consensus-level change to Bitcoin’s transaction and block structure.
SegWit and Bitcoin Scaling Compared With Bitcoin Cash
Bitcoin’s approach to scaling has also been a major source of debate within the cryptocurrency ecosystem.
Bitcoin Cash followed a different path and increased its block-size limits rather than adopting Bitcoin’s exact scaling approach.
If you want to understand the differences between these approaches, see our detailed comparison of Bitcoin vs Bitcoin Cash:
Bitcoin vs Bitcoin Cash: Key Differences
The comparison is useful because it shows that Bitcoin and Bitcoin Cash addressed concerns around transaction capacity and fees through different protocol strategies.
Advantages of SegWit
SegWit introduced several important benefits to Bitcoin.
1. Reduced transaction malleability
SegWit significantly reduced third-party transaction malleability for supported transaction types.
2. More efficient block space
Witness data receives a different weight in Bitcoin’s block-capacity calculation.
3. Potentially lower transaction costs
More efficient transactions can require fewer fee-paying weight units than comparable legacy transactions.
4. Better foundation for Lightning
Reduced transaction malleability helped support the development of payment-channel systems.
5. New transaction formats
SegWit introduced native witness programs and new address formats.
6. Better protocol extensibility
The witness structure created additional flexibility for future Bitcoin script and transaction improvements.
Limitations of SegWit
SegWit is important, but it is not a perfect or complete solution to every Bitcoin problem.
SegWit does not eliminate fees
Bitcoin still has limited block space. During periods of high demand, fees can rise.
SegWit does not make Bitcoin infinitely scalable
The Bitcoin base layer still has throughput limitations.
Wallet support matters
Users need wallets and services that properly support the relevant SegWit transaction formats.
Not every Bitcoin transaction is SegWit
Bitcoin continues to support multiple transaction formats.
SegWit does not eliminate all forms of malleability
The upgrade significantly addressed important third-party malleability issues, but technical details vary by transaction type and witness structure. Additional Bitcoin Improvement Proposals addressed related malleability vectors.
Is SegWit Still Important in 2026?
Yes, SegWit remains an important part of understanding Bitcoin’s current transaction architecture.
The upgrade is no longer a new feature. It is part of Bitcoin’s established protocol history and is important for understanding:
- Bitcoin transaction formats
- Block weight
- Transaction fees
- Wallet address types
- Transaction IDs
- Lightning
- Bitcoin scaling
- Later Bitcoin protocol improvements
For anyone studying Bitcoin today, understanding SegWit provides useful background for understanding how Bitcoin evolved from its original transaction format toward more efficient transaction structures and second-layer systems.
SegWit and Bitcoin Security
SegWit improves important aspects of Bitcoin’s transaction architecture, but it should not be confused with a general security solution for every blockchain application.
Bitcoin users still need to understand issues such as private-key security, wallet security, phishing, malicious software, exchange risks, and broader blockchain security risks.
For a broader overview, read our guide to:
Blockchain Security Risks: What You Need to Know
Bitcoin’s consensus design also has different security considerations from smart-contract platforms. If you are interested in how blockchain applications can be evaluated for vulnerabilities, see our guide to:
Smart-Contract Security and Auditing
You can also learn about one of the major theoretical attacks on proof-of-work networks in our explanation of:
SegWit and Bitcoin Mining
SegWit also changed how miners and Bitcoin nodes deal with transaction and block data.
Mining nodes must account for block weight when constructing and validating blocks rather than relying solely on the old 1 MB block-size concept.
If you want to learn more about Bitcoin’s mining process, see our guide to:
Bitcoin Mining With a Web Browser
Mining, however, is separate from SegWit itself. SegWit changed Bitcoin’s transaction and block rules; it did not change the basic proof-of-work concept used to secure the Bitcoin network.
SegWit FAQ
What does SegWit stand for?
SegWit stands for Segregated Witness.
What problem does SegWit solve?
One of its most important goals was reducing transaction malleability. It also changed Bitcoin’s block-capacity calculation and improved transaction efficiency.
Did SegWit increase Bitcoin’s block size to 4 MB?
Not exactly.
SegWit introduced a 4,000,000-weight-unit block-weight limit and a new calculation that gives witness data a discount. It is therefore more accurate to describe SegWit as changing Bitcoin’s block-capacity model rather than simply increasing the block size to 4 MB.
Does SegWit reduce Bitcoin fees?
It can reduce the effective weight of supported transactions, potentially lowering the fee required for a transaction compared with an equivalent legacy transaction. Actual fees still depend on network demand and fee rates.
Does SegWit enable Lightning?
SegWit helped make payment-channel systems such as Lightning more practical by addressing transaction-malleability problems that affected certain off-chain transaction designs.
What is a SegWit address?
A SegWit address is an address associated with a SegWit witness program. Native SegWit addresses commonly use Bech32 encoding and often begin with bc1 on Bitcoin mainnet.
Is SegWit still used?
Yes. SegWit remains part of Bitcoin’s established transaction architecture and is important for understanding Bitcoin transactions, block weight, fees, and second-layer technologies.
Is SegWit a new cryptocurrency?
No.
SegWit is a protocol upgrade to Bitcoin, not a separate cryptocurrency.
When was SegWit activated?
SegWit was activated on Bitcoin mainnet in August 2017.
Final Thoughts
SegWit was a major change to Bitcoin’s transaction architecture.
Rather than simply increasing the traditional block-size limit, it separated witness data from the rest of the transaction and introduced a new block-weight calculation.
Its most important contributions include:
- Reducing transaction malleability
- Improving the efficiency of Bitcoin transactions
- Increasing effective block capacity
- Creating new SegWit transaction and address formats
- Improving the foundation for payment-channel systems
- Supporting the continued evolution of Bitcoin’s transaction architecture
Understanding SegWit is therefore essential for anyone who wants to understand how modern Bitcoin transactions work.
As Bitcoin continues to evolve, concepts such as transaction weight, witness data, txid, wtxid, SegWit addresses, and Lightning remain important parts of the broader Bitcoin scaling and transaction ecosystem.
One thought on “What Is SegWit? How Segregated Witness Improves Bitcoin”