Elysium Testnet

Elysium is currently testnet-only (chain ID 99801). Mainnet endpoints will be added under /elysium/mainnet when it launches.

What is Elysium?

Elysium is an Arbitrum Orbit (Nitro/ArbOS) L2 built by Kinetiq that settles to HyperEVM and runs co-located with HyperCore. It targets 100–200 ms blocks and ~100× HyperEVM’s throughput, with HYPE as the native gas token, bridged 1:1 from HyperEVM. HypeDexer indexes Elysium testnet end to end: its blocks, transactions, logs and tokens, the batches it posts on HyperEVM testnet, and the bridge between the two chains.

Base URL

https://api.hypedexer.com/elysium/testnet

All endpoints use the same X-API-Key header, response envelope (success, message, data, has_more) and pagination (limit up to 1000, offset) as the EVM endpoints. Time filters start_time / end_time take ISO 8601 UTC timestamps.

What you can query

Area	Endpoints	Highlights
Chain	`/stats`, `/stats/daily`, `/blocks`, `/transactions`, `/logs`	Activity excluding spam and system transactions, full receipts, decoded token transfers
Settlement	`/batches`	Every batch posted to the SequencerInbox on HyperEVM, with the Elysium blocks it contains and its posting delay
Bridge	`/bridge/transfers`, `/bridge/retryables`, `/bridge/tokens`, `/bridge/reserves`	Deposits and withdrawals tracked on both chains, stuck retryables, proof of reserves
Tokens	`/tokens`, `/tokens/{address}/holders`, `/tokens/{address}/transfers`	ERC-20 / 721 / 1155 metadata, supply, holders, bridge origin
Accounts	`/user/{address}/balances`, `/user/{address}/activity`, `/user/{address}/bridge`	Balances (also at a past block), unified activity feed, bridge history

Key concepts

User transactions and spam

Elysium testnet carries a lot of automated traffic. user_transactions and active_addresses exclude:

ArbOS system transactions (tx_type = 0x6a)
Bridge-delivered transactions (0x64 deposits, 0x69 retryable tickets, 0x68 redeems)
Known spam: empty transfers to 0x…dead and pulse(bytes32) heartbeats, flagged is_spam = 1

Raw transactions stay available: /transactions includes everything unless you pass include_spam=false or include_system=false.

Bridge transfers

A transfer is identified on both chains:

Direction	ID	Lifecycle
Deposit (HyperEVM → Elysium)	`d:<message index>`	`initiated` (HyperEVM message) → `ticket_created` (retryable on Elysium) → `completed` (redeemed), or `redeem_failed` / `expired`
Withdrawal (Elysium → HyperEVM)	`w:<position>`	`initiated` (`L2ToL1Tx` on Elysium) → `executed` (Outbox on HyperEVM)

route tells how the asset moves:

Route	Asset
`native`	HYPE, the gas token
`canonical`	A HyperEVM ERC-20 bridged into Elysium (standard Arbitrum gateway)
`mirror`	An Elysium-native token bridged out to HyperEVM (locked in an `ElysiumBridgeWallet`, minted as a mirror on HyperEVM)

/bridge/transfers/{tx_hash} accepts any hash of the journey: the HyperEVM transaction, the Elysium delivery transaction, the redeem transaction or the retryable ticket ID.

Retryable messages that move no asset (such as token registrations) are hidden by default; pass include_messages=true to include them.

Proof of reserves

/bridge/reserves is refreshed every 15 minutes and checks the bridge invariants:

native: HYPE held by the Bridge contract on HyperEVM ≥ net HYPE bridged into Elysium
canonical: token balance of the HyperEVM gateway ≥ totalSupply of its Elysium representation
mirror: Elysium token locked in its bridge wallet ≥ totalSupply of the mirror on HyperEVM

Pass only_unbacked=true to list only the tokens that break their invariant.

Quick examples

curl "https://api.hypedexer.com/elysium/testnet/stats" \
  -H "X-API-Key: YOUR_API_KEY"

curl "https://api.hypedexer.com/elysium/testnet/bridge/transfers/0xYOUR_TX_HASH" \
  -H "X-API-Key: YOUR_API_KEY"

curl "https://api.hypedexer.com/elysium/testnet/bridge/retryables?status=failed" \
  -H "X-API-Key: YOUR_API_KEY"

curl "https://api.hypedexer.com/elysium/testnet/user/0xYOUR_ADDRESS/balances?block=400000" \
  -H "X-API-Key: YOUR_API_KEY"

Network


Chain ID	`99801`
Settlement	HyperEVM testnet (chain `998`)
Data availability	AnyTrust
Public RPC	`https://elysium-testnet-rpc.hypedexer.com` (HTTPS and WSS)
Explorer	`https://test-explorer.elysium.kinetiq.xyz`

Snapshots

Running your own Elysium node? Start from a HypeDexer snapshot instead of syncing from genesis. A sync from genesis replays every batch posted on HyperEVM since the chain was deployed and takes days on a public HyperEVM RPC. With a snapshot, a new node only has to catch up on the blocks produced since the snapshot was taken (less than a day). We publish an archive snapshot (all historical state) of our own Elysium testnet node every day, around 03:30 Paris time. The last 2 snapshots are kept.


