3 posts tagged with "attestation"

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.

There's a 3-second cliff in Ethereum's attestation system. Blocks that arrive after it — when validators have already started forming their head votes — cause measurable drops in head accuracy. The earlier post established that with 50,000 slots of data.

What it didn't answer: who's responsible?

I started this looking for evidence that high-MEV blocks are harder for execution clients to process. The intuition is obvious: MEV blocks are full of complex DeFi interactions, sandwich attacks, arbitrage — all the state-thrashing stuff. Surely they're heavier to execute.

They're not. The correlation between MEV block value and newPayload execution time is r = −0.004. Essentially random noise.

What actually predicts execution latency is simpler and more boring: how much gas the block used.