Fee Rate Escalation
A surge in transaction fees due to heavy mempool congestion, leading to bidding wars for block space.
Fee rate escalation is what happens when demand for block space exceeds supply. The mempool fills with unconfirmed transactions; miners pick the highest-fee-per-vbyte; everyone bids up to get in.
Bitcoin produces one block roughly every 10 minutes, with a ceiling of 4 million weight units per block. That ceiling is fixed by consensus and doesn't expand under load. In the year to October 2026, blocks averaged about 1.6 MB of transaction data. When transaction submission rate exceeds the rate of block production, the mempool grows, and the fee floor to confirm in the next block (or the next few blocks) climbs.
Historical fee spikes:
- December 2017: at the peak, the median fee rate in some blocks passed 1,400 sat/vB (block 500,521 on December 22).
- April 2021: median fee rates in some blocks came close to 300 sat/vB (block 679,911 on April 20).
- 2023 and 2024, the Ordinals era: the first inscription went into a block on December 14, 2022, and the ord software updated its inscription guide for mainnet in January 2023. Inscriptions then competed with payments for block space. On May 8, 2023, block 788,763 carried 2,494 inscriptions among its 4,293 transactions, and its median fee rate was about 683 sat/vB.
- April 2024 Runes launch: the Runes token protocol switched on at block 840,000, the same block as the halving. Two blocks later the median fee rate in mined blocks passed 500 sat/vB and stayed above it for nearly 11 hours straight.
What you can do during fee escalation:
- Wait. Fee escalation is usually self-correcting. As fees climb, people whose payments can wait hold off, and the backlog eventually clears.
- Use Lightning. Off-chain payments aren't bidding for the same block space.
- Use Replace-by-Fee to bump a stuck transaction.
- Batch. Multiple recipients in one transaction amortize the fee overhead.
- Use Taproot. Schnorr signatures and key-path Taproot spends are slightly smaller than ECDSA-based equivalents.
The base layer prioritizing fees over throughput is a feature. It's what makes Bitcoin's block size cap politically tractable and gives Lightning room to be the actual high-volume payment rail.
Key takeaways
- Occurs during sudden transaction surges or mempool spikes
- Encourages users to delay low-priority transactions or use LN
- Bidding wars can push fees to very high levels briefly
Related chapters
Corrected
-
Was: The entry put the April 2024 fee spike down to the halving, saying fees rose as miners' subsidy income dropped.
Now: The spike came from the launch of the Runes token protocol, which switched on at block 840,000, the same block as the halving. Two blocks later the median fee rate in mined blocks passed 500 sat/vB, and it stayed above that for nearly 11 hours straight. Details
Sources (14)
- Bitcoin Core 31 - chainparams.cpp (mainnet target block spacing 10 * 60 seconds)
- BIP 141 - Segregated Witness (block weight must be at most 4,000,000)
- mempool.space - block sizes and weights chart (blocks averaged 1.58 MB over the year to October 10, 2026)
- mempool.space - block 500,521 (December 22, 2017), median fee rate about 1,403 sat/vB
- mempool.space - block 679,911 (April 20, 2021), median fee rate about 297 sat/vB
- ordinals.com - inscription 0, the first inscription (block 767,430, December 14, 2022)
- ord pull request 1342 - Update inscriptions guide for mainnet (merged January 23, 2023)
- ordinals.com - block 788,763 (May 8, 2023): 2,494 inscriptions among 4,293 transactions
- mempool.space - block 788,763 (May 8, 2023), median fee rate about 683 sat/vB
- BIP 340 - Schnorr signatures (a fixed 64-byte format, against DER-encoded ECDSA signatures of up to 72 bytes)
- BIP 341 - Taproot (a key path spend needs only one witness element, the signature)
- Ordinals docs - Runes specification (activates on block 840,000)
- mempool.space - block 840,002, first block over 500 sat/vB median after the April 20, 2024 halving
- mempool.space - block 840,064 (11:00 UTC April 20, 2024), last of the run over 500 sat/vB
Related terms (11)
Published . Revised . One correction logged for this page.
Edit this page on GitHub