SonarX

Indexed ConstellationBlockchain Data

Constellation is a network whose ledger is a directed acyclic graph: a global layer orders snapshots for DAG while metagraphs above it keep their own validators, state and tokens.

Constellation logo

How to query Constellation data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

Query Constellation 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 Constellation 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 Constellation 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 request

REST over the indexed dataset

Query indexed Constellation 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 Constellation data behind their own API layer

Constellation data: frequently asked questions

What is Constellation?

Constellation is a network whose ledger is a directed acyclic graph rather than a chain of blocks. A global layer runs consensus over the whole network and keeps the ledger for DAG, the native currency, while metagraphs sit above it: application networks with their own validators, state and often their own token, submitting snapshots to the global layer instead of executing there. Validator selection turns on a reputation model the project calls Proof of Reputable Observation, and a hybrid validator node runs both the global layer and the currency layer beside it. Progress is measured in snapshots and global snapshot epochs, taken incrementally so that catching up does not mean downloading a full one, and a fork resolves as the state of the graph most validator nodes accept.

Constellation data on SonarX

SonarX indexes what the network records: global snapshots and their epochs, currency transactions with their fees, metagraph snapshot submissions, validator participation and rewards, and derived address balances. Everything is normalized into the model SonarX uses across every network it covers, so a graph-structured history can be queried with the same SQL as a block-structured one.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

How SonarX indexes Constellation

There is no height to index on, so the ordering has to come from the snapshots themselves. A pipeline built for linear blocks assumes one parent per unit and one canonical tip; here the unit is a snapshot, several can be in flight, and the accepted state is the one a majority of validator nodes observe. Incremental snapshots make the record a series of deltas rather than of complete states, so reconstructing balances at an epoch means replaying from the last full snapshot forward. Metagraphs add the second dimension, because a holder’s position can be denominated in a token the global layer never accounts for, and that has to be said rather than assumed.

What teams build with Constellation data

Holder and distribution analysis is the first workload: balances and transfers of the native currency over time, which is the part of the network with one authoritative ledger. Validator and reward accounting is the second, reconstructing what participation earned per epoch. Data-provenance research is the third and the one specific to this design, since the question is which metagraphs submitted what, and when, rather than what a transfer moved. RWA and tokenization analytics is the solution area this work sits in, Hedera is the usual comparison for a network that does not order into blocks, and Provenance is the one for regulated record-keeping.

Getting Constellation 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. Constellation history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether a specific metagraph is in scope, because that is a different question from the global ledger. 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 Constellation data API?

APIs over indexed Constellation 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 Constellation 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 Constellation coverage go?

The historical data-share and file delivery cover the network's recorded snapshot history, and are available today. The network has been through more than one major protocol version, so a long series has to be read against the architecture of its era rather than as one uniform sequence, and depth is confirmed when the share is scoped.

Does Constellation have blocks?

Not in the usual sense. The ledger is a directed acyclic graph, and progress is recorded as snapshots ordered by the global layer rather than as a single chain of blocks. Where another chain has a height, this network has a snapshot ordinal and an epoch, and even a fork resolves as the state of the graph a majority of validator nodes accept rather than as the longest chain.

What is a metagraph, and is its data part of this dataset?

A metagraph is an application network that runs on top of the global layer with its own state, its own validators and often its own token, submitting snapshots upward. The global layer records those submissions and the movement of DAG, the native currency, so a metagraph's internal state is not automatically part of a global view. Tell us which metagraph matters and we will confirm what can be covered.

Constellation logo

Get Constellation data from SonarX