Provenance labels
Every figure carries exactly one label - onchain, mirrored or hypothetical.
| Label | Meaning | Examples |
|---|---|---|
| onchain | Computed by the pox5-reader contract on mainnet from pox-5 state, at the call or at the coverage-cache refresh that stored it (its burn height is shown). | Coverage for a cycle, headroom, obligation, payout order, reserve, pending pool |
| mirrored | Posted by the publisher from mainnet events, the Hiro API or a price source, and stored with its raw inputs on the testnet risk-feed. | Per-distribution pool and obligation, STX-only yield, anything priced in sats/STX |
| hypothetical | A stress test or what-if, always shown with its assumption. | Stress results, the 3,000 BTC book, cliff prices under assumed inputs |
Rules
- Exactly one label per figure. The API returns it as the
provenancefield of every metric. - Price-based figures are never onchain. The STX/BTC price is not on-chain, so anything that uses it is mirrored or hypothetical.
- The dashboard prefers onchain. When
pox5-readeris unavailable, a headline figure falls back to the latest distribution and saysmirrored.
When a figure comes from events instead of the contract
Some of pox5-reader's read-onlys cannot be called through a public node at all: each call into pox-5 costs about 136k of read length and the endpoint allows 500,000 (Read limits). Where that happens, a figure has two possible origins, and the label always says which:
| Computed by the contract | Summed from events | |
|---|---|---|
| Label | onchain | mirrored |
| How | pox5-reader reads pox-5 state, in a transaction recorded by coverage-cache | The indexer adds up the calculate-rewards events of the distributions concerned |
| Where you see it | Dashboard headline figures, /metrics/current | /metrics/cycles/:n, per-distribution figures in /intervals |
They can differ, for two honest reasons. The windows may not be the same — a whole finished cycle against the current cycle so far — and the contract rebuilds the pool from rewards-per-token × shares, which truncates to within about two sats per interval of the event total. Anything larger than that is a bug, and npm run verify fails on it.