SonarX

Indexed CoreumBlockchain Data

Coreum, now branded tx, keeps token policy in the protocol of its Cosmos SDK Layer 1: an issuer can freeze, whitelist or take a commission on a transfer without writing a contract.

Coreum logo

How to query Coreum data with SonarX

Instant Data Share

Available today

Snowflake, and file dumps to your object storage

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

Coreum data: frequently asked questions

What is Coreum?

Coreum has produced blocks since its genesis on 12 March 2023, and it is now branded tx after a merger with Sologenic that the chain’s own governance ratified. What runs underneath is unchanged: validators run CometBFT under proof of stake, accounts are bech32 strings with a core prefix, and the native token is written ucore at the protocol level whatever ticker sits on top of it. Two design choices separate this chain from its neighbors. Tokens issued through its asset module carry features the protocol enforces, so freezing, whitelisting and a commission on every send are configuration rather than contract code. And gas is deterministic: a message costs what its type costs instead of what its execution measures. CosmWasm contracts run beside those modules, and assets bridged from the XRP Ledger circulate here as issuer-scoped denominations.

Coreum data on SonarX

SonarX indexes what the chain records: blocks and transactions with their typed messages, token issuance with the features attached to it, freezes and whitelist changes, commissions taken on transfers, order-book activity from the chain’s own trading module, CosmWasm contract calls, IBC and bridged denominations, staking records, and derived balances. 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.

How SonarX indexes Coreum

Token policy is the thing to plan around. Because the asset module can take a commission on a send, freeze an account or demand a whitelist, the amount debited and the amount credited need not match, and a rejected transfer is often policy rather than a fault, so a transfer table alone misstates both flow and intent. Deterministic gas cuts the other way and makes fees easier: cost follows message type, so spend can be attributed to activity without reasoning about execution. Bridged assets carry issuer-scoped denominations, which is what keeps two tokens with the same symbol apart.

What teams build with Coreum data

Token supply and holder accounting is the first workload, and the issuer controls are what make it non-trivial: circulating supply here depends on which balances are frozen and which accounts were ever allowed to hold the asset. Bridged-asset reconciliation is the second, matching what was locked on the source ledger against what circulates here. Market research on the chain’s own order book is the third, and desks comparing protocol-level venues usually pull Injective into the same warehouse. Validator income accounting is a fourth, and it has to allow for a minimum gas price that moves with block load rather than a fixed fee, so revenue per block is a function of how busy the chain was. Token analytics covers issuance work across chains.

Getting Coreum 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. This history is available now as a share or a file delivery, and streaming is provisioned on request. Say which assets and which bridge routes matter, because that 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 Coreum data API?

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

The historical data-share and file delivery cover the chain's recorded history from its March 2023 genesis forward, and are available today. Major upgrades added new module features over that span, so records written before them carry fewer fields than recent ones, and depth is confirmed when the share is scoped.

Is Coreum the same network as tx?

Yes. The community ratified a rebrand through onchain governance and the network now presents itself as tx, following a merger with Sologenic, but the chain is continuous: the same genesis, the same core address prefix and the same ucore denomination sit underneath the new branding. SonarX indexes one history, and most tooling still shows the older name.

Coreum logo

Get Coreum data from SonarX