コンテンツにスキップ

このページのソース

このページの主張はすべて固定されたリビジョンに紐づいています。検証元のソースを正確に確認できます。

universe-index-atomicals

Universe ARC-20 index and Marketplace v1 authority

リビジョン 670030e50071

固定パスを開く: marketplaceDocs

Universe ARC-20 token explorer feed and the durable Marketplace v1 protocol authority.

Deprecations

Raw

What is scheduled for removal, what replaces it, and what a deprecation does and does not promise.

Universe implementation Verified 2026-08-31 Metadata & Sources

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

このコンテンツはまだ日本語訳がありません。

A deprecated capability still works. It is scheduled for removal, and every deprecation records six things:

  1. The old behavior.
  2. The new behavior.
  3. The effective version.
  4. Migration instructions.
  5. The compatibility impact.
  6. The source evidence.

A deprecation does not promise the old and new behaviors are identical. Read the migration note rather than assuming a rename.

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.

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
  1. A deprecation is announced here and in the changelog feed before removal.
  2. A deprecated route is marked in its OpenAPI document, and CI requires it to name a replacement.
  3. Removal happens in a version, never silently.
  4. Nothing is removed without a documented replacement or an explicit statement that the capability is gone.

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

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.