Indexed ChilizBlockchain Data
Chiliz Chain carries one asset class on a standalone EVM Layer 1 forked from BNB Smart Chain: fan tokens issued by clubs as CAP-20 contracts and priced in CHZ.
How to query Chiliz data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Chiliz 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 Chiliz 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 Chiliz 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 Chiliz 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 Chiliz activity within seconds
- Fraud and anomaly detection that has to fire before settlement
- Live dashboards and alerting on Chiliz 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
Curated Datasets
Available todayPurpose-built tables
Protocol-level Chiliz datasets modelled for one job, so the decoding and the joins are done before the data reaches you.
- DeFi
Used for:
- Position-level Chiliz lending, swap and liquidity analysis
- Reward, delegation and validator reporting without rebuilding the model
- Token distribution, holder and payment-flow reporting
- Risk and exposure work that needs protocol state, not raw logs
- Skipping the decoding layer an in-house team would have to maintain
- Extending an existing Chiliz share with a modelled slice
Balances
Available todayTables and REST
Read what a Chiliz 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 — on request
- Batch API for wallets, tokens and balances in bulk — on request
Used for:
- Reconstructing Chiliz 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 Chiliz balances on page load
- Compliance checks that read one Chiliz 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 Chiliz 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 Chiliz data behind their own API layer
Chiliz data: frequently asked questions
What is Chiliz?
Chiliz Chain has produced blocks since its mainnet opened in May 2023, and it exists for one asset class: fan tokens issued by football clubs and other sports organizations. It is a standalone Layer 1 rather than a rollup, forked from BNB Smart Chain, which is itself a fork of go-Ethereum, so execution is the EVM against an account model with twenty-byte addresses and the network answers to chain ID 88888. Blocks arrive roughly every three seconds under Proof of Staked Authority, a hybrid of proof of authority and proof of stake in which a small elected validator set signs them. CHZ is the native token and pays gas, and the same asset also circulates as an ERC-20 contract on Ethereum. Fan tokens follow CAP-20, functionally equivalent to ERC-20, so a club’s token decodes with tooling an Ethereum team already runs.
Chiliz data on SonarX
SonarX indexes Chiliz blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances, with each club’s CAP-20 contract carried as an asset of its own. Those records land in the normalized model SonarX uses on every network it covers.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Point-in-time balance tables are available for Chiliz, and the rest can be enabled on request. Kafka streaming can be enabled for Chiliz on request.
How SonarX indexes Chiliz
This chain decodes like an EVM network and reads like a token registry. Most of the state worth querying sits in a long list of small CAP-20 contracts that share bytecode and differ only in name, symbol and issuance, so the work is attribution rather than decoding: a token has to be tied to the organization that issued it before holder counts mean anything. CHZ itself spans two networks, since the gas asset here is also an ERC-20 elsewhere, and any supply figure that reads one side only is wrong.
What teams build with Chiliz data
Token-distribution analysis is the first workload: who holds a club’s token, how concentrated that holding is, and how it moved after each issuance. Treasury and issuance reporting is the second, since an organization that mints an asset has to account for what it sold, what it retained and what came back. Bridge flow analysis is the third, following CHZ between this chain and Ethereum so a supply figure counts each unit once. Consumer wallet analysis turns up as a fourth, because holders here arrive through apps rather than exchanges. Token analytics covers the issuance side across chains, and teams studying community-owned assets often pull ApeChain alongside this one.
Getting Chiliz 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. Chiliz history is available now as a share or a file delivery, and streaming is provisioned on request. 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 Chiliz data API?
Real-time and batch APIs over indexed Chiliz 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 Chiliz 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 Chiliz coverage go?
The historical data-share and file delivery cover the chain from its 2023 mainnet forward, and are available today. Fan tokens that existed before that date lived elsewhere, so a study of a club's token across its whole life is scoped against this chain plus wherever the earlier balances sat. Real-time delivery keeps the same dataset current to chain tip and is enabled on request.
How are fan tokens represented in Chiliz data?
As individual contracts, not as rows of one shared token. Each club issues its own CAP-20 asset, and those contracts largely share bytecode while differing in name, symbol and supply, so decoding is straightforward and attribution is the real work. SonarX keeps every contract distinct rather than merging assets that happen to use the same symbol, which matters when two organizations pick the same short ticker.
