Troubleshooting
Four questions, in order
Section titled “Four questions, in order”1. Are you on the right address?
Core is at www.bitcoinuniverse.io. The bare bitcoinuniverse.io redirects to
a different Bitcoin Universe application, so a link missing the www will not
show the pages described here.
2. Is it unavailable, or is it empty? These look similar and mean opposite things. A dash is not a zero. An empty table is not a failed read. Reading the numbers takes two minutes and resolves a large share of reported problems.
3. Does the protocol support what you are trying to do? Nine of the 29 marketplace protocols support neither buying nor listing, and thirteen sit behind a feature gate. The support matrix says which, and each protocol page gives the registry’s stated reason.
4. Is the deployment open for trading right now?
curl -s https://api.bitcoinuniverse.io/health \ | jq '{marketplaceProfile, mutate: .mutationTraffic.ready}'A read-only profile means every trading action is closed, whatever the matrix
says. That is gate 3, and it is a property of the running deployment rather
than of the protocol.
By symptom
Section titled “By symptom”| Symptom | Go to |
|---|---|
| A market says unavailable | Market and reader states |
| A figure shows as a dash | Reading the numbers |
| A column I expected is missing | Protocol indexes |
| A wallet will not connect | Wallet and signing problems |
| A control is disabled with a reason | Market and reader states |
| A control is not there at all | The support matrix |
| A balance shows as unavailable | Addresses |
| An asset is missing from Portfolio | Portfolio |
| A purchase was refused over runes | Asset-bearing outputs |
| A settlement is still pending after a block | Confirmation and reorg policy |
| A search returned several results | Search |
| No USD price is shown | Fiat prices |
A 429 from the API | What is public |
A 404 on an API path | The public reader boundary |
Information worth including in a report
Section titled “Information worth including in a report”- The page or route, and the width you saw it at.
- What you observed, and what you expected instead.
- The
X-Request-Idheader, if the problem involved an API call. - The
X-Universe-Releasevalue, so the report is pinned to a build. - Screenshots with any personal data removed.
Never include a seed phrase, a private key, an unbroadcast signed transaction, a session token, or anyone else’s address. None of those are needed to reproduce a defect, and they cannot be un-sent.
Where to send it
Section titled “Where to send it”- A documentation error, a broken link, or a page that does not match the product: open an issue.
- A suspected security issue: report it privately. Do not open a public issue for it.