Indexed MetisBlockchain Data
Metis charges gas in METIS rather than ETH and moved block production to a permissioned sequencer pool, so no single operator orders this Ethereum optimistic rollup.
How to query Metis data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Metis 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 — on request
Used for:
- Analytics teams already on Snowflake that want Metis 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 Metis 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
Enabled on requestEvent stream
Consume Metis 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 Metis activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Metis 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
Balances
Enabled on requestTables and REST
Read what a Metis 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 Metis 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 Metis balances on page load
- Compliance checks that read one Metis 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 requestREST over the indexed dataset
Query indexed Metis 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 Metis data behind their own API layer
Metis data: frequently asked questions
What is Metis?
Metis is an optimistic rollup that has settled on Ethereum since 2021, launched under the name Andromeda and built as a fork of Optimism’s original virtual machine. Execution is EVM-equivalent, so Solidity contracts and twenty-byte addresses behave as they do on the L1, and the network answers to chain ID 1088. Gas is paid in METIS, an ERC-20 issued on Ethereum and bridged in, which puts it among the few Ethereum L2s where the fee asset is not ETH. Block production later moved to a permissioned sequencer pool: several sequencers agree under a Tendermint consensus and a threshold-signing module signs the batches sent to Ethereum, so no single operator orders the chain. How those batches reach Ethereum has itself changed more than once, which is the part of the history that matters most to anyone reconciling against the L1.
Metis data on SonarX
SonarX indexes Metis blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Fee fields keep the chain’s own denomination inside the model used on every network SonarX covers.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for Metis on request. Kafka streaming can be enabled for Metis on request.
How SonarX indexes Metis
Metis history arrives in eras and a backfill has to make them agree. The chain began on Optimism’s early virtual machine, so its first records carry that generation’s shapes, and the move to a sequencer pool changed who signs a batch. What gets published to Ethereum has changed as well, so the L1 half of a reconciliation differs depending on the height you stand at. Gas denominated in METIS is the standing adjustment: every fee series here is priced in a bridged ERC-20, so a comparison against an ETH-priced rollup needs a conversion the records do not carry.
What teams build with Metis data
Fee and treasury work comes first here, because the fee asset is the network’s own token: what users spent, what the sequencer set collected and how much METIS crossed the bridge are one connected question rather than three. Position-level DeFi analytics is the second workload, reconstructed from decoded events and internal transfers over long ranges. Bridge flow analysis is the third, following capital between Ethereum and the rollup with both legs of each transfer in view. Teams comparing rollup economics usually pull Mantle alongside this one, since it is the other L2 that priced its gas in a token of its own.
Getting Metis data from SonarX
Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Metis history is available now, with the chain’s earlier and later record formats reconciled into one model. 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.
Is there a Metis data API?
Real-time and batch APIs over indexed Metis data are enabled on request: the same indexed dataset the Snowflake share reads, served over REST once provisioned. Tell us the lookup pattern you need.
How do I get Metis data into Snowflake?
SonarX provisions a data-share into your own Snowflake account. The share appears as a database you query with SQL, so there is no pipeline to build and no second copy to store, and it stays current as SonarX advances the indexing pipeline.
How far back does Metis coverage go?
The historical data-share and file delivery cover the chain from its 2021 mainnet forward, and are available today. That span includes its origins as a fork of Optimism's original virtual machine and the later move to a sequencer pool, and the normalized dataset reconciles those eras rather than starting where the record format settled down.
Is gas on Metis paid in ETH?
No. Fees are paid in METIS, which is issued as an ERC-20 on Ethereum and bridged to the chain, so a cost series here is denominated in a token whose supply also lives on the L1. A model ported from an ETH-priced rollup misprices transactions until the fee asset is swapped, and a full picture of the token needs both chains lined up at the block level.
What changed when Metis moved to a sequencer pool?
Ordering stopped depending on a single operator. A permissioned set of sequencers now agrees on batches under a Tendermint consensus, and a threshold-signing module submits them to Ethereum. For anyone reading the data, block production and batch submission are attributable to a rotating set rather than to one address, so an analysis that keys on the submitter has to allow for the change partway through the history.
