Kinetiq has opened the mainnet for Elysium, a high-throughput Layer 2 designed to run decentralized-finance applications around Hyperliquid. The production network appeared in Kinetiq's documentation on November 9 with chain ID 99901, a public RPC endpoint and HYPE as its native gas asset. The launch gives developers a new EVM environment, but several of Elysium's most closely watched links to HyperCore are scheduled for a later upgrade rather than available on day one.

A faster EVM layer above HyperEVM

Elysium runs on Arbitrum Orbit technology, uses Conduit infrastructure and settles to HyperEVM, the smart-contract side of Hyperliquid. Kinetiq describes the chain as targeting 100-millisecond canonical blocks and 300 million gas units per second. Those figures are design and load-testing targets, not a guarantee that applications will always see the same performance under public traffic.

Related reporting: Hyperliquid Records First $14.58M USDC Reserve-Yield Payment

The architecture addresses a deliberate constraint in HyperEVM. Kinetiq's documentation says HyperEVM produces small three-million-gas blocks every second and larger 30-million-gas blocks once a minute. That keeps contract activity close to HyperCore, but it can limit applications that update state frequently, including market-making systems. Elysium is intended to absorb those higher-frequency workloads while keeping settlement and assets inside the broader Hyperliquid ecosystem.

What is live at launch

Kinetiq says the initial network ships on stock ArbOS with native HYPE gas, bridges to HyperEVM and a path for assets to move toward HyperCore. HYPE moves across the bridge one-for-one and remains the gas token, so Elysium does not require a separate network token merely to pay transaction fees. The mainnet configuration page lists a public RPC at rpc.elysium.kinetiq.xyz and recommends providers such as Alchemy for production traffic.

Alchemy independently outlined the rollout before launch and said Elysium is an optimistic rollup whose transactions settle to HyperEVM. It also identified trading, swaps, bridges, tokenized assets and analytics among the initial application categories. Availability still depends on each application deploying its own contracts, publishing supported assets and managing its own operational risks; a network launch does not establish that every announced integration is fully functional.

HyperCore integration comes later

The most important limitation is timing. Kinetiq says native reads of HyperCore order books and the fast write path for placing HyperCore orders are planned for an ArbOS upgrade about four weeks after mainnet. Until then, Elysium contracts do not receive the full direct market-data and trading interfaces described for the completed design. Developers porting applications from HyperEVM therefore need to distinguish launch-day functionality from the post-launch roadmap.

Speed brings familiar trust assumptions

Elysium starts with a single sequencer and an AnyTrust data-availability model using one Conduit-operated server, with full-data posting to HyperEVM as a fallback. Kinetiq says a multi-member data-availability committee and permissionless proving through Arbitrum's BoLD system are later hardening steps. Standard optimistic withdrawals also face a challenge period of about five and a half days, making an exit materially slower than a deposit.

For builders, the launch creates a production environment for applications that need faster blocks or more execution capacity than HyperEVM currently provides. For users, it adds another chain, bridge and set of contract addresses to verify. Adoption will depend less on the published throughput target than on reliable infrastructure, audited applications, usable liquidity and delivery of the planned HyperCore upgrade. November 9 marks the network's opening, not the completion of every feature in Kinetiq's architecture.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.