Elysium Tech Stack: Arbitrum Orbit L2 Settling to HyperEVM
Elysium is an Arbitrum Orbit Layer-2 running Nitro on ArbOS 51 that settles to HyperEVM, Hyperliquid's EVM layer. It uses AnyTrust for data availability, HYPE as its gas token, and targets 100-200 ms blocks with 300 Mgas/s of execution. It is operated with Conduit and built by Kinetiq.
This page is for builders, researchers and curious traders who want the Elysium tech stack in one place: what it runs on, how fast it is, what it costs, and how it compares to chains you already know. If you only need the basics, start with what Elysium is.
What is an Arbitrum Orbit chain?
Arbitrum Orbit is a framework for launching your own chain using Arbitrum's Nitro software. An Orbit chain can settle to Ethereum, to an Arbitrum chain, or to another EVM chain. Elysium picks HyperEVM as its parent. That makes it a Layer-2 on top of Hyperliquid's EVM rather than on top of Ethereum.
Because Elysium runs stock ArbOS, Solidity and Vyper contracts compile unchanged, and standard tools like Foundry, Hardhat, viem and ethers work as expected. See deploying a contract on Elysium for a walkthrough.
Why does Elysium settle to HyperEVM?
HyperEVM deliberately keeps its blocks small, roughly 1 second blocks with 3M gas each. That protects HyperCore, Hyperliquid's trading engine, from being slowed by heavy EVM workloads. The downside is limited room for busy apps. Elysium exists to give trading apps, launchpads and market-making AMMs more space, while staying inside the Hyperliquid ecosystem and paying gas in HYPE. For the relationship between all three layers, read Hyperliquid, HyperEVM and Elysium.
What are the core specs?
| Spec | Elysium |
|---|---|
| Framework | Arbitrum Orbit, Nitro, ArbOS 51 |
| Parent chain | HyperEVM (mainnet chain ID 999, testnet 998) |
| Chain ID | Mainnet 99901 (what ElyScreener reads), testnet 99801 |
| Block time | Design target 100-200 ms; testnet observed about 0.25-0.32 s |
| Execution target | 300 Mgas/s |
| Gas token | HYPE, bridged 1:1, no wrapper |
| Testnet gas price | About 0.01 gwei |
| Data availability | AnyTrust committee, fallback to full data on HyperEVM |
| Sequencing | Single sequencer, no public mempool, priority-fee ordering |
| Operator | Kinetiq, with Conduit |
How does AnyTrust data availability work?
On a classic rollup, all transaction data is posted to the parent chain, which is secure but costly. With AnyTrust, a Data Availability Committee stores the data and signs a compact certificate that gets posted to HyperEVM instead. If the committee cannot provide signatures, the chain falls back to posting full data to HyperEVM. It keeps running, it just becomes more expensive. This is a big reason testnet gas stayed around 0.01 gwei. More on costs in Elysium gas fees.
How are transactions ordered?
Elysium launches with one sequencer and no public mempool. Within a block, transactions are ordered by priority fee, with no privileged lanes. For developers this has a practical effect: pending-transaction filters return nothing, so apps should rely on block inclusion rather than watching a mempool. Tracing is available through debug_* methods only; trace_* is not supported.
If the sequencer censors a user, forced inclusion through the delayed inbox on HyperEVM provides a fallback. Validation is permissioned at launch, with permissionless fraud proofs via Arbitrum BoLD planned. The full risk picture is in Is Elysium safe?
What should developers know before deploying?
- Testnet first. Use chain ID 99801 and the public RPC
https://testnet-rpc.elysium.kinetiq.xyz, with the explorer at elysium.kinetiq.xyz/testnet-explorer. Free test HYPE is covered in the testnet faucet guide. - Mainnet RPCs. Community endpoints such as
https://rpc-live.elysp.comandhttps://rpc-live.boxa.clubare in use. Kinetiq is expected to publish an official mainnet RPC, so swap to it once available. - No mempool tricks. Do not build logic that depends on seeing pending transactions. Confirm by receipt.
- Short blocks. Timestamps advance quickly, so avoid assumptions copied from 12-second Ethereum blocks.
How do bridging and withdrawals work?
- Canonical bridge: built on Arbitrum Orbit gateways for HyperEVM ERC-20s and HYPE.
- Mirror bridge: lets Elysium-native tokens reach HyperEVM and HyperCore.
- Withdrawals: optimistic, finalizing after a challenge period.
Step-by-step instructions are in bridging HYPE to Elysium.
What is coming with the HyperCore upgrade?
A planned ArbOS upgrade, about four weeks after the November 9, 2026 mainnet, adds two pieces. First, a precompile to read live HyperCore market data at around 70 ms granularity and 150-350 ms freshness. Second, an ElysiumCoreWriter predeploy so contracts can route trade-only orders to a user's HyperCore account in around 100-200 ms. The data is attested by the sequencer. This is not live at launch.
How does Elysium compare to other chains?
The table below uses only figures we can stand behind. Where a number is not part of our verified facts, we leave it general rather than guess.
| Chain | Type | Block time | Gas token | Settles to |
|---|---|---|---|---|
| Elysium | Arbitrum Orbit L2 | Target 100-200 ms (testnet ~0.25-0.32 s) | HYPE | HyperEVM |
| HyperEVM | EVM layer of Hyperliquid | About 1 s, 3M gas per block | HYPE | Part of Hyperliquid L1 |
| Base | Ethereum L2 (OP Stack) | Check Base docs | ETH | Ethereum |
| Robinhood Chain | Arbitrum-based L2 | Check official docs | Check official docs | Check official docs |
| Solana | Layer-1, non-EVM | Sub-second slots | SOL | Not applicable |
The key difference: Elysium is the only one in this list built to sit next to Hyperliquid's order books, paying gas in HYPE and planning native access to HyperCore data.
What does this mean for traders?
Fast blocks and cheap gas make it practical to launch and trade thousands of small coins. ElyScreener tracked about 4,200 coins across Elysium launchpads as of November 4, 2026. Speed cuts both ways, though: bots can buy in the very first block. That is why the ElyScreener live screener flags bot bundles, where three or more wallets buy in the same block. Trade carefully, and never with funds you cannot lose.
FAQ
Is Elysium an Arbitrum chain?
Yes. Elysium is an Arbitrum Orbit chain running Nitro on ArbOS 51. Unlike most Orbit chains, it settles to HyperEVM instead of Ethereum.
What is Elysium's block time?
The design target is 100-200 ms. On testnet, observed block times were around 0.25-0.32 seconds.
What is the Elysium chain ID?
The mainnet chain ElyScreener reads is 99901. The testnet chain ID is 99801. The parent HyperEVM mainnet is 999.
Does Elysium use a data availability layer?
Yes, AnyTrust. A committee stores data and posts certificates to HyperEVM, with a fallback to posting full data if the committee is unavailable.
Can I use Hardhat or Foundry on Elysium?
Yes. Elysium runs stock ArbOS, so Solidity and Vyper compile unchanged and Foundry, Hardhat, viem and ethers all work.
Open ElyScreener →