Ethereum Pectra Hard Fork’s blob capacity enhancement operates within analyst forecasts, Ethpandaops said: May 30th Report.
The update, launched on May 7th via Ethereum Improvement Proposal 7691 (EIP-7691), doubled the default blob count from 3 to 6 and raised the ceiling from 6 to 9.. Blobs are data works contained in the Ethereum block.
This report calculated 123 beacon chain nodes in 27 countries, 29 control data centers, and 94 in residential environments to track “new head” events. This is the timestamp that is recorded when the client declares a block and the chunk declares a hint for a new chain.
In the benchmark, 66% of the peers are required to reach a new head within 4 seconds. Or the risk of blocking becomes an orphan.
Work as expected from home users
The chart covering 50,025 slots through May 28th shows that it accepts locally built solo staker blocks at under 99.5% in under 4 seconds, with only a handful of outliers.
Block size and arrival time regression is a project in which the home node can withstand up to 14 blobs before brushing a deadline well above the 9 blob cap.
The report concluded that “home users were able to support nine blobs,” and examined pre-fork modeling, which assumes bandwidth sensitivity at the network edge.
The report then stress-tested the model against the worst block size of 60 million gas, reflecting the lower limit of Pectra.
The same regression has resulted in a safe capacity trimmed into 10 chunks, leaving a narrow margin, clearing the live 6/9 envelope.
The report increases until the peer-to-peer data availability sampling (Peerdas) ship increases with subsequent releases of Fusaka, with a higher gas cap tightening the window further, strengthening community calls and halting future gas restrictions.
Manageable relay timing
Approximately 91% of the main chain block routes through the MeV boost relay and inserts a bid concept round trip between the proposer and the builder.
The relay source block recorded a slightly slower new head, with home nodes recording 97.1% within 4 seconds and 99.5% on locally built blocks.
The distribution plot attributes tails to relays that delay header broadcasts as part of the competitive timing strategy. The worst 60 million GAS simulation shows the safe relay capacity of five blobs, but Ethpandaops expects relays to be adjusted if a competitive landscape is punished for slow delivery.
Furthermore, dEvelopers will move from proponents’ Blob propagation to Peerdas under Fusaka Hard Fork.
Ethpandaops said the team is “heads down” to the Peerdas integration. This reduces the bandwidth per block and opens the room for higher gas limits and greater blob counts when deployed.
The report concluded that Pectra’s first week telemetry indicates a designed 6/9 BLOB schedule function. There is room for client teams to focus on upgrading Fusaka’s data availability without immediately putting any immediate pressure on the bandwidth ceiling.