Token pages
Source and verification
- Owning repository
- bitcoinuniverseio/stampdex (private application source)
- Source path
- frontend route manifest, deployment resolution
- 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
For: anyone considering a trade. Goal: open the right token, read its identity, and read its book. Prerequisites: none. Chain and network: Bitcoin mainnet. Safety: reading only.
The address that means one token
Section titled “The address that means one token”https://stampdex.fun/trade/src20/KEVIN/23765f9bc6b87e078b1f93ed213f90b9004998336575f726e46f34ddbea5e5f3Ticker plus deployment transaction. That is the link Copy link gives you, the link the tab title and the shared card describe, and the link a market row opens. Send it to somebody and they open the token you were looking at.
The shorter /trade/src20/KEVIN still works, and so does
/trade/src20/by-tx/<deploy transaction> when you have a transaction and no ticker.
Both resolve before a market is shown.
The seven resolution states
Section titled “The seven resolution states”Only one of them opens a market.
| State | What happened | What you see |
|---|---|---|
loading | The answer has not arrived | A status card |
resolved | The URL named a transaction the index confirms | The trading terminal |
replace | The ticker has exactly one deployment | The address changes to the long form and the market opens |
choose | More than one deployment claims the ticker | Each deployment with its transaction, block, and creator. No market |
unknown | The index answered and holds no deployment for this ticker | Nothing to price, nothing to trade |
unavailable | The index did not answer | A retry. No market |
mismatch | The transaction belongs to a different ticker | A link to that ticker. No market |
unknown and unavailable are never shown as each other. One means nobody deployed
the ticker. The other means StampDEX could not ask.
You cannot buy, sell, or sign anything from a ticker that has not resolved to exactly one deployment.
What the page shows
Section titled “What the page shows”- Identity first. Deployment transaction, deployment block, date, and creator, above the price.
- The order book. Real signed listings, sorted by unit price ascending. Every listing’s unit price times its amount equals its total; the API refuses to serve one where that does not hold.
- Price history. Recorded prices only. StampDEX does not interpolate a curve for a token with sparse trades, so a thin market draws a thin chart.
- Where these numbers came from. A section naming the source of each figure.
- Trades and activity. What actually happened, with transaction ids.
How to verify
Section titled “How to verify”curl "https://stamp.api.bitcoinuniverse.io/api/v1/market/deployments/KEVIN"The response carries a resolution field with the values single, ambiguous,
unknown, or unavailable, matching the states above.
Common failure states
Section titled “Common failure states”| You see | Cause | Recovery |
|---|---|---|
| A chooser instead of a market | Two deployments share the ticker | Pick the deployment you researched |
| “The index did not answer” | The index is unreachable | Retry. The token is fine, the read is not |
| A link to a different ticker | The transaction in your URL deploys something else | Follow the link, or check where your URL came from |