SonarX
Coming soonElysium mainnet launches November 9, 2026. SonarX will support it from day one.Read the announcement →

Indexed ElysiumBlockchain Data

Elysium is a high-throughput DeFi chain built by Kinetiq for the Hyperliquid ecosystem: an Arbitrum Orbit rollup that settles to HyperEVM, runs alongside HyperCore and uses HYPE as gas, with 100 ms blocks and a 300 Mgas/s execution target.

Elysium on the SonarX chain grid

How to query Elysium data with SonarX

Snowflake, and file dumps to your object storage

Query Elysium blockchain data with plain SQL from a live database inside your own Snowflake account, populated with the indexed chain dataset. There is no pipeline to build and no second copy to store. The same dataset ships as file dumps to your own object storage for lakes and warehouses that are not Snowflake.

  • Full history as a Snowflake data-share
  • File dumps to S3 or your own object storage
  • Real-time delivery, current to chain tip

Used for:

  • Analytics teams already on Snowflake that want Elysium data beside their existing tables
  • Fund accounting and treasury reporting that reconciles against a fixed history
  • Cross-chain questions answered in one SQL statement instead of one query per chain
  • Loading Elysium history into BigQuery, Databricks, Redshift or a Spark lake
  • Replacing a self-hosted indexer and the engineering time that keeps it running
  • Serving one governed dataset to several desks without copying it per team

Kafka Streaming

Coming soon

Event stream

Consume Elysium activity as a continuous stream of normalized records, produced as the chain is indexed instead of polled for.

Used for:

  • Trading and execution systems that act on Elysium activity within seconds
  • Fraud and anomaly detection that has to fire before settlement
  • Live dashboards and alerting on Elysium wallet or protocol activity
  • Feeding a stream processor that already reads from Kafka
  • Keeping an internal store hot without waiting for a batch window
  • Event-driven services that would otherwise poll on a timer

Curated Datasets

Coming soon

Purpose-built tables

Protocol-level Elysium datasets modelled for one job, so the decoding and the joins are done before the data reaches you.

  • DeFi
  • Staking — on request
  • Tokens and payments
  • RWAs and tokenization — on request

Used for:

  • Position-level Elysium lending, swap and liquidity analysis
  • Reward, delegation and validator reporting without rebuilding the model
  • Token distribution, holder and payment-flow reporting
  • Risk and exposure work that needs protocol state, not raw logs
  • Skipping the decoding layer an in-house team would have to maintain
  • Extending an existing Elysium share with a modelled slice

Balances

Enabled on request

Tables and REST

Read what a Elysium address held, either as it stands now or exactly as it stood at a past block or timestamp.

  • Point-in-time balance tables, as at any block or timestamp
  • Real-time balances API for latest and historical balances
  • Batch API for wallets, tokens and balances in bulk

Used for:

  • Reconstructing Elysium portfolios and NAV as at a reporting date
  • Audit and reconciliation work that has to be repeatable months later
  • Wallet and portfolio products that render Elysium balances on page load
  • Compliance checks that read one Elysium address at one block height
  • Refreshing holdings for a whole book of accounts on a schedule
  • Tax and cost-basis workflows that need holdings at each event

Realtime API

Enabled on request

REST over the indexed dataset

Query indexed Elysium records over REST, reading the same dataset the share reads, with no warehouse in the path.

Used for:

  • Applications that need one answer rather than a table scan
  • Customer-facing screens where query latency is visible to a user
  • Services that have no data warehouse and do not want to run one
  • Prototyping against production data before committing to a share
  • Backend checks that run per request instead of per batch
  • Teams that want indexed Elysium data behind their own API layer

Elysium data: frequently asked questions

What is Elysium?

Elysium is a high-throughput DeFi chain built by Kinetiq, which describes itself as the largest HYPE liquid staking protocol on Hyperliquid, for the Hyperliquid ecosystem. It is an optimistic rollup on Arbitrum Orbit that settles to HyperEVM, runs alongside HyperCore and uses HYPE as its native gas token. Blocks come every 100 ms, with a perceived transaction receipt of about 300 ms, and the execution target is 300 Mgas/s, against 3 Mgas/s on HyperEVM small blocks. An AnyTrust data availability committee keeps the transaction data, with a fallback to posting full data on HyperEVM. Public mainnet launches on November 9, 2026, with a private mainnet running before then and a testnet live now.

