I thought the missing corner of Ethereum's storage-lifecycle table would be ordinary transaction-local scratch space. It wasn't. Across August 5-18, 166,386 contract-slot cycles started at zero, became nonzero, and returned to zero before the block ended. USDC and USDT alone made 44,355 of them.
EIP-8374 looks like bookkeeping: stop deleting warm-access entries when an inner call reverts. Across 14 complete mainnet days, that one rule would have turned at least 169,495 later account accesses from cold to warm. The funny part is where they landed. 136,127 of them, or 80.3%, were calls into the same USDC FiatTokenV2_2 implementation.
This is not a chain-wide gas miracle. The verified address-only saving is 423,737,500 gas, just 0.0139% of the gas used in the window. It does expose a real execution shape hiding behind proxy calls: an inner frame touches an implementation and reverts, then a surviving frame reaches the same implementation and pays the cold surcharge again.
Ethereum's epoch boundary has a ridiculous reorg profile. Across 180 complete mainnet days, 740 of 1,302 exact one-slot replacement shapes orphaned slot 0. The block on the other side of the boundary, slot 31, did it four times.
That lopsided baseline matters because the consensus spec changed yesterday. PR #5547 removed Fulu's epoch-boundary guard from get_proposer_head, allowing a slot 0 proposer to replace a late slot 31 head without changing who gets to propose.
My March post about Ethereum's December receipt storm contained a dead giveaway. It said all tracked receipt history weighed 55.5 GB, then put December alone at 61.4 GB. One month cannot be larger than all history. I should have stopped there.
The underlying xatu-cbt receipt models were later repaired and re-backfilled. With the same fixed dates, December now comes to 42.19 GB of logical receipt RLP, not 61.4 GB. The model sums to 1.315 TB from August 8, 2015 through March 7, 2026, not 55.5 GB, and neither number is a measurement of node disk usage.
At slot start, Ethereum's blob pool did not look ready. Roughly 1.5 seconds later, it did.
Across eight fixed mainnet observers and 14 complete UTC days, 88.83% of canonical blob cell positions had been seen when the slot began. By the time the same observer saw its first PeerDAS data column, the share was 98.71%. The missing ten percentage points mostly arrived in the small gap before the block and its data turned up.
Ethereum has a five-month block-history rule. It does not have one five-month history clock.
A new draft EIP-8383 proposes cutting the minimum block-serving range from 33,024 epochs to 8,192, or from 146.8 days to 36.4 days at today's 12-second slots. I expected the current five-month boundary to roll forward with the chain. For most Lighthouse and Prysm peers in Xatu, it did not move at all.
Teku followed Plataberget with a broken data-column gossip decoder. That sounds impossible until you remember PeerDAS has more than one way to recover data.
Across 15 continuously observed Teku nodes, not one data-column sidecar reached the gossip validator during the matched 30-minute window before the patched build arrived. The same 15 nodes submitted 114,383 sidecar messages to that validator in the window after rollout, and 83,684 passed gossip verification.
Ethereum added just under two million net storage slots on August 16. XEN Crypto was responsible for 1,464,993 of them.
That came from 5,747 transactions, only 0.31% of the day's transaction count. They used 26.3% of execution gas and left behind 73.7% of the net slot growth. Under the constants in EIP-8037, the XEN storage writes alone backcast to 149.25 billion state gas, or 69.2% of that day's 50% state-gas target at the observed block limits.
EIP-7709 came back from the dead last week. The proposal would charge BLOCKHASH for the storage reads it now represents, which sent me looking for contracts that call it hard enough to care. One SHIB airdrop did: 374 transactions into a single contract produced 149,600 calls, or 58.4% of every observed BLOCKHASH execution in a 14-day trace window.
The gas story is stranger than the count. Each airdrop read the same two ancestors 200 times, so most of the proposed storage charges would be warm. Even the cheapest all-warm backcast still pushes 327 of the 374 historical transactions past their original gas limits before their refund becomes usable.
The Gloas spec had a nasty edge: one validator could count twice toward a builder payment by sending two slashable attestations. The fix merged on August 16. Mainnet's 552 included attester-slashing proofs contain zero examples of the exact trigger.