Indexed ProvenanceBlockchain Data
Provenance, the Cosmos SDK Layer 1 Figure Technologies built for regulated finance, records assets as markers with explicit permission grants and metadata scopes that commit to off-chain records.
How to query Provenance data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Provenance 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 Provenance 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 Provenance 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 Provenance 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 Provenance data behind their own API layer
Provenance data: frequently asked questions
What is Provenance?
Provenance has produced blocks since its genesis on 20 April 2021, and Figure Technologies built it to carry real financial assets rather than crypto-native ones. Validators run CometBFT under proof of stake, which gives a committed block immediate finality. The native token is HASH, written on chain as nhash at a billion nhash to one HASH, and accounts are bech32 strings with a two-letter pb prefix. CosmWasm contracts run here, but the chain’s distinctive machinery is its own modules. Markers are asset accounts that carry explicit permission grants over minting, burning and movement. Metadata scopes commit to records kept off chain. Attributes attach attested values to an address, which is how identity and eligibility are expressed. Loan origination and fund administration are the workloads the design was built around.
Provenance data on SonarX
SonarX indexes what this chain records: blocks and transactions with their typed messages, marker creation and the grants attached to it, metadata scopes and the records they commit to, address attributes, exchange orders and holds, sanctions and quarantines, staking and reward records, and derived balances. It all lands in the normalized model SonarX uses across every network it covers, so dollar flows from Noble join to the obligations they settle.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.
How SonarX indexes Provenance
Most of the meaning here sits beside the money. A marker is an account with rules attached, so who may mint, burn or move an asset is state that has to be read alongside the balance it governs. Metadata scopes carry commitments rather than contents, so the chain says a record exists and who signed it and nothing about what it says. Attributes make an address’s standing a matter of record instead of inference. And a transfer can be held, quarantined or sanctioned, so a payment that never settled may have been a decision rather than a fault.
What teams build with Provenance data
Asset servicing reconciliation is the first workload: matching a marker’s supply and the grants over it against the servicing records a fund keeps in its own systems. Portfolio reporting as of a date is the second, because the audience for this chain asks for period-end positions rather than live balances. Evidence assembly is the third and is specific to this chain, since a scope commitment is what ties a document an auditor holds to a moment on chain. Eligibility analysis is a fourth, reading attributes to see which accounts were permitted to hold what and when. RWA and tokenization work spans this chain and MANTRA alike.
Getting Provenance 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. Provenance history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether marker-level or account-level detail leads, because the two are scoped differently. 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 Provenance data API?
APIs over indexed Provenance 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 Provenance 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 Provenance coverage go?
The historical data-share and file delivery cover the chain's recorded history from its April 2021 genesis forward, and are available today. The chain's own modules have been extended repeatedly over that span, so records written under an older module version decode differently from recent ones, and depth is confirmed when the share is scoped.
What is on the chain if the loan documents are not?
A commitment and a pointer. The metadata module records scopes, sessions and records that identify a document and commit to its contents, so the chain establishes that something existed and who wrote it without holding the file. Analysis here describes obligations and their lifecycle, and it cannot read the paperwork sitting behind them.
Can a transfer on Provenance be blocked or held?
Yes, and by design rather than by failure. Assets issued through the marker module carry explicit permission grants, governance can sanction an address, and a recipient can quarantine incoming funds instead of accepting them automatically. A history read as transfers alone will show gaps that were in fact policy decisions.