HyperEVM keeps its blocks small on purpose, which preserves composability with HyperCore. Elysium takes the sustained, latency-sensitive activity that needs more room, such as high-frequency trading and market-making AMMs that refresh quotes several times per second, while assets, settlement and market structure stay Hyperliquid-native.

Elysium data on SonarX

SonarX plans to support Elysium from day one, indexing it from the first block and staying live at the tip, with the same automated, around-the-clock data quality controls applied to every chain. The standard Elysium coverage spans blocks, transactions and failed transactions, receipts, logs and traces, contracts created, token, NFT and internal transfers, priced transfers with USD valuation, approvals, DEX pools and swaps, token metadata and asset discovery, and token pricing with current and historical OHLCV views.

The same normalized model is used on every chain SonarX covers, so an Elysium query and a HyperEVM query take the same shape and join without a translation layer.

How SonarX indexes Elysium

Elysium runs stock ArbOS, so its blocks, receipts and event logs take the shapes an Arbitrum-family pipeline already reads, and Solidity and Vyper contracts deploy unchanged. Two properties shape how its data is read. The first is the gas token: HYPE bridges 1:1 from HyperEVM as native gas and withdraws 1:1, so native value on Elysium and HYPE on HyperEVM reconcile without a wrapper. The second is the link to HyperCore. About four weeks after mainnet, a network upgrade lets contracts read live HyperCore order books, prices, balances and positions, and place orders on HyperCore through a trade-only agent on the user’s own account, so contract activity on Elysium and market activity on HyperCore become two halves of one flow.

What teams build with Elysium data

Market makers and prop-AMM operators come first: measuring quote refresh behavior and pool activity on Elysium, then comparing it with the HyperCore order book at the same moment using the order book snapshots SonarX publishes. Token launch research is second. A token can launch on an Elysium AMM, deepen on prop-AMM markets, graduate to a HyperCore spot order book and reach a perpetual listing through HIP-3, and each step is readable from decoded transfers and swaps. Treasury, fund accounting and risk teams reconciling HYPE and token movements between HyperEVM, Elysium and HyperCore are third, along with analysts tracking which applications attract activity in the first weeks, when launch flows set the baseline for everything after.

Getting Elysium data from SonarX

Elysium launches on November 9, 2026, and the announcement of SonarX’s day-one support covers what the chain is, why it matters for Hyperliquid and what SonarX will deliver. Tell us the delivery target, the datasets you need and how fresh they have to be, and access is scoped before the first block, so a complete record from block one is in place with no gaps to backfill later. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.

When does Elysium launch, and when will SonarX support it?

Elysium's public mainnet launches on November 9, 2026, with a private mainnet running before then and a testnet live now. SonarX plans to support Elysium from day one, indexing it from the first block and staying live at the tip. Reserve access before launch to have data in place on launch day.

Is Elysium a Layer 2?

Yes. Elysium is an optimistic rollup built on Arbitrum Orbit that settles to HyperEVM and posts its commitments there. An AnyTrust data availability committee keeps the transaction data, and if the committee is ever unavailable the chain posts full data to HyperEVM instead.

What is the gas token on Elysium?

HYPE. It bridges 1:1 from HyperEVM as native gas and withdraws 1:1, with no wrapper asset and no new token to hold in order to transact. HYPE and any ERC-20 on HyperEVM bridge to Elysium permissionlessly, and withdrawals to HyperEVM finalize after the challenge period.

Is Elysium EVM-compatible?

Yes. Elysium runs stock ArbOS, so Solidity and Vyper contracts compile unchanged and Foundry, Hardhat, viem and ethers work as they do on any Arbitrum Orbit chain. Blocks, transactions, receipts and event logs take the shapes an EVM pipeline already reads.

Which Elysium data will SonarX deliver at launch?

Blocks, transactions, failed transactions, receipts, logs, traces, contracts created, token and NFT transfers, priced transfers with USD valuation, approvals, DEX pools and swaps, token metadata and token pricing, delivered as a Snowflake data-share, Kafka streams or file delivery. Balances and API access are enabled on request.

How do Elysium sequencer fees work?

Per the Elysium documentation, 25% of sequencer fees goes to builders, distributed automatically to the contracts that consume Elysium blockspace, 50% buys KNTQ on the open market for the Hyperliquid Assistance Fund, where it is removed from circulation, and 25% funds protocol operations.

Elysium logo

Get Elysium data from SonarX