Indexed Canton NetworkBlockchain Data
Canton is a network of Daml applications that keep their contracts private to the parties involved and settle across one shared layer, the Global Synchronizer, where Canton Coin pays for traffic and funds rewards.
How to query Canton data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Canton 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 Canton 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 Canton 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
Realtime API
Enabled on requestREST over the indexed dataset
Query indexed Canton 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 Canton data behind their own API layer
Canton data: frequently asked questions
What is Canton?
Canton is a network of applications that keep their state private and still settle with each other. Applications are written in Daml, Digital Asset’s smart contract language, and each contract is visible only to the parties that hold rights or obligations under it. Coordination between applications runs through the Global Synchronizer, a shared layer operated by a set of Super Validators that orders and timestamps the messages passing between parties without reading them. Canton Coin (CC) is the network’s native token. It pays for traffic on the Global Synchronizer, and the network issues it in rounds as rewards to the validators that run the infrastructure and the application providers whose activity uses it.
Canton data on SonarX
SonarX indexes the public side of the network: Canton Coin transfers and balance changes, coin locks and their release, the opening and closing of each issuance round, Canton Coin pricing by round, and the rewards paid to validators and application providers. The same normalized model covers every network SonarX indexes, so Canton Coin activity can be read next to the other settlement networks in one query.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.
How SonarX indexes Canton
Canton has no public ledger of every transaction, and that shapes what can be indexed. Application contracts are private to their parties by design, so SonarX does not reconstruct them. The Canton Coin layer is public, and it is accounted for in rounds rather than blocks: each round carries its own coin price and reward parameters, and rewards are recorded as claims against a round before they become spendable coin. SonarX keeps the round on every record, so supply, fees and operator rewards reconcile round by round.
What teams build with Canton data
Canton Coin supply analysis is the first workload: how much was issued in each round, how much was spent on traffic, and how much is locked at any point. Operator reward accounting is the second, following what validators and application providers earned round by round. Treasury and settlement reporting is the third, for institutions that hold or move Canton Coin and need an independent record of those movements. Tokenization covers the asset side across chains.
Getting Canton 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. Canton history is available now, and real-time delivery 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.
What Canton data does SonarX index?
SonarX indexes the public activity that settles on the Global Synchronizer: Canton Coin transfers and balance changes, coin locks and their release, the opening and closing of each issuance round, Canton Coin pricing by round, and the rewards paid to validators and application providers. Private application contracts stay private to their parties and are not part of the public record.
How do I get Canton 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.
Why can't SonarX see every Canton transaction?
Because Canton is built to prevent that. A Daml contract is visible only to its stakeholders, and the Global Synchronizer orders and timestamps encrypted messages without reading what they contain. What is public is the Canton Coin layer that pays for that traffic and rewards the operators, and that is the layer SonarX indexes.
What is a Canton round?
A round is the issuance interval for Canton Coin. Each round opens with its own coin price and reward parameters and closes once its rewards are settled, so issuance, fees and rewards are all accounted for per round rather than per block. Analysis of Canton Coin supply or operator income is therefore round-shaped.
Is Canton an EVM chain?
No. Canton applications are written in Daml, a smart contract language built around parties, rights and obligations, and the network does not run the Ethereum Virtual Machine. Addresses, contracts and events follow Canton's own model rather than Ethereum's, so Canton data is modeled as its own network.