Crypto Balloon

Elysium Mainnet: Fast-Block Claims Alongside Single-Sequencer and Withdrawal Constraints

Elysium, a Layer 2 network in the Hyperliquid ecosystem built by Kinetiq and operated by Conduit, launched its mainnet, according to an Odaily report published on November 9, 2026, at 21:26:17 UTC+8.

The report lists a 100-millisecond block time, approximately 300 milliseconds for funds to arrive, and an execution target of 300 Mgas/s. The execution figure is a target, not a demonstrated throughput result in the supplied report.

Launch architecture and withdrawal limits

Elysium uses Arbitrum Orbit’s Nitro/ArbOS stack and settles on HyperEVM. Gas is paid in native HYPE bridged from HyperEVM at a 1:1 ratio. The report lists the chain ID as 999.

At launch, the network uses:

  • A single sequencer with neutral priority-fee ordering.
  • AnyTrust for data availability, initially served by a single Conduit server, with the committee yet to be determined.
  • Standard optimistic withdrawals with a challenge period of approximately 5.5 days.

The reported arrival speed should therefore not be confused with the time required for a standard optimistic withdrawal. Fast blocks and a multiday withdrawal challenge period describe different parts of the system.

Token-market pathway remains an official claim

According to officials cited in the report, tokens can follow a route from issuance on the Elysium AMM, through deeper liquidity via prop-AMM, to graduation onto HyperCore’s spot order book and perpetual-futures listing through HIP-3. The report does not document a token completing that full route.

Contracts can read HyperCore order books, prices, balances and positions. An upgrade was planned for approximately four weeks after the report, adding HyperCore-native market-data precompiles and a fast write channel; the supplied source does not confirm its subsequent delivery.

The distinction is between the reported launch configuration and the broader market-access promise: the former includes a single sequencer and initially single-server data-availability service, while the latter is presented as an official pathway rather than a documented end-to-end outcome.