World Chain to Stream EIP-7928 Access Lists on Aug. 17

World Chain will enable streamed EIP-7928 full block access lists on its mainnet on Aug. 17. The network plans to publish access-list data every 200 milliseconds during block assembly and aims for throughput of up to 1 gigagas per second while keeping validator hardware requirements unchanged.

The upgrade embeds Block-Level Access Lists, the EIP-7928 structure that records every account and storage slot touched during block execution, into World Chain’s flashblock architecture. By publishing state reads and writes as blocks are built, validators can begin verification before a block is complete. Validators can check independent transactions in parallel across multiple CPU cores rather than re-executing every transaction in sequence.

World Chain’s implementation extends the EIP-7928 specification by emitting access-list updates every 200 milliseconds inside flashblocks. The team will enable the feature on mainnet via a runtime flag that client operators can activate ahead of a coordinated hard fork. The runtime flag allows operators to opt in on compatible client software without requiring a network-wide software upgrade at launch.

Internal testing on World Chain networks found validation latency remained stable while throughput increased, reaching one gigagas per second on standard cloud infrastructure. The tests indicate block producers could raise transaction throughput without proportionally increasing the computing power needed by independent validators.

EIP-7928 defines a consensus-verified record of state accesses for each block so clients can validate and schedule execution in parallel rather than discovering dependencies during execution. Ethereum has scheduled the specification for inclusion in the Glamsterdam upgrade; World Chain plans to deploy streamed block-level access lists on mainnet before that network-level change, making it one of the earliest production systems to run the feature at scale.

Under the streamed access-list workflow, validators receive incremental maps of the accounts and storage slots touched by transactions while a block is still under construction. Operators who flip the runtime flag will see client software start emitting and consuming these access lists as part of the consensus process. Once the network accepts the upgrade, validators and client operators can join the streamed BAL workflow and validate blocks using the predeclared access maps rather than discovering read/write dependencies during execution.