119 posts tagged with "data"

Yesterday's Plataberget post stopped at 11:15 UTC with finality still pinned to epoch 1,534. I left the same 84 validator-node cohort in place and kept watching. The extra three hours made the head-count proxy look pretty bad.

At 09:05, 57 of the 84 head gauges were already at or beyond the Gloas fork slot. That is 67.86% of the nodes, but the latest complete epoch had only 45.94% of eligible stake voting for the target. Finality did not return until 13:55, four hours and 50 minutes later.

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.

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 created 587,445 contracts with non-empty runtime code in the first 14 complete days of August. 537,256 of them repeated runtime bytecode seen in an earlier block inside the same window.

That is 91.5%. The obvious culprit is the usual flood of 45-byte proxies, but those tiny contracts are only half the story. They own the address count; a few thousand large redeployments own the bytes that EIP-8058 is trying to stop charging twice.

EIP-8375 proposes two one-third burns. It burns one third of transaction priority fees in every payload, and it sets an external builder's auction target to one third of the signed gross bid. That sounds additive. It is not.

In a fixed signed-number backcast across 89,994 canonical MEV-Boost blocks, the two standalone amounts were 408.394 ETH and 326.692 ETH. Adding them gives 735.086 ETH, but the draft's actual credit rule burns 469.829 ETH. The missing 265.257 ETH is overlap, equal to 36.1% of the naive sum.

Ethereum's move from a 45 million to 60 million gas limit looked like a coordinated step from a distance. At block grain it was a fight. Across the 7,866 canonical blocks in the network-level ramp, 3,958 took the maximum legal step up and 3,714 took the maximum legal step down.

That is 97.5% of blocks pulling the limit as hard as the protocol allowed, one way or the other.

Ethereum's green receipt is a blunt answer to a messy question. Across 14 complete days, 288,119 transactions returned success even though at least one child call errored. Those transactions contained 1,225,260 failed child calls between them, or roughly one mixed result for every 115 successful transactions.

In February I described Ethereum's block timestamps as a tight but noisy clock: 12.05 seconds on average, with 0.38% of blocks supposedly arriving more than 14 seconds after the previous one. That was the wrong clock. Execution payload timestamps are protocol slot time, so consecutive canonical blocks in the fixed seven-day reconstruction are either 12 seconds apart or, when one slot has no canonical block, 24 seconds apart.

The embarrassing bit is that the old 0.38% was close to a real number. It just measured empty-slot cadence, not late block arrival.