What Is Kinetiq Elysium? The HyperEVM L2 Explained

Last updated: November 9, 2026

Endpoint and plans: Elysium RPC endpoint.

Terms on this page: Chain ID · Sequencer · Priority fee.

At a glance

What you see

You see Elysium named as an L2 for Hyperliquid and need to place it next to things you already know: is it a fork of HyperEVM, a sidechain, or an Arbitrum chain; does it have its own token; which chain ID belongs in the wallet; and can a contract on it read HyperCore order books today. Search results mix Kinetiq's chain with an unrelated older project that also used the name Elysium.

Why this happens

Hyperliquid has two execution environments: HyperCore, the order-book L1 with spot and perpetual markets, and HyperEVM, its EVM, chain ID 999. Kinetiq's documentation describes HyperEVM as deliberately constrained — small blocks carry 3M gas every second and 30M gas comes only in big blocks every 60 seconds — which keeps EVM activity composable with HyperCore but leaves little room for sustained high-frequency trading on the EVM. Elysium is Kinetiq's answer: a separate Arbitrum Orbit rollup that executes transactions itself and settles to HyperEVM, the way an Orbit chain normally settles to Ethereum or Arbitrum One. Kinetiq states a 300 Mgas/s execution target and real canonical blocks at about ten per second, so latest and receipts keep their plain meaning, with no preconfirmation layer. HYPE is native gas on Elysium end to end: it bridges in 1:1 from HyperEVM and withdraws 1:1. Because Elysium runs stock ArbOS at launch, standard EVM tooling — Solidity, Foundry, Hardhat, viem, ethers — works unchanged, and Arbitrum-specific behavior applies, such as the ArbSys precompile at 0x…64 for messages back to the parent chain. The launch posture is the standard one for a new Nitro chain: one sequencer orders transactions by priority fee with no privileged lanes, validation is permissioned with Arbitrum BoLD planned later, withdrawals are optimistic and wait a challenge period, and data availability uses the AnyTrust model with a single data availability server at launch and automatic fallback to posting full data on HyperEVM. The Hyperliquid-specific parts — a precompile that reads live HyperCore state and a predeploy that routes orders to HyperCore — are scheduled for an ArbOS network upgrade after launch, not for the first block.

Elysium, HyperEVM and HyperCore side by side

What to do

1. Configure wallets and clients with chain ID 99901 for Elysium mainnet and check it with eth_chainId, which returns 0x1863d. Do not reuse the HyperEVM entry (999): a transaction signed for one chain ID is invalid on the other.
2. Treat Elysium as an Arbitrum Orbit chain when you port code: block.number inside a contract follows Arbitrum's rules for the parent chain, ArbSys at 0x0000000000000000000000000000000000000064 is the system precompile, and every block begins with an ArbOS system transaction, so a block's transaction count includes it.
3. Plan for a fast head. At about ten blocks per second, a polling loop that assumes one block per second falls behind, and an eth_getLogs range of 10,000 blocks covers roughly 17 minutes of chain time. Use explicit block numbers for repeatable reads and page log scans by range.
4. Get gas by bridging HYPE from HyperEVM. Kinetiq's bridging guide describes native HYPE as a direct 1:1 deposit with no token contract; ERC-20s use the canonical token bridge. Withdrawals back to HyperEVM wait the rollup's challenge period.
5. Do not build launch-day logic on HyperCore precompiles. Kinetiq schedules the market-data precompile and the order-routing predeploy for an ArbOS upgrade about four weeks after mainnet; check the network's announcements for the activation block before relying on them.
6. Keep two other names apart: Hyperliquid's own HyperEVM testnet (998) and the unrelated Vulcan Forged chain that used the name Elysium on chain IDs 1338 and 1339 with its own token. Neither is Kinetiq Elysium.

curl -s "$ELYSIUM_RPC_URL" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# {"jsonrpc":"2.0","id":1,"result":"0x1863d"}   -> 99901, Elysium mainnet
# "0x185d9" -> 99801, Elysium testnet;  "0x3e7" -> 999, HyperEVM

import { defineChain } from "viem";

export const elysium = defineChain({
  id: 99901,
  name: "Elysium",
  nativeCurrency: { name: "HYPE", symbol: "HYPE", decimals: 18 },
  rpcUrls: { default: { http: [process.env.ELYSIUM_RPC_URL!] } },
});

When this is not our problem

Elysium's sequencer, bridge, data availability and upgrade schedule are run by Kinetiq and its operators; an RPC provider, Triport included, serves the chain's data and relays signed transactions but cannot change block production, fees or the withdrawal window. To read Elysium mainnet on Triport, set ELYSIUM_RPC_URL to the keyed URL form https://triport.io/r/<YOUR_KEY>/elysium.