A Guide to HyperEVM's Dual Block Architecture

Jul 2, 2025

HyperEVM's Dual Block Architecture
HyperEVM's Dual Block Architecture

Hyperliquid is a high-performance blockchain that separates execution into two states governed by a unified consensus. The native execution layer is called HyperCore, while HyperEVM offers EVM compatibility and is a fork of Ethereum's Cancun upgrade (without blobs). This setup enables developers to deploy Solidity smart contracts while allowing seamless interoperability with HyperCore state.

Dual Block Architecture Explained

Dual block architecture is Hyperliquid's unique solution to scaling HyperEVM state without forcing a trade-off between block speed and size. Instead of using a uniform block structure, HyperEVM produces two block types over the same timeline. This allows users to choose either speed or capacity depending on the transaction's purpose.

This approach enables:

  1. Users can get faster confirmations.

  2. Developers can deploy large, complex smart contracts

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

How Dual-Block Architecture Works

The dual block Architecture on the Hyperliquid blockchain operates by producing two distinct block types:

  1. Small Blocks: Produced every 1 second, with a gas limit of 2M. Ideal for lightweight, time-sensitive transactions.

  2. Large Blocks: Produced every 60 seconds, with a gas limit of 30M. Ideal for heavier transactions, such as smart contract deployments.

Dual Block Architecture Overview Hyperliquid

Transactions are routed into one of two on-chain mempools, depending on whether they are tagged for fast or big blocks. These blocks are uniquely generated, all under a unified sequence of HyperEVM block numbers.

To target a large block, developers can submit the following action:

{"type: "evmUserModify", "usingBigBlocks": true} This state is set at the HyperCore user level and must be unset again for future transactions to return to small block inclusion.

You may also opt to use the bigBlockGasPrice JSON-RPC method to estimate the base gas fee for the next big block.

Validator Performance in Hyperliquid

Hyperliquid blockchain validators are essential to the success of dual block architecture. They are responsible for executing and verifying both small and large blocks. For a broader look at tools supporting the Hyperliquid ecosystem, Imperator’s guide highlights some of the best platforms for tracking validator health and performance.

Strong validator performance doesn’t just support the protocol; it directly drives the scalability and reliability of Hyperliquid.

Final Thoughts on Dual Block Architecture

Hyperliquid blockchain's dual-block architecture offers a novel way to boost throughput on its EVM layer while staying anchored to the unified consensus with HyperCore. HyperEVM delivers scalability and flexibility, paving the way for a more efficient, user-friendly, builder-friendly blockchain environment.

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

FAQs

  1. What is dual block architecture in Hyperliquid?

It’s a block production model that uses two types of blocks: small and large. To improve scalability and support different transaction needs on the Hyperliquid blockchain.

  1. How is this different from other EVM-compatible chains?

Unlike traditional EVM chains with a single block type, Hyperliquid lets users choose between fast, lightweight blocks or larger blocks designed for complex transactions.

  1. Does HyperEVM support dual block Architecture?

Yes. HyperEVM is built to work with this architecture and automatically routes transactions based on whether they prioritise speed or capacity.

  1. Is HyperEVM running on a separate consensus mechanism?

No. HyperEVM and HyperCore operate under the same unified consensus: HyperBFT, which ensures a synchronised state and secure execution.

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security

From concept to connection in seconds.
Set up your RPC with ease

99.99% uptime

Ultra-low latency

Enterprise-grade security