Indexed RACEBlockchain Data
RACE is an OP Stack rollup in the Superchain built to tokenize and distribute real-world assets, so the contracts that matter on it represent claims on things rather than liquidity pools.
How to query RACE data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query RACE 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 RACE 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 RACE 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 RACE 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 RACE activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on RACE 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 RACE 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 RACE 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 RACE balances on page load
- Compliance checks that read one RACE 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 RACE 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 RACE data behind their own API layer
RACE data: frequently asked questions
What is RACE?
RACE is an Ethereum Layer 2 that has been live since July 2024, built with the OP Stack and joined to the Superchain, the group of chains that share Optimism’s codebase and route a share of their fee revenue to its collective. A sequencer orders transactions into blocks and posts the batches to Ethereum, which settles them, and withdrawals wait out the challenge window before they can be claimed on the L1 side. Execution is the EVM, gas is paid in ETH and the network answers to chain ID 6805. What separates it from the other OP Stack chains is purpose: it was built to tokenize and distribute real-world assets, including trade finance, private credit, real estate and collectibles, so the contracts that matter here represent claims on things rather than liquidity pools.
RACE 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. Issuer and holder activity reads as decoded events.
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 RACE on request. Kafka streaming can be enabled for RACE on request.
How SonarX indexes RACE
An asset-issuance chain puts the interesting records in places a DeFi pipeline does not look. Token contracts here represent claims rather than pools, and they do not share a single interface, so decoding depends on resolving each contract’s own ABI instead of matching a standard one. The OP Stack adds its own record types on top: a system transaction opens every block, deposits arriving from Ethereum have no L2 signer, and each transaction carries an L1 data component in its cost. Keeping those apart from issuer and investor activity stops a holder count from including the chain’s own bookkeeping.
What teams build with RACE data
Holder registers come first. An issuer has to be able to state who holds a tokenized asset at a given block, which is a point-in-time question rather than a latest-balance one, and it has to survive an audit later. Lifecycle reporting is the second workload: issuance, transfers, restrictions and redemption are separate events, and the record of an instrument is the sequence rather than its current balance. Reconciliation against off-chain registers is the third, since the onchain token is one side of a book kept in two places. This is the work tokenization and RWA solutions cover across chains, and teams comparing venues for it usually pull Plume alongside this one.
Getting RACE 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. RACE coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. 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 RACE data API?
Real-time and batch APIs over indexed RACE 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 RACE 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 RACE coverage go?
The historical data-share and file delivery cover the chain from its 2024 mainnet forward, and are provisioned on request. Because the chain is younger than most rollups, a full backfill is short enough to land in one delivery, which is usually the fastest way to start rather than streaming from the tip and waiting.
Why does RACE data need per-contract ABIs?
Because tokenized-asset contracts do not share one interface the way pool contracts on a DeFi chain do. An issuance, a transfer restriction and a redemption are contract-specific events, so decoding leans on resolving each contract's own ABI rather than assuming a standard. SonarX decodes against the ABI it resolves per contract, which is what keeps issuer actions readable as events instead of raw input data.
