The naive MaxEB question is easy to ask and surprisingly easy to answer with data.

If one validator can carry 2,048 ETH, does it get one sync committee ticket or something closer to sixty-four?

The answer on mainnet is blunt: sync committees follow stake, not validator count.

A stale execution peer is not always a node that forgot the latest fork.

Sometimes it is a modern client binary sitting at the mainnet genesis block and politely telling the world it is ready for Homestead.

Across seven complete UTC days, 201 of 1,444 discovered mainnet execution node IDs advertised old fork IDs. 164 of those had the old Frontier fork ID, 0xfc64ec04, with next = 1150000.

That is not "slightly behind."

That is genesis.

PeerDAS has a tiny ENR field called cgc.

It is supposed to say how many custody groups a peer has. The boring answer would be: most peers advertise the minimum, a few advertise more, and probe results roughly follow that.

The boring answer was wrong.

A lot of Ethereum code still says SELFDESTRUCT.

That word is now a trap.

After EIP-6780, SELFDESTRUCT only deletes code and storage when the contract was created in the same transaction. Older contracts can still send their ETH balance to a beneficiary, but the account does not get wiped.

So I checked how often the opcode is still real deletion.

Attestations are not a smooth cloud of votes.

They pulse.

"Fast confirmation" sounds like something that should happen early.

On mainnet, at least in the one Xatu node emitting the new Beacon API event, it happens at 11.555 seconds into a 12-second slot.

That is fast compared with finality. It is not fast compared with the slot clock.

Correction — 17 July 2026: UNSUPPORTED was a derived RPC-snooper label for a null or non-array V2 result, not proof that an execution client lacked the method. The client/version support interpretation below is wrong. The complete successful-return counts still hold because V2 is all-or-nothing. The correction matches the same requests across the consensus and snooper captures.

The blob data is there.

The Engine API path to fetch it is not equally there.

I started with the boring version of the question: which MEV-Boost relay has share?

The data immediately refused to answer it cleanly.

I screwed up the June blob chart.

The shape was right. The unit was wrong. I divided blob gas by 786432, which is six blobs' worth of blob gas, then called the result "blobs". That means every number in the post was one-sixth of the actual blob count.

June 3 was not 6,408 blobs. It was 38,445 blobs.

June 18 looked like a new blob demand record.

It was, technically. Ethereum carried 40,822 actual blobs that day, beating June 3's 38,445.

But the record was weirdly hollow. June 18 carried 25% less useful blob payload than June 3, even with more blobs.