Indexed CeloBlockchain Data
Celo is an OP Stack rollup on Ethereum, migrated in 2025 from its own proof-of-stake Layer 1, and the network where a transaction can pay its gas in cUSD instead of CELO.
How to query Celo data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Celo 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 Celo 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 Celo 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 Celo 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 Celo activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Celo 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
Available todayTables and REST
Read what a Celo 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 — on request
- Real-time balances API for latest and historical balances
- Batch API for wallets, tokens and balances in bulk
Used for:
- Reconstructing Celo 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 Celo balances on page load
- Compliance checks that read one Celo 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 Celo 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 Celo data behind their own API layer
Celo data: frequently asked questions
What is Celo?
Celo has produced blocks since its mainnet launch in April 2020, first as a proof-of-stake Layer 1 with an elected validator set running Istanbul BFT. In March 2025 it migrated at block 31,056,500 to an OP Stack rollup that settles to Ethereum and publishes its transaction data to EigenDA, with a sequencer producing one-second blocks. The native asset is CELO, and execution is account-based over twenty-byte addresses. One property survived the move intact: a transaction can pay its gas in a whitelisted ERC-20 instead of CELO by naming the asset in a fee-currency field, which is how cUSD, cEUR and cREAL are spent as gas. Governance controls that whitelist through a directory contract, and low-decimal tokens enter it through adapters.
Celo data on SonarX
SonarX indexes Celo blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, in the normalized model used on every chain SonarX covers.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for Celo, and the rest can be enabled on request. Kafka streaming can be enabled for Celo on request.
How SonarX indexes Celo
Fees are the awkward part. Gas here can be denominated in an ERC-20, so the cost of a transaction means nothing until the fee-currency field has been read and resolved, and some of those addresses resolve to adapter contracts rather than to the token a user thinks they spent. Stablecoin gas also means fee revenue arrives in several assets at once, which no single-column fee model represents. The 2025 migration is the second seam: blocks either side of it were produced by different systems, and the consensus fields the older client wrote are absent from the migrated history.
What teams build with Celo data
Stablecoin flow analysis is the workload this chain was built for, and it needs transfers, balances and the fee currency together, because on Celo the payment and the fee can be the same asset. Token analytics covers the asset side of that across networks. Cost and unit-economics work is the second job: a remittance business here pays in cUSD, so its expense series is denominated in a stablecoin rather than in a volatile gas token. Portfolio reconstruction is the third, and it spans the migration, since a holder’s records run through both the Layer 1 years and the rollup ones. Teams comparing payment-first designs usually look at Tempo beside it.
Getting Celo 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. Celo history and the balance APIs are available now, so a first delivery is provisioning rather than engineering. 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 Celo data API?
Yes. Real-time and batch APIs over indexed Celo data are available today, covering historical and latest balances and wallet, token and balance lookups in bulk. They read from the same indexed dataset as the Snowflake share and the file delivery, so an API answer and a warehouse query agree.
How do I get Celo 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 Celo coverage go?
The historical data-share and file delivery cover Celo from its 2020 mainnet launch forward and are available today, including the years it ran as its own Layer 1 before the March 2025 migration. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
How are Celo transactions that pay gas in stablecoins recorded?
A Celo transaction can name a fee currency, and when it does the gas was paid in that ERC-20 rather than in CELO. Indexed Celo data keeps the named asset beside the fee, so a cost series can be read in whatever was actually spent. Some of those addresses belong to adapter contracts that wrap low-decimal tokens, which is why a fee currency address does not always match a token address.
Did Celo's history restart when it became an Ethereum L2?
No. The migration was a hard fork of the same chain at block 31,056,500 in March 2025, so block numbering continues and the earlier years remain one history with the later ones. What changed is how blocks are made: a sequencer produces them, Ethereum settles them, and the fields the old consensus wrote are no longer part of the record.
