Deprecations
What is scheduled for removal, what replaces it, and what a deprecation does and does not promise.
Universe implementation Verified 2026-08-31
Describes what a Bitcoin Universe service actually does today. It is not a statement about the protocol in general.
- Page ID
-
releases/deprecations - Normative authority
- Universe implementation documentation
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- developer, integrator
- Owner
- bitcoin-universe-docs
- Sources
-
- Universe ARC-20 index and Marketplace v1 authority
at
670030e50071private repository
- Universe ARC-20 index and Marketplace v1 authority
at
Ce contenu n’est pas encore disponible dans votre langue.
The policy
Section titled “The policy”A deprecated capability still works. It is scheduled for removal, and every deprecation records six things:
- The old behavior.
- The new behavior.
- The effective version.
- Migration instructions.
- The compatibility impact.
- The source evidence.
A deprecation does not promise the old and new behaviors are identical. Read the migration note rather than assuming a rename.
Current deprecations
Section titled “Current deprecations”Marketplace legacy purchase alias
Section titled “Marketplace legacy purchase alias”| Field | Value |
|---|---|
| Old | POST /api/marketplace/v1/protocols/{protocolId}/buys |
| New | POST /reservations followed by POST /purchases/prepare |
| Effective | Marketplace v1 |
| Impact | The merged step is separated into reservation and preparation, which is why the replacement is two calls |
| Migration | Migration |
| Evidence | Recorded in the Marketplace v1 contract in index-atomicals |
The alias remains available. New integrations use the replacement.
Marketplace legacy reconcile alias
Section titled “Marketplace legacy reconcile alias”| Field | Value |
|---|---|
| Old | POST /api/marketplace/v1/protocols/{protocolId}/orders/{orderId}/reconcile |
| New | POST /api/marketplace/v1/protocols/{protocolId}/settlements/{orderId}/reconcile |
| Effective | Marketplace v1 |
| Impact | Route move only, under the settlement resource |
| Migration | Migration |
| Evidence | Recorded in the Marketplace v1 contract in index-atomicals |
The sunset policy
Section titled “The sunset policy”- A deprecation is announced here and in the changelog feed before removal.
- A deprecated route is marked in its OpenAPI document, and CI requires it to name a replacement.
- Removal happens in a version, never silently.
- Nothing is removed without a documented replacement or an explicit statement that the capability is gone.
Documentation route compatibility
Section titled “Documentation route compatibility”The earlier standalone documentation files are not deprecated. They are preserved as compatibility artefacts and regenerated from the current content on every build, so they cannot drift from it.
| Route | Status |
|---|---|
/index.html |
Generated, current |
/about.html |
Generated, current |
/guide.html |
Generated, current |
/reference.html |
Generated, current |
/specification.md and /specification.html |
Generated, current |
/sources.md and /sources.html |
Generated, current |
/llms.txt and /llms.html |
Generated, current |
What has never been deprecated
Section titled “What has never been deprecated”Page IDs. A page ID is never reused and never renamed without a redirect, which is why an agent should key on the page ID rather than the URL. See AI and agent access.