transparency_latest
The latest hourly PUBLIC transparency attestation (GET /transparency/latest — no auth): a Merkle
root over every wallet balance, the verified total supply, a transaction attestation, the state root,
and the Bridge Ledger root, plus the BSV transaction that anchors the batch. ANCHORING IS BATCHED,
NEVER IMMEDIATE: the attestation's OP_RETURN transaction is usually broadcast within minutes of its
timestamp, and it can take longer when the network is busy. Until then the newest attestation's
top-level bsv_txid legitimately reads the string "pending" — that is the normal in-flight state,
NOT "unanchored" and NOT an error. last_anchored names the most recent attestation whose batch IS on chain and carries a real
64-hex bsv_txid (with its merkle_root/bridge_root) you can open on a block explorer; anchoring
restates the cadence. Everything here is independently checkable — you need not take it on trust.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fees | No | ||
| volume | No | ||
| bsv_txid | No | may read "pending" for ~5h — in-flight, NOT unanchored | |
| tx_count | No | ||
| anchoring | No | ||
| timestamp | No | ||
| state_root | No | ||
| bridge_root | No | ||
| bridge_rows | No | ||
| merkle_root | No | ||
| total_supply | No | ||
| wallet_count | No | ||
| last_anchored | No | newest attestation actually on chain | |
| settlement_root | No | ||
| supply_verified | No | ||
| algorithm_version | No | ||
| settlement_leaves | No |