Indexed ZoraBlockchain Data
Zora, the OP Stack rollup the Zora minting team runs on Ethereum, exists to make issuing media cheap, so its blocks fill with collection deployments, mints and NFT transfers.
How to query Zora data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Zora 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 Zora 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 Zora 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 Zora 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 Zora activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Zora 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 Zora 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 Zora 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 Zora balances on page load
- Compliance checks that read one Zora 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 Zora 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 Zora data behind their own API layer
Zora data: frequently asked questions
What is Zora?
Zora is an Ethereum Layer 2 that has been producing blocks since 2023, built on the OP Stack and operated by the team behind the Zora minting protocol. It is an optimistic rollup: a sequencer orders transactions, batches go to Ethereum for data availability and settlement, and the chain runs the EVM unchanged, with two-second blocks and ordinary twenty-byte addresses. Gas is paid in ETH, and the network has no separate gas token. What makes it worth its own dataset is the traffic. Where a general-purpose L2 fills its blocks with swaps and lending calls, Zora exists to make issuing media cheap, so contract deployments, mints and NFT transfers dominate. Collections are deployed from factory contracts, and each mint carries a small fixed protocol fee divided several ways, between the creator, the parties who referred the collection and the collector, the first minter and Zora itself.
Zora 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 a Zora collection can be compared with the same creator’s activity on another network without reconciling two schemas first.
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 Zora on request. Kafka streaming can be enabled for Zora on request.
How SonarX indexes Zora
An NFT-first chain stresses different parts of a pipeline. New collections appear constantly and are deployed from factories, so ABI resolution has to follow each new contract back to the implementation it copies, or its mints decode as unlabeled calls. ERC-1155 issuance emits single and batch events covering several token IDs at once, so a row count is not a token count. The money is the subtle part. A mint fee does not move to the creator when the mint happens: it accrues to a balance in a rewards contract and is withdrawn later. Creator earnings are what accrued minus what has been claimed, a reconciliation rather than a sum of payments.
What teams build with Zora data
The work here is about people and collections rather than positions. Collector analysis is the common request: which addresses mint early, which follow a creator across collections, and which appear only for one drop, all of which need the full mint history rather than a recent window. Creator revenue accounting is the second, reconstructing what a mint actually paid out once the split is resolved. Marketplace and royalty analysis is the third, following secondary transfers to see whether a collection trades at all after issuance. Wallet analytics covers the address-level side of that work across chains, and teams usually pull Base alongside Zora because collectors move between them.
Getting Zora 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. Zora history is available now, and a collection arrives with its whole mint record rather than a recent window of 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 Zora data API?
Real-time and batch APIs over indexed Zora 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 Zora 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 Zora coverage go?
The historical data-share and file delivery cover the network's recorded history from its 2023 launch forward, and are available today. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
How is NFT mint activity represented in Zora data?
As decoded events plus the value movements behind them. An ERC-721 mint emits one transfer; an ERC-1155 mint can emit a single or a batch event covering several token IDs at once, so counting rows and counting tokens are different questions. The mint fee is split between several parties and accrues to a rewards balance rather than paying out inline, so earnings are read from accruals and later withdrawals.
Is Zora the network or the minting protocol?
Both names are in use. Zora the network is the OP Stack Layer 2 covered by this page. The Zora protocol is a set of contracts for issuing and trading media, and its contracts are deployed on several chains, including Base, so a share of Zora activity is not recorded on the Zora network at all. SonarX indexes each network separately, which is what keeps the two questions apart.