Section II: HyperBFT and EVM

That competitive success required custom infrastructure. The platform built HyperCore, a bespoke L1 blockchain that prioritizes performance and accessibility while making deliberate compromises around decentralization.

Consensus Layer: HyperBFT

Hyperliquid initially launched on a Tendermint-based consensus engine before migrating to HyperBFT, a custom Byzantine Fault Tolerant design optimized for trading workloads. Permissionless validators and token staking were introduced later, after the HYPE token generation event.

HyperBFT achieves finality as long as more than two-thirds of validators remain honest. The system organizes block production through deterministic leader schedules, with epochs spanning roughly 100,000 rounds, or approximately 90 minutes.

This performance comes with inherent risks in leader-based systems. If a designated leader misbehaves or goes offline, they can temporarily censor transactions until the next rotation. While validator rotation and monitoring mitigate this risk, it represents a meaningful compromise compared to leaderless consensus mechanisms.

Validator Economics

To become an active validator, each participant must self-delegate at least 10,000 HYPE tokens. Active validators earn the right to produce blocks and receive rewards based on their total delegated stake.

Validators can charge delegators a commission on earned rewards. However, to protect delegators from exploitation, commission increases are strictly limited: validators can only raise their commission if the new rate remains at or below 1%. This prevents validators from attracting large amounts of stake with low commissions, then dramatically increasing fees to take advantage of unsuspecting delegators.

One-day delegation locks and seven-day unstaking periods balance validator commitment with capital liquidity, though these parameters involve their own tensions between security and flexibility.

Execution Layer: HyperEVM

HyperEVM addresses the accessibility challenge by providing full EVM compatibility (the Ethereum Virtual Machine introduced in Chapter II), using HYPE as the native gas token. This allows existing Ethereum wallets, tools, and developer workflows to integrate seamlessly, a crucial factor for adoption.

HyperCore-HyperEVM Synergy: Dual Block Architecture

HyperEVM's power comes from how it runs alongside HyperCore under shared HyperBFT consensus, creating seamless interoperability between high-speed trading infrastructure and smart contract programmability.

HyperCore produces blocks with sub-second finality, optimized for order book operations and delivering ~200k orders per second. HyperEVM operates within the same global state but maintains its own dual block architecture: think of it like having two lanes on a highway, a fast lane with frequent small blocks every second (2M gas) for quick, lightweight interactions, and a slow lane with larger blocks roughly every minute (30M gas) for complex smart contract deployments. This separation allows optimization for both trading latency and smart contract throughput without forcing a compromise between speed and block size.

The layers coordinate sequentially. EVM contracts read HyperCore state from the previous Core block and enqueue actions that execute in subsequent Core blocks, creating a controlled, structured interaction rather than arbitrary cross-calls.

The key innovation lies in the communication mechanism between these environments. Special built-in functions expose HyperCore's native state directly to EVM contracts, providing access to perpetual positions, spot balances, vault equity, staking data, and oracle prices, all synchronized to the latest Core block. A dedicated system contract enables the write path, allowing contracts to enqueue well-defined actions: placing orders, managing positions, transferring collateral, and adjusting staking. While reads are synchronous, write actions are processed asynchronously in later Core blocks, giving HyperCore control over execution timing and risk management.

Such architecture unlocks applications impossible on traditional DEXs. Developers can build vaults that dynamically adjust perpetual positions based on real-time prices and equity thresholds, or automated strategies that respond to liquidation events and funding rate changes. All of this is done through familiar Solidity code that delegates actual trade execution and risk accounting to HyperCore.

Asset linking extends this integration to liquidity itself. Each HyperCore spot asset can be linked to an ERC-20 on HyperEVM through asset bridge contracts at special 0x200... addresses. Once linked, moving assets between Core and EVM requires no wrapped tokens or separate bridge contracts. It's just standard transfers. The same USDC or HYPE supply flows freely between Core trading and EVM DeFi without fragmentation or conversion steps.

