Token bridging on Elysium

How tokens move between Elysium, HyperEVM, and HyperCore, and how the bridge legs compose into a full lifecycle: launch on Elysium, mirror to HyperEVM, and graduate to a HyperCore spot orderbook. Each leg also stands alone, so a token can start in any of the three environments and bridge wherever it is needed.

Testnet is live — chain ID 99801, RPC https://testnet-rpc.elysium.kinetiq.xyz, explorer elysium.kinetiq.xyz/testnet-explorer. Each guide below carries the testnet addresses for its own leg. Mainnet contract addresses (including the deposit-wallet family), chain ID, and RPC endpoints are published at launch, and details may be refined before then. HyperCore's native linkage mechanism is live Hyperliquid protocol behavior today.

The three environments

• Elysium: a high-throughput EVM chain (100–200 ms blocks) with HYPE as native gas. See What is Elysium.
• HyperEVM: Hyperliquid's EVM (chain ID 999). Elysium settles to HyperEVM, and HyperEVM is the hop between Elysium and HyperCore.
• HyperCore: Hyperliquid's L1, with spot and perp orderbooks at ≈70 ms cadence. The destination for tokens that graduate to a spot orderbook.

The bridging map

Issuers taking a token to HyperCore for the first time also need HyperCore spot deployment, the one-time ceremony that buys the ticker and links it to a deposit wallet. For the contract-level design (architecture diagrams, address derivation, and the trust model), see Token bridging architecture.

Supported tokens

Both EVM legs support standard ERC-20s whose transfers move the exact requested amount. Fee-on-transfer and rebasing tokens are not currently supported, because escrow and minted supply must match 1:1.

The mirror bridge also requires IERC20Metadata (name(), symbol(), decimals()), since the metadata is part of the pairing, and works best with immutable metadata. See the 1:1 guarantee.

Native HYPE

HYPE is Elysium's gas token. Deposit HYPE on HyperEVM and receive native gas on Elysium 1:1, or burn native HYPE on Elysium and withdraw HYPE 1:1. There is no wrapper asset and no token contract in this path. HYPE moves as native value (msg.value) end to end, and every bridge fee in these guides is paid the same way.

HyperEVM-native tokens: the canonical bridge

Any ERC-20 on HyperEVM bridges to Elysium permissionlessly. The token locks in the bridge's standard gateway on HyperEVM (the gateway contract holds the escrow itself), and a 1:1 representation is minted on Elysium. The first-ever deposit auto-deploys the representation at a deterministic address, with no registration, issuer involvement, or permission required. Burning the representation on Elysium releases the escrow on HyperEVM after the challenge period.

This is the stock token bridge of the Arbitrum Nitro stack that Elysium runs on, unchanged. It connects Elysium and HyperEVM only and is unrelated to any bridge on the Arbitrum network itself. Full flow with code: Bridging HyperEVM tokens to Elysium.

Elysium-native tokens: the mirror bridge

The mirror bridge is the canonical bridge run in reverse. An Elysium-native token locks on Elysium and a 1:1 mirror is minted on HyperEVM. The native token needs zero bridge code: no special interfaces, no mint authority granted to anything, and no wrapping. Existing tokens bridge the same way as purpose-built ones, and holders on Elysium always hold the original asset.

Setup is one-time and permissionless, with one transaction on each chain in either order: deploy the escrow wallet on Elysium, and deploy and register the mirror on HyperEVM. Full flow with code: Bridging Elysium tokens to HyperEVM.

The 1:1 guarantee

Every Elysium token maps to exactly one live mirror, enforced on-chain:

• A mirror's identity is keyed by the token plus its exact metadata (name, symbol, decimals).
• The Elysium factory reads the token's live metadata and only ever deploys the escrow wallet for the mirror that metadata produces. No other party can place code at that wallet's address.
• Mirror supply is only minted against wallet escrow. A mirror created with any other metadata can exist, but its wallet can never be deployed, so its supply stays zero forever. It is an inert contract, not a competing token.

To find the canonical mirror, call expectedL1Mirror(token) on the Elysium factory, or on HyperEVM check that the mirror has factory provenance and a nonzero supply. Bridging Elysium tokens to HyperEVM has the code, and Token bridging architecture explains the derivation.

Token lifecycle

The legs compose into the full lifecycle without leaving the Hyperliquid ecosystem:

A mirror on HyperEVM is an ordinary ERC-20, so it graduates to HyperCore the same way any HyperEVM token does. A deposit wallet escrows it, and HyperCore credits and debits Core spot balances against that escrow, keeping escrowed balance equal to circulating Core supply. The issuer runs HyperCore spot deployment once, and holders then bridge with HyperCore bridging via deposit wallets.

Amounts and decimals

• Both EVM legs preserve decimals exactly. A representation has the same decimals as its HyperEVM original, and a mirror has the same decimals as its Elysium original. All EVM calls take base units.
• The Core linkage scales between the EVM token's decimals and the Core token's weiDecimals. See HyperCore bridging: amounts and decimals.
• Bridge fees on the EVM legs are paid in native HYPE (msg.value) on the chain where the transaction starts. There are no fee-token approvals anywhere.