SegWit was activated on the Bitcoin network in August 2017 after years of debate. It was a soft fork — a backward-compatible upgrade, meaning wallets that hadn’t upgraded yet could still operate on the same network. No chain split was required.
The name “Segregated Witness” sounds technical, but the idea behind it is straightforward. To understand it, you need to know one thing about how Bitcoin transactions are structured.
The problem SegWit solved
Every Bitcoin transaction contains two kinds of data. The first is the transaction data itself: who is sending bitcoin, to which address, and how much. The second is the witness data (also called the signature): the cryptographic proof that the sender actually controls the funds being spent.
Before SegWit, both types of data lived together in the same block. This created two problems.
Problem 1 — Transaction malleability: Because the signature was bundled with the transaction data, it was technically possible for someone to alter the signature (without invalidating it cryptographically) before the transaction was confirmed. This changed the transaction ID, even though the transaction itself was valid. This “malleability” bug made it very difficult to build systems that depended on knowing a transaction’s ID before it was confirmed — which is exactly what the Lightning Network needs to do.
Problem 2 — Block space efficiency: Signatures make up a significant portion of transaction data — roughly 60 percent. Packing them into the main block limited how many transactions could fit per block, pushing fees up during congested periods.
What SegWit changed
Signatures moved to a separate data structure
SegWit “segregated” the witness data (signatures) from the main transaction block into a separate extended block. Old nodes that hadn’t upgraded simply didn’t see the witness data — they still saw valid transactions. Upgraded nodes saw the full picture.
Transaction malleability fixed
With signatures removed from the main transaction data, the transaction ID is now based only on the core transaction content. It can no longer be altered before confirmation. This fixed a bug that had existed since Bitcoin’s earliest days.
Effective block capacity increased
By counting witness data differently in the block size calculation, SegWit effectively increased how much transaction data could fit in each block without raising the 1MB limit. SegWit transactions are cheaper because they are weighted differently in the fee calculation.
Lightning Network unlocked
The malleability fix was the key prerequisite for the Lightning Network. Lightning requires creating payment channels that depend on knowing transaction IDs before confirmation. Once malleability was fixed, Lightning could be built safely. SegWit and Lightning arrived in the same year, and that was not a coincidence.
How to tell if an address is SegWit
Bitcoin addresses come in different formats, and the format tells you what type of transaction structure is being used:
Bitcoin address formats
If your wallet generates bc1q or bc1p addresses, you’re using SegWit or Taproot and paying the lowest possible on-chain fees. OrangeTill supports all address formats, so customers with any wallet type can pay you regardless.
Why it matters in context
SegWit is a good example of how Bitcoin upgrades work. There was no central authority that could simply push an update and force everyone to comply. The upgrade required miners to signal support, wallets to choose to adopt it, and the community to reach broad consensus. It took years of debate and ultimately activated through a process called a soft fork — change that is backward compatible, so nobody is forced off the network. That process is slow and sometimes contentious. It is also, by design, trustworthy — no single entity controlled the outcome.
All the technical heavy lifting, handled.
OrangeTill supports SegWit, Taproot, and all current address formats automatically. You don’t need to know the difference to accept payments.
Try OrangeTill Free →