The dual-layer architecture between HyperCore and HyperEVM has also enabled arbitrage activity around Unit-bridged assets. Arbitrageurs exploit price differences between assets on HyperCore's trading layer and their linked representations on HyperEVM, with this activity visible in on-chain analytics. This arbitrage serves an important function: it helps keep prices synchronized between the layers and provides liquidity depth, though it also highlights the complexity of maintaining price coherence across multiple execution environments.

Consider native liquid staking as an example of what this enables. Protocols like Kinetiq use these built-in read functions to track validator performance and staking state, while write functions handle delegation and rebalancing operations. When users stake HYPE through Kinetiq, the protocol stakes on HyperCore validators while issuing kHYPE tokens on HyperEVM. This is similar to how liquid staking works on Ethereum (Chapter II), where users receive tradeable tokens representing their staked position. Those tokens participate in lending markets, AMMs, and structured products while the underlying HYPE continues earning staking rewards and securing the network. This happens without the fragmentation typical of systems where liquid staking tokens exist on separate layers from the base staking mechanism.

This design represents a deliberate choice: provide full EVM tooling with privileged access to high-performance infrastructure, rather than forcing developers into unfamiliar environments. The trade-off is increased complexity and a broader attack surface. Contracts with write access can trigger real trading actions on HyperCore, requiring careful security around permission models. Hyperliquid mitigates this by constraining the system to a structured set of actions, rolling out features gradually, and strongly incentivizing audits for any contract that can enqueue Core operations.

Builder Codes: Incentivizing Front-End Development

Most crypto exchanges tightly control their interfaces, capturing all trading fees while forcing users through a single gateway. Hyperliquid takes the opposite approach: Builder Codes allow third-party developers to create custom trading platforms that earn fees from the activity they generate.

Developers attach unique identifiers to transactions routed through their interfaces. When users trade through these platforms, builders earn an additional fee of up to 0.1% on perpetual trades and 1% on spot trades, creating direct economic alignment: better interfaces generate more volume, which means more revenue. Developers compete on user experience rather than extracting rent through proprietary access.

Phantom Wallet integrated Builder Codes in July 2025, enabling native perpetual trading without leaving the wallet environment. In under six months, it's generated approximately $10 million in total revenue, with daily earnings now approaching $100,000. Rabby, MetaMask, and Axiom have followed with their own integrations. Based.one, a trading super-app built on Hyperliquid and backed by Ethena Labs, created a custom interface on the protocol's infrastructure.

The ecosystem impact has been substantial. Builder Code integrations have generated over $100 billion in additional perpetual volume, with developers collectively earning nearly $40 million. These figures demonstrate how fee-sharing can bootstrap front-end diversity without fragmenting liquidity.

By unbundling the interface layer from the protocol and creating explicit incentives for third-party development, Hyperliquid effectively crowdsources both user acquisition and interface innovation. Third-party frontends can also iterate on UX faster than the core team: several already offer private TWAPs and advanced order types unavailable on the main Hyperliquid interface. The trade-off? Reduced direct revenue capture and the risk that inferior interfaces could damage user experience. Market competition and fee-based filtering should naturally select for quality over time.

Collateral System

USDC serves as collateral on Hyperliquid. All perpetual positions use USDC as collateral, creating a unified margin system that simplifies risk management and capital efficiency. The platform has attracted nearly $6 billion in bridged USDC from Arbitrum.

In September 2025, Circle announced it would launch a native version of USDC on Hyperliquid, starting with the HyperEVM network and expanding to HyperCore later. Circle also invested in HYPE tokens, making it a direct stakeholder in the platform. This development comes shortly after Hyperliquid held a competition to select an issuer for its native USDH stablecoin, which was won by Native Markets.

The arrival of native USDC on HyperEVM has a meaningful structural implication for the Arbitrum bridge. As native USDC becomes the dominant form of collateral on HyperCore, the earlier bridged USDC from Arbitrum, which depends on a permissioned 3-of-4 validator multisig, can be gradually deprecated. Over time this reduces the system's reliance on that concentrated withdrawal mechanism and shifts the collateral base toward a more direct, Circle-backed issuance model.