Overview
Block time, throughput, gas token, settlement, data availability, and sequencing parameters, with reference points against other chains.
Last updated
The parameters Elysium launches with. Testnet is live — see Networks for its chain ID, RPC, and explorer. Mainnet is pre-launch, so values may be refined before it ships.
At a glance
Parameter | Value |
|---|---|
Stack | Arbitrum Orbit (Nitro/ArbOS), operated with Conduit |
Block time | 100–200 ms real canonical blocks |
Perceived receipt | ≈300 ms |
Throughput | 300 Mgas/s execution target, validated in load testing before mainnet |
Gas token | HYPE, native ( |
EVM | Stock ArbOS at launch, with current EVM semantics and standard tooling |
Settlement | HyperEVM (chain ID |
Data availability | AnyTrust data availability committee, with full-data posting to HyperEVM as an automatic fallback |
Sequencing | Single sequencer at launch, neutral priority-fee ordering, no privileged lanes |
Withdrawals | Standard optimistic withdrawals with a challenge period |
Chain ID, RPC, explorer | See Networks — testnet is live |
Networks
Testnet is live and open. Mainnet endpoints are published at launch.
Testnet | Mainnet | |
|---|---|---|
Chain ID |
| Coming soon |
RPC |
| Coming soon |
Block explorer | Coming soon | |
Settles to | HyperEVM testnet (chain ID | HyperEVM (chain ID |
Testnet runs the same stack and the same contracts as mainnet will; only the endpoints and deployed addresses differ. Parameters may still be refined before mainnet.
Blocks
The 100–200 ms tick is the block. Elysium produces real canonical blocks at that cadence, so latest and transaction receipts have their plain meaning. There is no preconfirmation overlay to reason about. Block time will be tuned toward the ≈100 ms Nitro block floor as the chain hardens.
EVM
Elysium launches on stock, off-the-shelf ArbOS, so the EVM baseline follows the deployed ArbOS version. The Elysium-specific surfaces (HyperCore market data and Trading on HyperCore from Elysium) arrive later through an ArbOS network upgrade and are opt-in.
Data availability
A committee of data availability members stores the full transaction data and signs a certificate for each batch. Only the ≈100-byte certificate is posted to HyperEVM, which keeps per-transaction settlement costs minimal. If the committee is ever unavailable, the chain automatically posts full data to HyperEVM instead. See Security and data availability for the trust model.
Reference points
Chain | Block or slot time | Notes |
|---|---|---|
Elysium | 100–200 ms | real canonical blocks, ≈300 ms perceived receipt |
Robinhood Chain | ≈100–141 ms | the same Nitro execution engine, with Ethereum blobs for data availability |
Base | 200 ms preconfirmations | ≈300–500 ms perceived end to end |
Solana | ≈400 ms slots | |
HyperEVM | 1 s small blocks | 3M gas per small block |