Large-balance validators have a split personality now.

The same >=1024 ETH cohort is 25.64% of active effective stake, but only 0.646% of ordinary attestation committee positions.

I had been reading the gas-limit signalling table too literally.

It shows a stubborn 30M/36M tail, even though Ethereum's block headers have been sitting around 60M gas for months. I used to describe that tail as validators still signalling old limits. That was too generous. A chunk of it looks like relay-registration fossils.

A state write is not one write.

That sounds obvious if you have stared at Merkle Patricia tries long enough. It still hits differently when you count it block by block.

Across seven complete UTC days, the median Ethereum block made 1,329 logical state writes and rewrote 6,930 MPT nodes.

About 5.26 trie nodes per logical write. Every block. Quietly.

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.