Your L2 bridge has timed out three blocks in a row. The spinner is spinning. Somewhere in the background, fees are being burned, validators are collecting tips, and those two things are happening on entirely separate tracks, for entirely different amounts, with no connection between them whatsoever.
That separation is the whole story. Blob transactions, introduced under EIP-4844, split the fee economy in a way that directly changes how validators account for rewards during congestion. The burn happens on one track. The validator reward happens on another. During a spike, those tracks diverge in ways that matter for anyone trying to model validator economics seriously.
Two Fee Markets Living in the Same Block
Before EIP-4844, Ethereum had one fee market: execution gas, governed by EIP-1559's base fee mechanism. Every transaction competed for the same scarce resource, gas, and the base fee burned. Validators collected only the priority fee, the tip.
Blobs added a second, parallel market. Blobs carry data that rollups post to Ethereum for data availability (meaning: proof that the underlying transaction data exists and can be reconstructed, without executing any of it on-chain). They're pruned after roughly 18 days. Because they consume a different resource, they get their own base fee, their own target (currently 3 blobs per block, max 6), and their own EIP-1559-style adjustment curve.
So a single Ethereum block now has two base fees. The execution base fee, denominated in gwei per gas unit. The blob base fee, denominated in gwei per blob. Both are burned. Neither goes to the validator.
The validator's cut comes exclusively from priority fees: the execution tip on regular transactions, and the blob transaction tip attached to any blob-carrying transaction. Two burn mechanisms, one tip pool. That's the whole ledger.
What the Adjustment Curves Actually Do Under Pressure
This is where a lot of commentary goes wrong by treating the two markets as symmetric. They aren't.
The execution base fee adjusts by up to 12.5% per block depending on whether the block was above or below the 15-million-gas target. The blob base fee uses the same percentage-adjustment logic but against a target of 3 blobs per block. Same math, very different pressure dynamics.
Imagine a sudden wave of Optimism and Arbitrum batches hitting simultaneously: 5 or 6 blobs in every block for 20 consecutive blocks. The blob base fee doubles roughly every 8 full blocks at maximum utilisation (12.5% compounding). After 20 full blocks, you're looking at a blob base fee more than 11x its starting value. It compounds like interest on a loan you didn't know you were taking out.
Now consider two validators, call them Priya and Marcus, who each propose blocks during that 20-block window. Priya's block lands at block 5, when the blob base fee has risen only modestly. Marcus proposes block 18, when the fee has compounded substantially. Both validators see every wei of their respective blob base fees burned, not credited. What they each actually receive depends entirely on how much tip the rollup operators attached, which is usually a small, relatively static value because rollup operators optimise for cost, not generosity.
During the steepest part of a blob congestion spike, total ETH burned per block rises sharply, but validator revenue from blob activity barely moves. Priya and Marcus both earn roughly the same tip income. The protocol burns dramatically more. Their reward accounting looks flat against a backdrop of accelerating deflation.
The Validator's Actual Ledger During a Spike
Let's build this out with real numbers.
Suppose before the spike, the blob base fee sits at 1 wei per byte of blob data. Blobs are 128 KB each, so 131,072 bytes, meaning 131,072 wei per blob at that base fee. Three blobs per block, all burned: 393,216 wei burned per block from blobs alone. Validators collect, say, a 100,000 wei tip per blob transaction on top.
At peak congestion, 6 blobs per block for 20 blocks, the blob base fee has compounded to roughly 11x: about 11 wei per byte, or 1.44 million wei per blob. Six blobs: 8.6 million wei burned per block. Validator tips? Still roughly 600,000 wei (6 blobs times the same modest tip per blob). The burn has grown 22x. Validator blob-related income has grown 6x.
The gap between what the protocol destroys and what validators earn widens as congestion deepens. That's not a bug. It's the architecture. But it means validators watching their reward dashboards during an L2 congestion event will see something that looks underwhelming relative to the economic activity occurring.
The execution fee market, running in parallel, may be doing something entirely different. If the blob spike doesn't crowd out execution block space (and it largely doesn't, since blobs live outside the execution gas limit), execution base fees follow their own trajectory. A validator could be earning healthy execution tips while the blob burn accelerates independently.
The Honest Caveat: Tips Are Not Guaranteed to Stay Small
Everything above assumes rollup operators tip minimally. That's the typical behaviour, and it's rational: operators run sophisticated cost models and set tips just high enough to get included.
During severe, prolonged congestion, that calculus can shift. If blob space is genuinely scarce across multiple consecutive blocks and an operator needs to post a batch urgently (to settle withdrawals, for instance), they may bid up the tip substantially. Validators capture more revenue, and the picture changes.
Still, blob tips are thin and deliberate in a way execution tips aren't. Rollup operators are fewer in number, more sophisticated, and more cost-sensitive than average retail users. Sudden tip spikes happen, but they're episodic. Don't model them as structural.
One more thing worth separating out: attestation rewards and sync committee rewards exist entirely outside this fee discussion. Validators earn those regardless of fee market conditions. A validator's total income is base issuance plus tips. The fee burn affects the ETH supply and the net issuance rate, but it doesn't reduce the base staking yield directly.
Why This Matters for Net Issuance Modelling
Ethereum's post-merge monetary policy is often described as potentially deflationary: if enough ETH burns from base fees, net issuance goes negative. Blobs add a second burn lever that activates specifically when L2 activity is high.
Here's the uncomfortable implication that most issuance models underweight: the conditions most likely to drive blob fee burns, a thriving rollup ecosystem, high L2 transaction volume, are also conditions that don't proportionally enrich validators. More economic activity on rollups means more ETH burned, but validator rewards from that activity scale only with tip behaviour, not with the base fee itself.
Some analysts read this as a tension: validators secure the network, but the monetary benefit of L2 activity accrues to all ETH holders via supply reduction rather than specifically to validators. Others argue that's precisely the design intent, aligning validator incentives with Ethereum's security budget (issuance) rather than with L2 business cycles. I think the second reading is right, and the first confuses a feature for a flaw. The separation is deliberate, traced directly to EIP-1559's original logic extended into the blob domain.
Reading Your Validator Dashboard Correctly
If you're running a validator and watching your reward breakdown during an L2 congestion event, you're winning if your execution tips are healthy and your attestation rewards are clean. The blob burn column on a block explorer isn't your income. It's the protocol's income, in the form of supply destroyed.
The number to track for validator economics is priority fee revenue, broken down by execution tips and blob tips separately. During congestion, those two can diverge sharply from the burn figures, and conflating them produces badly wrong intuitions about profitability. Ask yourself: when was the last time you saw a validator dashboard that made this distinction clearly? Most don't.
The blob fee market is still young. Its tip dynamics will evolve as rollup operators compete harder with each other and as the blob target gets adjusted through future upgrades. But the structural relationship, burns go to the protocol, tips go to validators, with no crossover, is baked into the EIP-4844 design.
That separation is Ethereum's clearest statement about what it thinks validators are for. They're paid to secure the chain, not to clip coupons every time an L2 gets busy.