11 posts tagged with "consensus"

Something significant happened to Ethereum four days ago, and it's largely flown under the radar.

On March 2, 2026, between roughly 10:24 and 13:00 UTC, the mainnet experienced its most severe consensus disruption since the proof-of-stake transition. Block orphan rates hit 68%. Validator participation collapsed to zero in at least one epoch. The chain stopped finalizing — not for twenty minutes like the May 2023 incident, but for close to three hours.

This is the third network incident in twelve days.

Every MEV dashboard focuses on the same number: the execution layer bid that the winning builder pays the proposer. It's tracked obsessively. Tournaments are run around it. Entire firms exist to maximise it. And for 93% of blocks proposed on mainnet right now, it's the smaller of the two income streams the proposer receives.

The other stream — the consensus layer's attestation inclusion reward — sits quietly in the background, never shown on dashboards, never cited in "MEV revenue" charts. It's roughly four and a half times larger than the median MEV-boost payment.

Every attestation Ethereum's 960,000-odd validators cast has a clock on it. The slot it belongs to ticks past, and then proposers have up to 32 slots to pick it up and include it in a block. Include it in the very next slot and the attester earns a full reward. Wait two slots and the head-vote component — about three-sevenths of the total attestation reward — is already gone.

Most people assume this is a solved problem. Look at the median inclusion delay and you'd agree: it sits at roughly 1.001 slots and barely moves. The typical attestation is included almost immediately.

The median isn't the story.

Ethereum's block orphan rate should be nearly zero. It isn't — and the reasons why are more interesting than the number itself.

Over the last 30 days, 1,783 blocks were proposed on mainnet and then lost. Not missed (nobody tried), not reverted (execution failed) — proposed, gossiped, and then quietly discarded when another block won the fork choice. That's 59 blocks per day that disappeared into the void.

Most of them arrived on time.

Every 6.4 minutes, Ethereum's consensus clients have a problem. At the boundary between epochs, they need to do expensive work — update validator balances, compute committee assignments, tick the justification/finalization machinery. While they're doing it, the network doesn't stop. Blocks keep arriving. Attesters keep committing to what they see.

What happens to validators whose client is still mid-computation when the attestation window opens? They vote for the wrong head.

Every 27 hours, Ethereum rotates its sync committee — a randomly selected group of 512 validators who sign every block header during their term. Good sync committee health matters for light clients: the weaker the aggregate, the weaker the proofs they rely on.

Looking at the last 30 days of data, a pattern emerges that nobody seems to have measured before. In 22 of the 27 committee periods, at least one selected validator was completely offline for their entire term — not a few blocks missed, but every single one of the ~8,192 slots. Dead weight drawn by lottery.

Ethereum had 660 chain reorganizations in the last 30 days. That's a 0.31% reorg rate across roughly 216,000 slots — normal background noise for a live PoS network.

But here's something nobody talks about: if you ask Lighthouse how deep those reorgs were, you'll get a completely different answer than if you ask Prysm. Same event. Same block hashes. Different depth. Every single time.

When a validator is chosen to propose a block, it has a choice: publish the moment the block is ready, or wait for MEV-Boost bids to arrive and raise the payout. Most discussions frame this as a binary — you either participate in the timing game or you don't.

The data says it's more complicated. There are three distinct groups, and the middle one has mostly gone unnoticed.

Every proposer using MEV-Boost faces the same tradeoff: wait longer to capture more value, but at some point your block arrives too late for attesters to see it before they commit their vote. The timing game is well-understood in theory. What hasn't been measured is exactly where the cliff is — and how steep the drop really is.

The cliff is at 3.0 seconds. What happens after it is sharper than you'd expect.

Analyzing 52,104 blocks over 7 days: mean interval is 12.05s, median is 12s. Only 0.38% of blocks are delayed beyond 12 seconds. The network maintains remarkably tight timing.