Latest snapshot	`latest-archive.txt` (name of the most recent archive)
Download	`https://elysium-testnet-snapshots.hypedexer.com/elysium-archive_<block>.tar`
Checksum	`https://elysium-testnet-snapshots.hypedexer.com/elysium-archive_<block>.tar.sha256`
All files	elysium-testnet-snapshots.hypedexer.com
Format	Uncompressed `.tar` of the Nitro database (`l2chaindata`, `arbitrumdata`, `wasm`), ~19 GB
Client	Arbitrum Nitro `v3.9.5` (`offchainlabs/nitro-node:v3.9.5-66e42c4`)

<block> is the Elysium block the snapshot was taken at. Plan for about twice the archive size in free disk space during the restore.

Option 1: let Nitro download it

Nitro can fetch the latest snapshot on its own. Add these flags to your node:

--init.latest=archive
--init.latest-base=https://elysium-testnet-snapshots.hypedexer.com/

On first start, when the database is empty, Nitro reads latest-archive.txt, downloads the archive, verifies its SHA-256 and extracts it. If a database already exists, the flags are ignored, so you can leave them in place. Full example with Docker:

docker run -d --name elysium-node \
  -v elysium-data:/home/user/.arbitrum \
  -v "$PWD/chainInfo.json:/config/chainInfo.json:ro" \
  -p 127.0.0.1:8547:8547 -p 127.0.0.1:8546:8546 \
  offchainlabs/nitro-node:v3.9.5-66e42c4 \
  --conf.file=/config/chainInfo.json \
  --init.latest=archive \
  --init.latest-base=https://elysium-testnet-snapshots.hypedexer.com/ \
  --init.download-path=/home/user/.arbitrum/snapshot-download \
  --node.staker.enable=false \
  --execution.forwarding-target=https://rpc-elysium-testnet.t.conduit.xyz \
  --node.feed.input.url=wss://relay-elysium-testnet.t.conduit.xyz/ \
  --parent-chain.connection.url=https://rpc.hyperliquid-testnet.xyz/evm \
  --node.inbox-reader.max-blocks-to-read=1000 \
  --node.dangerous.disable-blob-reader \
  --node.data-availability.enable \
  --node.data-availability.rest-aggregator.enable \
  --node.data-availability.rest-aggregator.urls=https://das-elysium-testnet.t.conduit.xyz \
  --execution.caching.archive \
  --http.addr=0.0.0.0 --http.api=net,web3,eth --http.vhosts=* --http.corsdomain=* \
  --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=net,web3,eth --ws.origins=*

chainInfo.json is the Elysium testnet chain config, published by Conduit at https://api.conduit.xyz/file/v1/arbitrum/chaininfo/elysium-testnet.

Nitro keeps the downloaded archive in --init.download-path after extracting it. Delete snapshot-download from the volume once the node is running to free ~19 GB.

Option 2: download and extract it yourself

Get the latest snapshot name

BASE=https://elysium-testnet-snapshots.hypedexer.com
SNAPSHOT=$(curl -s $BASE/conduit-orbit-deployer/latest-archive.txt)
echo $SNAPSHOT

Download it and check the checksum

curl -O $BASE/$SNAPSHOT
echo "$(curl -s $BASE/$SNAPSHOT.sha256)  $SNAPSHOT" | sha256sum -c -

The last command must print OK.

Extract it into the Nitro data directory

Nitro stores the Elysium database in <data dir>/conduit-orbit-deployer/nitro/. The data dir is /home/user/.arbitrum in the Docker image.

mkdir -p data/conduit-orbit-deployer/nitro
tar -xf $SNAPSHOT -C data/conduit-orbit-deployer/nitro
sudo chown -R 1000:1000 data   # the Nitro image runs as uid 1000
rm $SNAPSHOT

Start the node

Mount data as /home/user/.arbitrum and start Nitro with your usual flags. It picks up the database and only syncs the blocks produced since the snapshot.

Use the snapshot with the same major Nitro version (v3.9.x). The snapshot is a shortcut, not a trust assumption on new blocks: your node still derives every new block from the batches posted on HyperEVM.

Need help, or a snapshot for another setup? Contact the HypeDexer team on Telegram, @wsm_enigma.

Introduction

REST API

What is Elysium?

Base URL

What you can query

Key concepts

User transactions and spam

Bridge transfers

Proof of reserves

Quick examples

Network

Snapshots

Option 1: let Nitro download it

Option 2: download and extract it yourself

​What is Elysium?

​Base URL

​What you can query

​Key concepts

​User transactions and spam

​Bridge transfers

​Proof of reserves

​Quick examples

​Network

​Snapshots

​Option 1: let Nitro download it

​Option 2: download and extract it yourself

What is Elysium?

Base URL

What you can query

Key concepts

User transactions and spam

Bridge transfers

Proof of reserves

Quick examples

Network

Snapshots

Option 1: let Nitro download it

Option 2: download and extract it yourself