Bitcoin Names

Names claimed by inscription, resolved by first-valid-claim indexing rules.

Chain

Bitcoin

Carrier

Ordinals inscription

Ownership model

utxo

Operations

mint, transfer

Also written

bitcoin-names, domains

Where it came from

Created outside Bitcoin Universe by The Bitcoin names community, 2023.

Where the specification lives

Bitcoin Names has no Bitcoin Universe specification repository. Its specification is Maintained upstream.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-names.

Support in Bitcoin Universe products

Feature gated

Implemented, but switched off unless an operator enables the gate.

Execution model: Built and executed inside Universe products. This surface sits behind the namesMarketplaceV1 feature gate.

Where it appears

• Core: view, view-collection, view-activity, list, update-listing, unlist, buy, make-offer, accept-offer, cancel-offer, settle, reconcile
• Wallet: view, send, receive

Implemented

• viewin-app-execution
• view-collectionin-app-execution
• view-activityin-app-execution
• listin-app-execution
• update-listingin-app-execution
• unlistin-app-execution
• buyin-app-execution
• make-offerin-app-execution
• accept-offerin-app-execution
• cancel-offerin-app-execution
• settlein-app-execution
• reconcilein-app-execution

Not implemented, and why

sell

Bitcoin Names has no executable offer workflow on this marketplace surface.

Operational behaviour

Indexing

State is read from Configured index-names executable Marketplace authority.

What must be true before any change is accepted: Execution requires distinct read and execution credentials, a fresh Names checkpoint, authoritative first-registration ownership, complete inventory, clean funding, immutable economics, and post-sign validation.

Confirmation

Settlement requires the exact confirmed Bitcoin transaction and the authoritative name inscription indexed at a buyer-owned output at stable checkpoints.

Settlement requires at least 1 confirmation.

Reorganisation

The authority continuously reconciles active broadcasts, appends reorg observations, invalidates affected orders deterministically, and preserves funding, broadcast, settlement, and replacement lineage.

Freshness

Every mutation is bound to stable Names, Ord, Bitcoin Core, and complete-inventory checkpoints; deployment readiness must enforce configured checkpoint age and lag limits.

Provenance

Capability facts on this page were generated from backend/packages/ecosystem-contracts/lib/protocols.js in bitcoinuniverseio/core at 15dd03b5986a. Implemented behaviour is not the same as production availability: see how to read our status.