How Fee Markets Respond to Demand Spikes

Cyclical fee variation is predictable and moderate. Event-driven variation is neither, and the events have recognisable signatures.

The event types

Competitive mints. A limited supply released at a known time. Thousands of participants submit simultaneously, bidding against each other. Fees spike vertically for minutes, then collapse.

A large proportion of the transactions fail, and the failures are charged.

Liquidation cascades. A sharp price move triggers automated position closures. Liquidators compete to execute them, bidding aggressively because the reward justifies it. Duration of minutes to an hour.

Airdrop claims. A distribution opens and recipients claim simultaneously. Spike sustained for hours rather than minutes, because claiming has no deadline pressure per individual.

Exploit responses. An incident produces rushed withdrawals and defensive transactions. Sharp and short.

The shape

Event spikes rise faster than cyclical variation because they are driven by simultaneous demand rather than by aggregate activity.

They also decay quickly. The base fee falls whenever blocks are less than half full, which happens as soon as the burst of demand clears.

For most events, waiting an hour returns fees to normal levels.

What this means for an ordinary user

Do not transact during a spike. Whatever you are doing can almost certainly wait an hour.

Do not participate in competitive mints unless you have priced the expected cost including failures. The arithmetic rarely works for individuals.

Expect elevated failure rates during spikes. A transaction estimated before the spike will be underpriced during it.

Check before submitting. The whole defence is thirty seconds on a gas tracker.

Detecting one in progress

Base fee several times its recent level. Blocks consistently at maximum size. A visible cluster of pending transactions at high fee levels.

All three are visible on any explorer or mempool visualisation.

The rollup contrast

Rollup fees are largely insulated from mainnet events, since dedicated data capacity decoupled the two markets.

An event that makes mainnet transactions expensive for an hour has little effect on rollup costs, which is one of the practical arguments for keeping routine activity there.

For venue users

Withdrawals initiated during a spike may be processed at elevated network fees, depending on the venue’s model.

Platforms passing through the network cost will charge more during a spike; those with a fixed fee will not. Venues that display the network component separately, such as venues that quote the network fee separately, make it visible which model applies and whether deferring by an hour is worth it.