Indexed ModeBlockchain Data
Mode is an OP Stack rollup in the Optimism Superchain where a developer can register a deployed contract and hold a transferable claim on the sequencer fees that contract produces.
How to query Mode data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Mode 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 Mode 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 Mode 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 Mode 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 Mode activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Mode 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 Mode 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 Mode 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 Mode balances on page load
- Compliance checks that read one Mode 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 Mode 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 Mode data behind their own API layer
Mode data: frequently asked questions
What is Mode?
Mode is an Ethereum Layer 2 built on the OP Stack, part of the Optimism Superchain, and open to the public since January 2024. It is an optimistic rollup: a sequencer orders transactions into two-second blocks and posts them to Ethereum, which holds the data and settles the chain. Execution is the EVM, unchanged, with the usual twenty-byte addresses, and gas is paid in ETH. MODE, introduced in 2024, is a separate token and does not pay for transactions. What distinguishes the network is where fee revenue goes. Through its fee-sharing system a developer registers a deployed contract and receives a transferable token representing the claim on the sequencer fees that contract produces; the accrued balance is withdrawn by whoever holds that token at the time. The chain’s own blocks start in late 2023, a few months before the public launch.
Mode data on SonarX
SonarX indexes blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so Mode sits beside the other Superchain networks in one dataset instead of one pipeline each.
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 Mode on request. Kafka streaming can be enabled for Mode on request.
How SonarX indexes Mode
Revenue attribution on this chain is a graph problem, not a column. Fees earned by a contract accrue to a claim that is held as a token and can be sold, so the address that deployed a contract is not necessarily the address that collected from it, and an answer to who earned what is only correct if the claim’s ownership history is indexed alongside the fee accruals and withdrawals. The chain’s start needs care too: blocks exist from late 2023, months before the launch that brought users, so any activity baseline drawn from the first blocks is measuring an empty chain rather than a quiet one.
What teams build with Mode data
The recurring workload is application economics. A team running a protocol here can measure what its own contracts generated, what was withdrawn against that, and how the two diverge over a quarter, which is a reporting question rather than a research one. Position-level DeFi analytics is the second, since lending and yield strategies are the bulk of what the chain hosts and their state lives in decoded events. Cross-chain user analysis is the third: the same wallets appear on Optimism and the other Superchain networks, and following one user across them is only possible when the chains sit in one schema. Analysts on the outside read the fee-sharing registrations as a signal of which contracts a team expects to matter, which is a fourth. Treasury reporting draws on the same records.
Getting Mode 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. Mode history is available now, including the quiet months of blocks that precede the public launch. 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 Mode data API?
Real-time and batch APIs over indexed Mode 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 Mode 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 Mode coverage go?
Back to the chain's first blocks, which predate the public launch: Mode began producing blocks in late 2023 and opened to users in January 2024, so the earliest weeks are quiet rather than absent. The historical data-share and file delivery cover that history and are available today, with real-time delivery provisioned on request.
How does Mode's fee sharing appear in the data?
As registrations, accruals and withdrawals rather than as payments inside each transaction. A developer registers a contract with the fee-sharing system and receives a token representing the claim on that contract's share; fees build up as a balance and are withdrawn separately. Because the claim is transferable, working out who earned a contract's fees over a period means following that token's ownership, not the deployer address.
Is Mode part of the Optimism Superchain?
Yes. Mode runs the OP Stack and is governed as part of the Superchain, which is why its blocks, receipts and deposit transactions have the same shape as Optimism's and Base's. That makes cross-chain comparison cheap, and it also means an address or a contract can exist on several of these chains at once, so the chain identifier has to travel with every row.