Indexed CelestiaBlockchain Data

Celestia has run since its mainnet beta opened on 31 October 2023, and it sells one thing: a guarantee that data was published. Validators run CometBFT under proof of stake, the same engine as the Cosmos Hub, TIA is the native token and divides into a million utia, and accounts are bech32 strings with a celestia prefix. What separates the chain from its neighbors is what it does not do. Celestia orders data and proves it was available, and it never executes the transactions inside that data. Rollups publish their blocks here as blobs, each tagged with a namespace and paid for by a transaction type that exists for that purpose, then execute and settle wherever they like. The mechanics matter: block data is arranged as a square of shares and extended with two-dimensional Reed-Solomon coding, then committed in namespaced Merkle trees, so sampling a few random shares is enough to be convinced the whole block was retrievable, and an application can download its own namespace while ignoring the rest.

SonarX indexes what this chain records: blocks and the share squares behind them, transactions and their typed messages, blob publications with their namespaces, sizes and commitments, the fees paid for them, staking records, and derived account balances. Everything is normalized into the model SonarX uses across every network it covers, so a publisher’s spend joins to the activity it paid to record.

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

The payload is not the point, because it cannot be read. A blob is opaque bytes addressed by a namespace, so the chain records who published how much data, under which namespace and at what price, and never what those bytes meant. The useful record is the commitment rather than the content: namespaces, share ranges, blob sizes and the fee market for space. Retention is the second consideration: availability is a guarantee about the moment of publication rather than permanent storage, so commitments stay in the chain’s history while payloads need not be kept by everyone, which makes an indexed archive of those commitments the durable artifact.

Cost accounting for a rollup is the first workload: what a chain pays to publish its data, per namespace and per period, which is one of the few genuinely fixed costs an operator can measure. Market research on data availability is the second, studying how fees respond as blocks fill and how much of the square is used, since this is a young market with an observable price. Namespace monitoring is the third, tracking which publishers appear and when they stop, which is a fair proxy for the health of the networks that depend on it. Reward accounting is a fourth, and staking analytics covers that work across chains. Teams comparing where rollups put their data pull Ethereum’s consensus layer into the same warehouse.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Celestia history is available now as a share or a file delivery, and streaming is provisioned on request. If the question is about one publisher’s namespace, say so, because that narrows the backfill considerably. 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.