Skip to content
elysa

Bridge

HyperEVM → Elysium

The Elysa API isn't answering, so this page assumes mainnet and reads chains through public RPCs. Signed transactions fall back to a public RPC too.

Bridge checkreading HyperEVM…
  1. Inbox 0xce59…2cff.bridge() → …
  2. Bridge.rollup() → …
  3. Rollup.chainId() → … (expect 99901, Elysium)
From (on HyperEVM)
Vault locked.
No browser wallet detected (EIP-6963).
AmountBalance — HYPE
HYPE

Max keeps 0.01 HYPE for gas

To (on Elysium)same address as the source

Deposit from a plain wallet you control. Smart-contract wallets, EIP-7702 accounts and exchange withdrawals are credited to an aliased address on Elysium that you may not be able to use. Never deposit straight from an exchange: withdraw to your own HyperEVM wallet first.

From another chain

Bridge to HyperEVM with Relay first, then deposit here to reach Elysium.

Open relay.link

Bridged tokens

Tokens moved from HyperEVM through the official bridge, with or without a pool yet.

See bridged tokens

Your withdrawals

claiming arrives in M1

Withdrawals you submit from this browser show up here with the date they become claimable.

How it works

Elysa uses the rollup's own bridge. Deposits call Inbox.depositEth() on HyperEVM and arrive on Elysium in seconds to a minute. Withdrawals call ArbSys.withdrawEth() on Elysium and become claimable on HyperEVM after the confirm period (about 6 days).

Vault wallets sign in this browser; Elysa's API only relays the signed transaction.