Indexed Liquid NetworkBlockchain Data

Liquid has produced blocks since 2018 and is a sidechain of Bitcoin, built on Elements, a codebase derived from Bitcoin Core. It inherits the UTXO model and drops the mining: a federation of functionaries proposes blocks in rotation on a fixed one-minute schedule, each block signed by a supermajority of signers, so there is no difficulty adjustment and no reorg to unwind. Two features change what a block contains. Confidential transactions hide the amount in an output and the asset it holds behind a Pedersen commitment, proved valid by a range proof rather than disclosed. And anyone can issue an asset, each getting a 64-character asset ID derived from its issuance transaction, so the chain carries many assets rather than one. L-BTC is the pegged bitcoin that pays fees, and a peg-in becomes spendable after 102 confirmations on Bitcoin.

SonarX indexes blocks and the federation’s signatures over them, transactions with their inputs and outputs, asset issuances and reissuance tokens with their asset IDs, explicit fees, and peg movements in and out. The same normalized model is used on every chain SonarX covers, so this activity joins to Bitcoin and 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. Kafka streaming can be enabled for Liquid Network on request.

Confidentiality decides what a dataset can honestly contain. Most outputs carry a commitment where another chain carries a number, so the indexed record holds the structure, the participants, the script forms and the unblinded fee, and it does not invent an amount the chain never stated. Where a value was published, or where a client shares a blinding key for its own addresses, the amount joins that client’s view rather than the public dataset. Federated signing makes the rest simpler than Bitcoin’s: signed blocks are final, so ingestion appends instead of correcting itself after a reorg.

Issuance monitoring is the first workload: which assets exist, who issued and reissued them, and how often, which is readable in full because issuances are not blinded. Peg accounting is the second and spans two chains, matching bitcoin locked on the Bitcoin side against L-BTC issued here. Settlement reconciliation is the third and belongs to participants: a desk with its own blinding keys can turn its confidential outputs into a ledger it can audit, while the public record confirms the timing and the counterparties. Token analytics covers the asset side of this across networks, and teams studying confidentiality in production usually read Zcash beside it.

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 early whether your workflow depends on amounts, because on this chain that question decides what is possible before delivery format does. 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.