Bitcoin Network Fees Explained: What You’re Actually Paying For
Why Bitcoin fees rise and fall, how they’re calculated, and the simple habits that stop you from overpaying on every transaction.
SegWit is short for Segregated Witness, and it is one of the most important upgrades in Bitcoin’s history. It is also one of the most intimidating-sounding, which is a pity, because the core idea is genuinely simple. If you have ever noticed that Bitcoin addresses come in different formats — some starting with 1, some with 3, some with bc1 — SegWit is the reason, and understanding it will make a lot of Bitcoin’s plumbing click into place.
Let us translate the whole thing into plain English, figure out why it mattered, and see why it still affects the fee you pay on every transaction today.
First, what is a Bitcoin transaction made of?
To understand what SegWit changed, you need a rough picture of what a transaction contains. Every Bitcoin transaction has two main parts:
The instructions: who is sending what to whom — the inputs (coins being spent) and outputs (where they go).
The signatures: cryptographic proof that the sender actually had the right to spend those coins. This signature data is sometimes called the “witness,” because it witnesses (testifies to) the validity of the transaction.
Here is the thing: that signature data is big. On many transactions, the witness/signature portion takes up the majority of the space. And in Bitcoin, space is scarce — each block has a limited size, blocks come roughly every ten minutes, and when blocks are full, fees rise as people compete to get in. If you want the full picture of that competition, our explainer on Bitcoin network fees covers it well.
The simple idea at the heart of SegWit
SegWit’s insight was this: separate (segregate) the signature data (the witness) from the rest of the transaction, and account for it differently.
Before SegWit, the signature was crammed into the main transaction data, counting fully against the block’s tight size limit. SegWit moved the witness data into its own section and gave it a “discount” in how it counts toward block space. The result was that more transactions could fit into each block without literally changing the old size limit — effectively raising Bitcoin’s capacity through a clever restructuring rather than a blunt “make blocks bigger” change.
An analogy: imagine a moving truck with a strict weight limit, where the bulky packing foam counts the same as the actual furniture. SegWit is the realization that you can put the foam in a trailer that is weighed at a discount — so you fit more real furniture (transactions) per trip (block) without buying a bigger truck.
Why this lowered your fees
Because SegWit transactions use block space more efficiently — the heavy signature data gets that discount — a SegWit transaction generally costs less in fees than the equivalent old-style transaction. When you use a modern wallet with a SegWit address, you are quietly paying less than someone still using a legacy address for the same payment.
And because more transactions fit per block, the whole network has more room, which eases fee pressure for everyone during busy periods. It was a capacity increase and a fee reduction rolled into one, achieved without a contentious change to the fundamental block size limit.
The bonus: SegWit fixed a sneaky bug
SegWit also solved a long-standing technical wart called transaction malleability. In plain terms: before SegWit, it was possible for someone to slightly alter a transaction’s unique ID after it was broadcast but before it confirmed — not to steal funds, but enough to confuse software that was tracking transactions by that ID.
By moving the signature out of the part of the transaction used to calculate its ID, SegWit made that ID stable and tamper-proof. This sounds like an obscure fix, but it was the unlock for major later innovations — most importantly the Lightning Network, the instant, ultra-cheap payment layer that depends on transactions having reliable, unchangeable IDs to function. No SegWit, no practical Lightning.
Why your address starts with bc1 (or 3)
This is where SegWit becomes visible in your everyday wallet. The address format tells you whether you are using SegWit:
- Addresses starting with
1— the original “legacy” format, from before SegWit. Still valid, but uses more block space and costs more in fees. - Addresses starting with
3— a transitional format that wrapped SegWit so older wallets could still send to it. Often called “nested SegWit.” - Addresses starting with
bc1q— “native SegWit” (technical name: bech32), the most efficient widely-used format. Lowest fees of the three. - Addresses starting with
bc1p— the newest format, from the later Taproot upgrade that built on top of SegWit’s foundation.
If your wallet gives you a bc1q or bc1p address, you are enjoying SegWit’s savings automatically. We go deeper on this in our guide to Bitcoin address types, which is handy if you have ever been nervous that different-looking addresses meant something was wrong. (They do not — they are just different generations of the same system.)
How SegWit actually happened: a quick history
SegWit activated on the Bitcoin network in August 2017, and the road there was famously contentious. Bitcoin had been wrestling for years with how to handle more transactions as it grew. One camp wanted to simply increase the block size limit; another favored the more conservative, clever SegWit approach that increased capacity without a hard change to that limit.
The disagreement was heated enough that it ultimately led some participants to split off and create a separate cryptocurrency. The main Bitcoin network adopted SegWit, and history has been kind to the decision — it delivered real capacity and fee improvements and laid the groundwork for Lightning and Taproot. If the idea of the network splitting intrigues you, our explainer on Bitcoin forks tells that story in full.
Do you need to do anything?
For nearly everyone, no — SegWit is not something you turn on. Any modern, reputable wallet uses SegWit addresses by default, so you are already getting the lower fees. The only practical takeaways are:
First, if you are still using an old wallet that only generates 1-addresses, you are overpaying on fees, and migrating to a current wallet will save you money over time. Second, do not be alarmed by addresses in different formats — sending from a bc1 wallet to a 1 or 3 address works perfectly fine; the formats all interoperate.
Common questions about SegWit
Is it safe to send from a SegWit wallet to an old-style address?
Completely safe. The different address formats all belong to the same Bitcoin network and interoperate freely. A SegWit (bc1) wallet can send to a legacy (1) address and vice versa without any special steps. The format only determines the efficiency and fee profile of the sender’s own coins — it never blocks a transfer between formats. If you have ever hesitated to paste an address because it looked different from yours, you can stop worrying.
Did SegWit make Bitcoin’s blocks bigger?
Not exactly — and this nuance is the clever part. SegWit did not raise the old block-size limit in the blunt sense. Instead it introduced a new way of measuring block space (called “weight”) that gives the segregated witness data a discount. The practical effect is that blocks can carry more transaction data than before, which feels like bigger blocks, but it was achieved through restructuring rather than a simple size increase. This subtlety is exactly what made SegWit acceptable to people worried that larger blocks would make running a node harder.
Do I lose anything by using SegWit?
No. For ordinary users SegWit is pure upside: lower fees, more network capacity, and the foundation for later improvements. The only people who ever needed to be careful were the developers of wallets and exchanges who had to update their software to support the new formats — work that was completed years ago. Today, using SegWit is simply the default smart choice.
Is SegWit the same as Lightning?
No, but they are deeply connected. SegWit is a change to how Bitcoin’s base-layer transactions are structured. Lightning is a separate “layer 2” payment network built on top of Bitcoin. The link is that Lightning relies on the malleability fix that SegWit provided — without stable, unchangeable transaction IDs, the payment channels that make Lightning work would be impractical. So SegWit is best thought of as a foundation, and Lightning as one of the most important things built upon it.
Why SegWit is a good example of how Bitcoin evolves
SegWit is worth understanding not just for its own sake but because it is a perfect case study in how Bitcoin improves. The network does not have a CEO who can push out changes. Upgrades require broad agreement among the people who run the software — node operators, miners, wallet developers, and users. SegWit was deliberately designed to be a “soft fork,” meaning it was backward-compatible: nodes that did not upgrade could still participate, they simply did not get the new benefits. This conservative, opt-in style of upgrading is a feature, not a weakness. It is slow and sometimes contentious, but it is also why Bitcoin has never had a catastrophic forced change imposed on its users. SegWit shows the system working as intended: a meaningful improvement, adopted carefully, with no one left stranded.
The one-paragraph summary
SegWit, activated in 2017, restructured Bitcoin transactions by separating the bulky signature (“witness”) data and counting it at a discount. That packed more transactions into each block, which lowered fees and raised capacity without a blunt block-size increase. It also fixed a malleability bug that made the Lightning Network possible. You experience all of this every time your wallet hands you a bc1 address — cheaper, more efficient transactions, courtesy of one of Bitcoin’s most elegant upgrades. If you want to see what got built on top of it, read about the Taproot upgrade next.