Kinetiq has launched Elysium on public mainnet, bringing a dedicated Layer 2 execution environment to the Hyperliquid ecosystem. According to Arbitrum’s official announcement, Elysium is the first dedicated blockchain built with the Arbitrum Platform to settle on HyperEVM, Hyperliquid’s EVM-compatible smart-contract environment. The network went live November 9 and uses HYPE as its native gas asset.
Elysium is designed to move application execution away from HyperEVM’s constrained blockspace while keeping settlement inside the broader Hyperliquid stack. HYPE can move between HyperEVM and Elysium on a 1:1 basis without a wrapped representation, while supported ERC-20 assets can bridge between the environments. The architecture adds dedicated execution capacity rather than replacing HyperEVM or HyperCore.
Elysium Targets Trading-Heavy Applications
Kinetiq configured the network around 100-millisecond block times and a target execution capacity of 300 million gas per second. The chain uses Arbitrum AnyTrust for data availability, with full-data posting to HyperEVM as a fallback, and Conduit operates its infrastructure. The 300 Mgas/s figure is a capacity target, not evidence of sustained production throughput or end-to-end settlement speed. Arbitrum explicitly distinguishes block frequency and execution capacity from final settlement performance.
The launch already includes several pieces of application and infrastructure support. Uniswap Protocol functionality is available from day one, while Alchemy, Arbitrum and Conduit are named launch partners. Fomo and Pump.fun also announced Elysium trading support around the November 9 mainnet activation. Those integrations establish usable trading infrastructure at launch, but they do not by themselves demonstrate durable liquidity, user activity or application adoption.
Elysium enters an ecosystem where Hyperliquid has already expanded beyond its original perpetuals market. HyperCore has added products such as HIP-4 outcome contracts, while portfolio-margin infrastructure has supported increasingly complex cross-asset trading strategies. Elysium extends that model by giving developers separate blockspace for applications that need frequent execution without placing the same load directly on HyperEVM.
HyperCore Hooks Remain a Post-Launch Upgrade
One of Elysium’s more significant features is not yet active. Kinetiq plans an ArbOS upgrade roughly four weeks after mainnet that would give smart contracts native read and write access to HyperCore. Applications could then read order-book depth, prices, balances and positions while submitting trades through revocable, trade-only agents. At launch, those direct HyperCore hooks remain planned functionality rather than an operational feature.
The separation matters because application logic and trading execution would occur in different environments. Elysium contracts would process strategy logic while actual orders execute against HyperCore’s books, potentially supporting market makers, lending protocols and automated vaults that react to live Hyperliquid market data. The approximately 100-millisecond trading pathway described for the future integration should therefore not be presented as a capability already available on mainnet.
Kinetiq has also attached network economics to future usage. The company says 50% of Elysium sequencer revenue will fund KNTQ buybacks, while 25% will be allocated to builders whose applications generate blockspace demand. Those allocations create a direct link between network activity and ecosystem incentives, although their economic significance will depend on actual sequencer revenue rather than the percentages alone.
The use of HYPE as gas further connects Elysium with an asset already embedded across Hyperliquid’s staking and trading infrastructure, including the broader HYPE staking ecosystem. The mainnet launch establishes the technical foundation, but transaction activity, liquidity and sustained application usage will determine whether the additional execution layer develops into a meaningful extension of Hyperliquid rather than simply additional available blockspace.