I got the February compounding-validator withdrawal post wrong. The 12:00 UTC batch was real: 42 withdrawals carrying 56,827.19 ETH. But those were not the first giant automatic payouts above the 2,048 ETH cap. They were full validator exits, and 99.11% of the day's corrected 58,177.93 ETH was deposited principal.
The slashing proof for the April 2023 mev-boost relay exploit did not land in the next block, or even the next hour. It was included 4,474 slots later: 14 hours, 54 minutes, and 48 seconds. Every other canonical proposer-slashing proof on Ethereum landed one or two slots after the conflicting header.
canonical_beacon_block_attester_slashing stores two attesting-index arrays for every proof. Summing those arrays across mainnet gives 245,290 validator-index positions. The protocol intersected them into 555 overlap positions, covering 554 unique validators. The arrays are evidence, not a validator-slashing counter.
canonical_beacon_validators looks like the obvious table to count validators. It is, but only after you pick one epoch. If you skip that step, you can manufacture half a billion validator rows in a day.
The name is the trap. beacon_api_eth_v3_validator_block has a slot, an execution block number, gas used, transaction count, blob gas, and payload values. It looks like a block table.
It is not a block table in the canonical sense. Across two complete UTC days, I joined Xatu's raw /eth/v3/validator/blocks/{slot} rows to the eventual canonical block for the same slot. Only 82 of 195,448 joined rows matched the canonical execution payload shape. In 14,312 of 14,341 canonical slots, not one observed v3 row matched the payload that actually landed on chain.
A voluntary exit has an epoch field, and it is very tempting to read that as "the epoch this validator exited." That is wrong in exactly the way that produces fake history. In the last 31 complete UTC days, 75.4% of mainnet voluntary exits carried an epoch more than 30 days old, or epoch 0.
The exit happened when the message landed in a canonical block. The message epoch was just the point from which the signature became valid.
The biggest validators are not the weird ones this time.
I expected the MaxEB performance chart to be boring: larger effective-balance validators are mostly run by serious operators, so they should miss less and vote cleaner. That was true for the 1024-2048 ETH bucket. It had the best liveness in the sample.
Then the bucket below it fell off a cliff.
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.
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.