One beacon_api_eth_v3_validator_block observer made Ethereum payloads look four times larger than they were.

In a two-hour mainnet sample, 161 prepared blocks from that path matched the canonical execution payload for their slot. The prepared-block rows reported 213,035 transaction entries. The matching canonical blocks contained 51,254 transactions: a 4.156x multiplier.

I called 38.6% of Ethereum gas a permanent-storage bill in February. That sentence was wrong. The table was a research allocation model, not a meter attached to physical state growth, and a quarter of the SSTORE gas it put in state_growth came from transactions that added no net-new storage slot at all.

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.

Ethereum added seven BLS12-381 precompiles in Pectra. In two weeks of fresh call-frame data, five of them were never touched. The other two were called 126 times each, and every call came from the same contract.

That contract was not a staking protocol. It was a small cross-chain bridge minting Wrapped Gonka.

meta_network_name = 'mainnet' used to look like enough of a chain filter. It is not anymore.

In four complete hours after Xatu widened its execution-peer capture, node_record_execution held 3,075 peer IDs under the mainnet label. 637 of them, 20.72%, reported a genesis hash that was not Ethereum mainnet's. The sample contained 116 distinct genesis values in total.

This is not mainnet suddenly splitting into 116 chains. The label belongs to the observation path; the remote peer's genesis is a separate field.

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.

A seven-day freshness filter against Xatu's old blob_sidecar eventstream returned 598 rows. They looked recent only because their event timestamps were in 2033, 2034 and 2040. Every payload and database insertion belonged to July 3, 2025.

This is not Ethereum taking eight years to deliver a blob. Two contributor clocks briefly went feral.

I need to correct a noun I used three weeks ago. I called canonical_execution_balance_reads logical instrumentation for ETH balance reads. The count was real; the thing being counted was not.

These rows are transaction-account prestate records. They are not BALANCE opcodes, repeated balance lookups, or a gas counter.

One transaction called USDT's transfer() function 519 times and emitted 519 Transfer logs. Xatu's canonical_execution_storage_reads table kept four records for USDT's fixed control slots. That looks broken until you read the extractor: this table is a prestate set, not an SLOAD counter.

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.