Indexed StacksBlockchain Data

Stacks has produced mainnet blocks since 14 January 2021, when the network relaunched around Proof of Transfer. Consensus is bound to Bitcoin: miners compete by spending BTC, the winning bid carries a commitment to the next Stacks block inside a Bitcoin transaction, and the STX holders who lock tokens in the protocol’s stacking contract receive those BTC commitments as reward. Contracts are written in Clarity, an interpreted language published on chain as source, decidable by design, with no loops and the ability to read Bitcoin state directly. The native asset is STX, divisible into a million micro-units, and mainnet addresses are c32-encoded, beginning SP for a single signer and SM for a multisig. Reward cycles are counted in Bitcoin blocks rather than in Stacks blocks. The Nakamoto release of October 2024 changed block production so several blocks are made within one tenure, and a BTC-backed asset, sBTC, followed that December.

SonarX indexes blocks and the Bitcoin heights they are anchored to, transactions, contract deployments with their Clarity source, contract calls and the events they emit, fungible and non-fungible asset movements, stacking operations, and account balances. The same normalized model covers every network SonarX indexes, so Stacks records and Bitcoin records can be joined in one query instead of assembled from two pipelines.

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

This chain has two clocks. A block’s place in history is fixed by the Bitcoin transaction that commits it, so ordering and finality depend on a height that lives on another network, and the indexed records carry both. Clarity removes one common problem and adds another: there is no ABI to resolve and no proxy indirection, because source is on chain, but call arguments and post-conditions are typed in the language’s own representation and have to be decoded from it rather than from an event signature. Stacking is the third piece, since the reward leg is a Bitcoin payment and appears nowhere in this chain’s transaction list.

Yield accounting is the workload that defines this chain. Stating what a stacking participant earned means pairing the STX they locked, the cycle it covered and the reward address they nominated with the BTC that actually arrived, which is an accounting exercise across two ledgers rather than a balance read. Bridged-supply tracking is the second, following sBTC issuance and redemption against the Bitcoin held behind it. Contract-level analysis is the third and reads unlike its EVM equivalent, since Clarity source is on chain and asset movements are protocol-level events rather than log entries to decode. Miner economics is a fourth: BTC committed against STX won is a public series on both sides. DeFi analytics is the solution area this work sits in across chains, and Babylon is the usual comparison when the question is about earning on BTC.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Stacks history is available now, and streaming is provisioned on request. Say whether Bitcoin records are in scope too, because the stacking and mining sides of this protocol are only half visible without them. 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.