Data provenance
Source and verification
- Owning repository
- bitcoinuniverseio/core registry, and bitcoinuniverseio/stampdex for the client map
- Source path
- MARKETPLACE_PROTOCOL_REGISTRY sourceOfTruth and indexer entries
- Applicable release
- continuous deployment, verify with GET /api/version
- Chain and network
- bitcoin / mainnet
- Lifecycle
- stable
- Last verified
- 2026-09-01
- This page
- Edit on GitHub · Bitcoin Universe platform
StampDEX names the source behind every number it shows. This page says where each kind of data comes from, and how to check for yourself.
The map
Section titled “The map”| Data | Source | Operated by |
|---|---|---|
| Bitcoin chain data: UTXOs, fee rates, block height, transaction status, broadcast | Universe Bitcoin node API | Universe |
| Listings, orders, and trades made on StampDEX | The StampDEX database | Universe |
| Stamps and SRC-20 index: deployments, supplies, holders, stamp metadata | stampchain.io | A third party |
| Collection and trait metadata | stampchain.io | A third party |
| Stamp artwork | stampchain.io, cached and thumbnailed by the StampDEX media cache | A third party, served through Universe |
| Token logos | OpenStamp and a wallet icon service, resolved server side and cached | Third parties |
| Counterparty compose for stamp trades | Counterparty API | Universe-operated node |
Bitcoin chain reads use Universe-operated services only. When that node is unreachable, the affected reads fail rather than quietly switching to another provider. Changing provenance without saying so would defeat the point of naming sources at all.
What the registry records
Section titled “What the registry records”The Bitcoin Universe ecosystem registry records the source of truth for each protocol independently of the product’s own description. This is the platform’s record, not StampDEX’s.
Bitcoin Stamps
Section titled “Bitcoin Stamps”| Question | Answered by |
|---|---|
| What is for sale, and at what price | StampDEX Counterparty dispenser order book |
| Who owns it | StampDEX/Counterparty indexer-backed compose validation plus wallet PSBT signatures |
| Whether a trade completed | StampDEX Counterparty dispense composition and Bitcoin broadcast |
| Protocol state | StampDEX and Stampchain |
| Primary index | StampDEX and Stampchain |
| Fallback sources | OpenStamp for reference metadata |
| Freshness policy | Universe does not enforce a StampDEX-versus-chain lag threshold. |
| Confirmation policy | Confirmation policy is delegated to StampDEX/Counterparty. |
| Reorg policy | Universe relies on StampDEX/Counterparty state and has no local rollback worker. |
SRC-20
Section titled “SRC-20”| Question | Answered by |
|---|---|
| What is for sale, and at what price | StampDEX SRC-20 order book |
| Who owns it | StampDEX one-time action challenge, seller listing PSBT, and indexed SRC-20 collateral checks |
| Whether a trade completed | StampDEX fill/confirm endpoints plus wallet Bitcoin broadcast |
| Protocol state | StampDEX |
| Primary index | StampDEX |
| Fallback sources | Stampchain activity; OpenStamp mint/deploy reference data |
| Freshness policy | Universe does not enforce a StampDEX-versus-chain lag threshold. |
| Confirmation policy | Confirmation policy is delegated to the StampDEX fill workflow. |
| Reorg policy | Universe retains broadcast receipts but delegates chain reconciliation to StampDEX. |
Two things in those tables deserve saying in plain words.
The order book depends on the Counterparty data layer. For stamps, the order book is the StampDEX Counterparty dispenser order book and ownership resolution is indexer-backed through StampDEX and Counterparty. If that data layer is wrong or behind, the venue is wrong or behind with it.
Universe does not cross-check the provider against Bitcoin. The registry records, for both protocols, that Universe allowlists and validates the exact request it forwards, and that StampDEX or Counterparty validates the underlying state, but that Universe does not compare the provider’s chain tip against Bitcoin’s own tip.
The third-party dependence, stated plainly
Section titled “The third-party dependence, stated plainly”The Stamps and SRC-20 index StampDEX reads is stampchain.io, run by the Bitcoin Stamps project. StampDEX does not hide this. Market rows carry a source object naming the origin of each number, and the status endpoint names the operator.
A Universe-operated Counterparty node is syncing. Until it is ready and a Universe stamps index runs on top of it, index reads stay on stampchain.io. This page will change when that changes.
Check it live
Section titled “Check it live”curl https://stamp.api.bitcoinuniverse.io/api/v1/indexer/statusThe answer names the mempool source, the stamp index source and its lag behind the
Bitcoin tip, the per-kind sources for index, collections, and media, and an operator
field that reads universe only when every stamp source is a Universe host. It also
states the freshness in plain words.
There is a per-transaction version too, which traces a single transaction through signed, broadcast, mempool, confirmed, and indexed. See Status and version.