119 posts tagged with "data"

A contract address can hold ETH before it has bytecode. That sounds like EVM trivia until a gas proposal has to decide whether deploying the code creates a new account or updates one that is already there.

Across 14 complete August days, 8,980 successful code deployments landed on addresses with a positive prestate balance. That was 1.03% of comparable creation frames, and the addresses held 5,989.950758 ETH in total before their deployment transactions began.

Eleven successful Glamsterdam contract-creation transactions did something Mainnet still treats as an ETH burn. During initcode, each new address called SELFDESTRUCT with itself as beneficiary. The address finished with no code, nonce zero and empty storage, but its 45,959–61,659 wei balance survived.

That is EIP-8246 working as designed. The stranger part is what EIP-7928 kept: 16 storage keys from accounts whose storage ended empty, including eight SSTORE writes that were erased at transaction finalization.

At first pass, Platåberget's new Gloas settlement table looks brutal. From August 21 through 30, 2,281 of 2,603 rows say DROPPED, an apparent failure rate of 87.6%.

That number is garbage as a payment rate. 2,250 of the dropped rows are the same empty shape: builder index zero, zero fee recipient, zero amount and zero weight. The observer emitted exactly one in every epoch. Filter those defaults out and the count flips: 31 of 353 nonzero pending-payment rows were dropped, or 8.8%.

The open 10-second branch of EIP-8198 says blob throughput stays unchanged per unit of wall-clock time. That is the intention. The integers refuse: the hard maximum falls from 105 to 102 blobs per minute, while the target rises from 70 to 72.

The arithmetic is small, but it changes real block packing. In the last 14 complete UTC days, 2,511 canonical Mainnet blocks carried more than the branch's proposed 17-blob cap. A shorter-slot chain gets more blocks in the same minute, so those blobs are not lost. The old block packing still has to change.

The raw block access list was boring. Besu, Erigon, Ethrex, Nethermind and Reth all returned the same 92,543 RLP bytes for one canonical Glamsterdam block, and those bytes hashed back to the header. Then I asked for decoded JSON: Reth shortened 424 fields that the API defines as exactly 32 bytes.

Ethereum has exactly three contracts whose runtime starts with 0xEF. An August 28 update to Draft EIP-8298 says as much, but the old EOF EIP that names the three attaches the nine-byte farewell to the wrong address.

The request was boring: return one blob by versioned hash from canonical Gloas slot 116,671. All 14 Lighthouse nodes answered that the block was pre-Deneb. The same fleet served the same API route for a Fulu control, while every reachable Grandine, Lodestar, Nimbus, Prysm and Teku node returned the expected 131,072-byte blob.

I asked Lighthouse for two blobs from one canonical Fulu block, listing commitment 6 before commitment 0. Every reachable Lighthouse supernode returned them as [6, 0]. That sounds like obedient filtering, but the Beacon API says the response follows the commitments in the block, so the correct order was [0, 6].

FOCIL's inclusion-list gossip limit looked precise: 8,348 bytes. It was precise for one 8,192-byte transaction, but real inclusion lists carry dozens of transactions, and SSZ adds a four-byte offset for every one. On focil-devnet-0, that mismatch made Lodestar refuse 209 of 211 local publish attempts.

Glamsterdam devnet 8 put 200,000,000 in its gas-limit schedule. Four validator-client groups signed 200M proposer preferences. Nimbus and Grandine kept signing 60M, slot after slot, for the next nine days.

The schedule worked exactly as designed. That is the awkward part.