HyperEVM Dual-Block Throughput and Large-Contract Transactions

Summary

HyperEVM divides transaction throughput across two interleaved block types: small blocks produced frequently and larger blocks produced less often. This design separates confirmation speed from block capacity, aiming to let users benefit from faster confirmations while allowing builders to include more demanding transactions. The two transaction pools are distinct, even though the mempool state remains on the umbrella Layer 1 execution system.

The document gives the initial timing and gas limits for each block type, and explains that block production is tied to Layer 1 block timing. The system accepts only a limited window of upcoming nonces per address and removes transactions that remain pending beyond a stated age. To target larger blocks, a developer must enable the account-level setting through a Core action; a Core user can be established by receiving a Core asset. A separate JSON-RPC method can estimate the base fee for the next large block. These are initial parameters, described as conservative and subject to future upgrades; the document offers no trading performance analysis.

Key ideas

• HyperEVM interleaves fast, smaller blocks with slower, larger blocks to separate confirmation speed from transaction capacity.
• Each block type draws transactions from its own mempool, while block numbers increase across both types.
• The initial configuration specifies distinct durations and gas limits, with future throughput changes expected through upgrades.
• Developers must enable an account-level setting to direct transactions to large blocks and can use a dedicated fee estimate method.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.