SonarX

Indexed SiaBlockchain Data

Sia is a proof-of-work storage network whose distinctive record is the file contract: a renter's payment and a host's collateral committed for a term, released only against a storage proof.

Sia logo

How to query Sia data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

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

Sia data: frequently asked questions

What is Sia?

Sia has been running since 2015, and it is a storage market with a ledger attached rather than a smart-contract platform. Blocks are mined under proof of work on a ten-minute target, and the ledger is a UTXO design in the same family as Bitcoin: value sits in outputs, and an address is the hash of the conditions required to spend one rather than of a single key. What makes it different is a third kind of object. A file contract commits a renter’s payment and a host’s collateral for a fixed term, and the host has to post a storage proof to be paid. There are two assets: siacoin, whose block subsidy declines toward a fixed floor so issuance never stops, and 10,000 Siafunds, created at launch, which take 3.9% of every storage payout. The v2 hardfork activated at block 526,000 in June 2025 and changed the transaction format.

Sia data on SonarX

SonarX indexes the objects the protocol actually keeps: blocks and transactions, siacoin and Siafund outputs, file contracts with their terms and collateral, contract revisions and renewals as they reach the chain, storage proofs and the payouts or forfeits that follow, and derived balances. The same normalized model is used on every chain SonarX covers, so storage activity joins to other 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 Sia

A contract’s life is mostly invisible. Renters and hosts revise their agreement between themselves and only the settled state is recorded, so the chain gives you formation, the final revision, and then either a valid storage proof or a forfeited collateral. Reconstructing what a host actually earned means matching those records across the proof window rather than summing transfers. The format change is the other consideration: history written before and after the 2025 hardfork uses two transaction encodings, and a dataset that decodes only the newer one silently loses the first decade.

What teams build with Sia data

Host economics is the first workload: what a provider committed as collateral, what it collected on proof and what it lost by failing one, restated per contract and per period. Storage-price research is the second, because contract terms carry a price for a quantity over a duration, which makes this one of the few public markets where the cost of rented capacity is directly observable. Arweave is the usual comparison there, since it prices permanence once instead. Siafund revenue accounting is the third and depends on following payouts into claims. Treasury reconciliation is the fourth, and wallet analytics covers the address-level side of that work across chains.

Getting Sia 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. Say whether contracts have to be reconstructed across the format change, because that decision shapes the backfill. 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 Sia data API?

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

The historical data-share and file delivery cover the chain's recorded history, which has run since 2015, and are available today. The v2 hardfork activated at block 526,000 in June 2025 introduced a new transaction format, so a complete history spans two formats and continuity across that boundary is part of what gets checked when the share is scoped.

What does the Sia blockchain record about stored data?

The agreement rather than the traffic. A renter and a host form a file contract that is recorded with its terms, its funding and the host's collateral, and the host later has to post a storage proof over a challenged part of the data to collect. Most of the relationship happens off chain and only the final state of a contract reaches a block, so the chain shows commitments, payouts and failures.

How do Siafunds appear in Sia data?

As a second asset with its own outputs. Only 10,000 Siafunds exist, all created when the network launched, and 3.9% of every storage-related payout is set aside for their holders. That share accrues and is claimed rather than streamed, so revenue attribution means following contract payouts into the claim outputs they generated rather than reading a balance.

Sia logo

Get Sia data from SonarX