What is Elysium?
Kinetiq is building Elysium as an Arbitrum Orbit L2 within the Hyperliquid ecosystem. Its planned launch uses stock ArbOS, native HYPE gas and HyperEVM settlement. It is a separate rollup, not another name for HyperEVM.
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
Why build beside HyperEVM?
HyperEVM limits its small-block capacity. Elysium targets sustained trading workloads, including market-making AMMs, frequent quote updates and general DeFi. The official target is 100 ms canonical blocks and 300 Mgas/s. These are pre-launch specifications, not our measured bot speeds, guaranteed fills or settlement times.
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
How Elysium fits into the Hyperliquid stack
HyperCore supplies spot and perpetual order books; HyperEVM supplies the EVM environment within Hyperliquid. Elysium adds rollup execution above HyperEVM. Token movement and the later direct read/write paths must be read separately.
↓ Elysium settles to HyperEVM · canonical / mirror token bridges are separate paths
↕ HyperEVM ↔ HyperCore token linkage
Post-launch direct paths: HyperCore state → Elysium read precompile; Elysium order intent → keeper agent → HyperCore. These are separate from settlement and token bridging.
First-party source ↗ · Checked 2026-11-05
HyperCore vs HyperEVM: related network guideLaunch capabilities vs later upgrades
The launch plan and the current public availability are different. Elysium remains pre-launch in the official docs. Planned launch capabilities must pass launch-day verification before we label them live.
| Planned phase | Capabilities |
|---|---|
| LAUNCH_CAPABILITIES | stock arbos · native hype gas · canonical blocks · hyperevm settlement · anytrust data availability · canonical bridge · mirror bridge · hypercore graduation path |
| POST_LAUNCH_CAPABILITIES | hypercore market data precompile · elysium core writer · keeper fast write |
| Current observation | PRE_LAUNCH · PENDING_LIVE_VERIFICATION |
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
Later: reading HyperCore market data
The native market-data precompile is planned for an ArbOS upgrade about four weeks after mainnet, not day one. It is designed to expose order books, prices, balances and positions through a co-located node. The docs describe sequencer-attested data rather than a HyperCore state proof; applications must check its freshness.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
Later: trading on HyperCore from Elysium
The ElysiumCoreWriter and keeper path are also post-launch. The design uses a trade-only agent on the user’s HyperCore account. The agent can place and cancel orders but cannot withdraw funds. Actions are asynchronous: an Elysium intent is not a confirmed HyperCore fill, and the two systems are not one atomic transaction.
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
How to add Elysium to your wallet
Mainnet network setup is prepared below. Pending values are not instructions to enter a placeholder in your wallet. Do not substitute the testnet network or a same-named chain. The docs currently offer a testnet add-network action, not a verified mainnet setup.
| Mainnet setting | Value |
|---|---|
| Network name | Elysium |
| RPC URL | MAINNET_VALUE_PENDING |
| Chain ID | MAINNET_VALUE_PENDING |
| Currency symbol | HYPE |
| Explorer URL | MAINNET_VALUE_PENDING |
- Open your wallet and check its custom EVM-network support.
- Open the official Elysium connection guide. Wait for confirmed mainnet values.
- When values are verified, add the custom network with its RPC, chain ID, HYPE symbol and explorer. Review before saving.
- Use the verified official funding route and check the balance on the destination network.
- Only then select Elysium in the terminal, inspect wallet permissions and verify the token and quote.
No add-network button is enabled while values remain pending.
First-party source ↗ · Published/updated 2026-10-20 · Checked 2026-11-05
Choose a wallet for a custom EVM network
MetaMask documents manual custom-network entry. That makes it a setup option to validate when Elysium mainnet parameters are available; it is not a completed mainnet connection test. In MetaMask Extension, open Networks, choose Add a custom network and enter the verified values from the table. Our existing MetaMask referral is for Rewards and is not used as an add-network or wallet-install link.
First-party source ↗ · Checked 2026-11-05
Do not assume every EVM wallet supports Elysium
Phantom’s published supported-network list does not include Elysium. Its manual custom-network restriction means HyperEVM support cannot be extended to Elysium. We do not show a Phantom referral as an Elysium wallet option.
First-party source ↗ · Checked 2026-11-05
Funding: native HYPE and token routes
Native HYPE moves between HyperEVM and Elysium as gas, 1:1. It is separate from the ERC-20 canonical and mirror routes below. For a trader starting with HYPE on HyperEVM, the documented native-HYPE route is the relevant funding path once its mainnet interface is verified. Keep gas on the chain where each action starts.
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
Optional funding step: HYPE on HyperEVM
ChangeNOW returned a BTC-to-HYPE quote for the HyperEVM receiving network during our check on 5 November. The network’s existing partner link opens ChangeNOW; choose your pair and explicitly select HYPE on HyperEVM, then check a fresh quote. This does not deposit onto Elysium or replace its official bridge. Availability depends on the current quote, amount and region.
First-party source ↗ · Checked 2026-11-05
HyperEVM → Elysium: canonical token bridge
For a HyperEVM-native ERC-20, the canonical bridge locks the original on HyperEVM and mints its representation on Elysium. The documented approval targets the token’s gateway, not the router. To return, burn the representation on Elysium and claim the original on HyperEVM after the challenge period. Mainnet gateway addresses and the exact available UI remain pending.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
Elysium → HyperEVM: mirror bridge
For an Elysium-native token, the mirror route instead locks the original on Elysium and creates a counterpart on HyperEVM. Its setup requires an escrow wallet and a registered mirror. Outbound minting follows the challenge period; the return burns the mirror to release the original. Token identity includes exact metadata. Rebasing and fee-on-transfer tokens are not supported by this documented flow.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
HyperCore deposit-wallet flows
The HyperCore leg is HyperEVM ↔ HyperCore. An Elysium-native token first needs its HyperEVM mirror. For a linked token, the deposit wallet holds the underlying ERC-20 while HyperCore credits the corresponding spot balance. This wallet is an escrow adapter, not an ERC-20 to add to a wallet token list. The Elysium deposit-wallet family remains pre-launch even though Hyperliquid’s native linkage behavior already exists.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
Bridging does not automatically create an order book
A token issuer must complete HyperCore deployment and linking steps; spot listing is an additional action. A token appearing as bridged or pending does not establish a listed pair, liquidity or trading support in a terminal. Traders should verify the actual market rather than follow issuer deployment instructions.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
Bridge and launch security checks
Bridge components include upgradeable contracts. A deterministic address does not remove upgrade or configuration risk. Match each asset to its own origin and bridge route, and verify mainnet contract provenance before approval. A successful transfer into escrow is only one leg of the process; check final delivery and any remaining claim step.
First-party source ↗ · Published/updated 2026-09-22 · Checked 2026-11-05
How trading differs from HyperEVM
Elysium documents priority-fee ordering and HYPE-denominated gas. Compare an actual product quote, its platform charge and network cost separately. Faster block cadence does not guarantee better liquidity, lower slippage or faster final withdrawal. MEV controls and private routing need product-specific evidence.
First-party source ↗ · Published/updated 2026-11-03 · Checked 2026-11-05
Know the launch trust model
The documented launch uses a single sequencer, permissioned validation and AnyTrust data availability, with HyperEVM fallback. Permissionless proving is part of later hardening. Optimistic withdrawals involve a challenge period; no fixed withdrawal duration is promised in this guide. We have not independently audited these systems.
First-party source ↗ · Published/updated 2026-10-20 · Checked 2026-11-05
DEXes, aggregators and launchpads
This short list records network-owned announcements, not verified liquidity or tested bot integrations. Listing a DEX or launchpad here does not populate any product’s supported-venue fields.
| Project | Role | Evidence state |
|---|---|---|
| Nest | DEX | ANNOUNCED · not live-tested |
| Uniswap | DEX infrastructure | ANNOUNCED · not live-tested |
| 0x | Swap API | ANNOUNCED · not live-tested |
| KyberSwap | Aggregator | ANNOUNCED · not live-tested |
| Citadel | Launchpad | ANNOUNCED · not live-tested |
| Montra | Launchpad | ANNOUNCED · not live-tested |
Nest: Network-owned source ↗
Uniswap: Network-owned source ↗
KyberSwap: Network-owned source ↗
Citadel: Network-owned source ↗
Montra: Network-owned source ↗
First-party source ↗ · Checked 2026-11-05
Contract addresses: check the environment
The official address reference currently labels its contracts as testnet and says mainnet addresses arrive at launch. We do not copy those addresses into mainnet instructions. Match the deployment network as well as the address, especially for tokens with familiar names such as WHYPE or USDC.
First-party source ↗ · Published/updated 2026-10-20 · Checked 2026-11-05
Official Elysium resources
Use these first-party references to check changes. Testnet destinations are labelled; mainnet transaction destinations remain pending. These are ordinary reference links, not affiliate redirects.
- Elysium docs ↗Pre-launch reference
- Elysium official site ↗Official project
- Kinetiq ↗Builder
- Ecosystem directory ↗Testnet directory + announcements
- Network connection details ↗Mainnet values pending
- Bridge documentation ↗Mainnet transaction route pending
- Contract reference ↗Testnet addresses; mainnet pending
- Elysium status ↗Network status reference
- Elysium on X ↗Official announcements
- Hyperliquid docs ↗HyperCore / HyperEVM context
Mainnet bridge and explorer transaction links: MAINNET_VALUE_PENDING.
Choose a tool after checking its Elysium record
Choose a product interface and prepare your account. Maestro and Banana Gun offer Telegram entries; GMGN offers a web terminal. These product-wide partner links are available now. Elysium launch commitments are documented, but the Elysium trading path still needs live verification.
Partner link · We may earn commission. Opens the general product; Elysium support is launch-confirmed, not live-tested. Check the selected chain before funding.
Partner link · We may earn commission. Opens the general product; Elysium support is launch-confirmed, not live-tested. Check the selected chain before funding.
Partner link · We may earn commission. Opens the general product; Elysium support is launch-confirmed, not live-tested. Check the selected chain before funding.
Track wallets and tokens only on a supported network
Cielo’s documented supported chains include HyperEVM and Hyperliquid, but we have not established Elysium support. No Elysium tracking referral is active. A familiar address or token appearing on another network does not confirm that Elysium transactions are indexed.
First-party source ↗ · Checked 2026-11-05
Pump.fun App: announced for November 9
Pump.fun announced Elysium trading in the Pumpfun App for November 9. This is a dated app commitment, not a live trading test or a separate confirmation for Terminal (formerly Padre). The funding asset, Elysium fee quote and supported tokens still need verification. Buying an Elysium token from an existing SOL balance is a launch-day check; it is not yet a confirmed route in this guide.
Partner link · We may earn commission. Opens the general product; Elysium support is launch-confirmed, not live-tested. Check the selected chain before funding.
First-party source ↗ · Published/updated 2026-10-28 · Checked 2026-11-05
Can an existing SOL balance fund a token on another chain?
Our October 22 Pump.fun walkthrough showed a Base token alongside a cross-chain swap panel and SOL as the account’s payment asset. No order was executed. That is useful preparation for the Elysium app launch, but it does not verify SOL-to-Elysium funding. At launch, check the destination chain, payment asset, receiving wallet, full quote and failure/refund handling.
First-party source ↗ · Checked 2026-10-22
Read the dated Base interface walkthrough →