World Chain said on August 5, 2026 that it will stream EIP-7928 block access lists inside every flashblock, letting validators verify transactions in parallel while a block is still being assembled. Mainnet rollout begins August 17.
Key Takeaways
- World Chain will stream EIP-7928 block access lists inside every flashblock starting with its August 17 mainnet rollout.
- Access lists let validators check independent transactions simultaneously across multiple CPU cores, removing the sequential bottleneck.
- The network is targeting up to one gigagas per second without raising the hardware validators need to run.
- Client operators can turn the feature on with a runtime flag, so no coordinated hard fork is required first.
- Ethereum plans to adopt the same block access list standard later as part of its future Glamsterdam network upgrade.
What Happened?
World Chain, the OP Stack layer-2 network secured by Ethereum and built around World ID proof of human, is the first production layer-2 to stream EIP-7928 block access lists inside every block it produces. The feature reaches World Chain Mainnet on August 17.
A block access list is a record of the blockchain state that each transaction reads and writes. That record is what lets independent transactions be checked at the same time across multiple CPU cores. Sequential order stops being a requirement for confirming validity.
The network is aiming at throughput of up to one gigagas per second with validator hardware requirements effectively unchanged. Those two numbers moving in opposite directions is the whole claim.
Full block access lists are coming to World Chain Mainnet on August 17. This deep dive covers the protocol design, execution model, benchmarks, and why streamed access lists matter for scaling. https://t.co/HOKb0ZYVAl
— World Chain (@world_chain_) August 5, 2026
Parallel verification attacks the throughput-hardware tradeoff
Validators today re-execute every transaction in a block in order before confirming the block is valid. More transactions therefore means more sequential work per validator, and more work means a bigger machine. That loop is what quietly narrows block validation to operators who can afford to keep upgrading.
World Chain breaks the loop by removing the ordering requirement. Execution speed itself stays where it was. The implementation extends the EIP-7928 specification, streaming access list data incrementally every 200 milliseconds through the network’s flashblock architecture. Verification of a block’s first transactions starts while its last transactions are still being assembled, so validation work spreads across the block-building window.
The design choice reads as a decentralization argument more than a speed one. Throughput gains that require better validator hardware push a chain toward fewer and larger verifiers, a tradeoff most layer-2 scaling work has accepted so far. Holding hardware flat while raising gas targets is a bet that independent verification stays reachable for ordinary operators, the condition L2 scaling and validator centralization explainer usually turns on.
Shipping ahead of Ethereum’s Glamsterdam timeline
Ethereum has EIP-7928 slated for its future Glamsterdam upgrade, which arrives as a hard fork. World Chain is turning the same standard on now through a runtime flag, so client operators can upgrade individually instead of waiting for a coordinated network-wide change. Node operators who want the feature before the mainnet date can enable it, run their client against the current network, and confirm their setup behaves before the rollout takes effect.
Internal benchmarking on World Chain test networks showed validation latency staying effectively stable as throughput rose, reaching one gigagas per second on standard cloud infrastructure. The network produced those figures with its own testing, and no outside audit has confirmed them. The benchmarks establish that the verification path itself scales. They do not establish how it holds up under sustained live traffic, a competitive fee market, or a validator set that did not build the software.
Several things the announcement does not answer:
- How many client operators will enable the runtime flag before the mainnet rollout, and what happens to those who do not?
- Whether latency stays flat under adversarial or heavily contended transaction ordering rather than benchmark load?
- Whether the 200-millisecond streaming extension gets folded back into the EIP-7928 specification or stays a World Chain variant?
- How the network handles a block whose access list turns out to be incomplete or wrong?
CoinLaw’s Takeaway
The practical read here is a supply side one for verification. Blockchains have generally bought throughput with validator hardware, and every step up that curve prices out a slice of independent operators. Streaming access lists inside flashblocks attacks the cost of verifying a block, and the runtime flag delivery means the upgrade path avoids the social coordination a hard fork requires. That combination is what makes this a first.
The wider significance depends on whether the approach survives contact with production. A layer-2 running the standard in front of Ethereum’s own Glamsterdam adoption turns World Chain into a live test of specification work the broader ecosystem is still scheduling, and the extension of streaming every 200 milliseconds is a design the specification itself does not currently include. If mainnet results match the test networks, other Superchain ecosystem have a documented path to copy, and Ethereum’s own implementation gains evidence it did not have before.
