Blockspace: Who Pays for Inclusion

Blockspace is the scarce capacity a blockchain sells: the right to have data permanently recorded in a block. It is not storage in the ordinary sense, because every node must keep and re-verify it forever, and it is not bandwidth, because demand is settled by a market rather than a queue. Blockspace is the single input every on-chain action consumes, and its price is the most honest measure of what a network can and cannot absorb.

Every fee you have ever paid was a bid for blockspace, whether you thought of it that way or not. Understanding who wins that bid, who is priced out, and why the market behaves badly under load explains most of the strange cost spikes users encounter.

• Blockspace is metered in weight, not transactions. A block limit constrains bytes or compute units, so cheap transactions are large transactions in disguise.
• Fees are an auction, not a price list. You bid for position in the next block; the clearing price is set by whoever else is bidding at that moment.
• Congestion is a subsidy to whoever values inclusion most. Ordinary payments lose to arbitrage, liquidations and inscription-style data writes.
• Layer-two capacity is cheaper because it compresses. Rollups buy a small slice of base-layer capacity and resell it as many cheap slots.

Blockspace is a metered resource, and the meter is not transactions

Block limits are expressed in units that approximate verification cost, not in a count of payments. That distinction drives almost every fee surprise. Two transactions can differ by a factor of ten in size while doing the same economic thing.

A plain value transfer with one input and two outputs occupies a predictable, small footprint. A contract call that touches several storage slots, or a batch settlement that writes thousands of state entries, occupies far more. When a network’s limit is measured in weight, the market is bidding on verification work, and a single large consumer can outbid hundreds of small ones.

This is why fee spikes rarely correlate with “number of users”. They correlate with a handful of actors whose marginal value per byte is high — arbitrage bots racing for a spread, liquidation keepers racing to close an undercollateralised position, or anyone writing bulk data because the chain is temporarily the cheapest append-only log available.

Who actually pays for blockspace

The payer is the party with the highest willingness to pay at the margin, and that is usually not the retail user whose transaction sits unconfirmed.

The fee auction, in plain terms

In a first-price auction, you submit a bid and hope it clears. In the fee-market designs most networks now use, a base fee adjusts block to block according to how full the previous block was, and you add a priority tip on top. The base fee rises when blocks are full and falls when they are empty. Your tip buys ordering within the block, not admission to it.

The practical consequence: during a spike, the base fee — not your tip — is what blocks you. Raising a tip on a transaction whose bid is below the base fee does nothing except waste money, because the transaction is invalid until the base fee falls or the bid rises.

Who gets priced out first

Low-value, non-urgent transfers exit the market first, and they exit silently. There is no rejection notice; the transaction simply waits. That is the intended behaviour of a fee market, and it is also a usability failure, because users interpret “pending” as “broken” rather than “outbid”.

Second to exit are applications whose unit economics assume cheap settlement — small tips, batch payouts, micro-payments. They do not disappear; they migrate to a layer two, or they move to a different chain, or they stop existing. Capacity pricing therefore shapes which applications a network can host, not just what they cost.

What one block of capacity buys

Capacity is measured in virtual bytes

The arithmetic is worth doing once, because it makes the layer-two argument concrete rather than rhetorical.

The same block at two price levels

Take a block capped near one million virtual bytes and a transfer near 140 bytes. That is roughly 7,000 transfers of capacity. If the clearing price is 10 satoshis per virtual byte, a transfer costs about 1,400 satoshis and the block collects about 9.9 million satoshis in fees. At 50 satoshis per byte, the same block collects roughly five times as much, and the effective cost per transfer rises in step. Nothing about the block changed except who could afford it.

Blockspace is not expensive because demand is high. It is expensive because supply is deliberately fixed and the queue is cleared by price rather than by waiting.

How to buy blockspace without overpaying

Treat every on-chain action as a bid you can time, size and sometimes avoid entirely.

1. Check the current base fee and the recent range over the last few hours before submitting anything non-trivial.
2. Decide whether the action is urgent. If it is not, queue it for a low-demand window rather than bidding into a spike.
3. Estimate your footprint honestly. Contract interactions cost more than the wallet preview often suggests.
4. Set a fee cap and let the transaction wait rather than chasing the market upward.
5. Batch related actions into one transaction when the protocol allows it, since overhead is paid once.
6. Move repeated, low-value activity to a layer two, and reserve base-layer capacity for settlements that need base-layer finality.
7. Record what you actually paid against what you bid, so your estimates improve instead of resetting each time.

The failure mode to watch for is fee escalation under panic. Users who bump a fee three times during a spike often pay more in total than a single well-priced transaction submitted an hour later.