OP Names

Source bitcoinuniverseio/core (private)

Path backend/packages/ecosystem-contracts/lib/protocols.js

Chain bitcoin

Network mainnet

Lifecycle read-only

Verified 2026-09-01

AvailabilityRead-onlyYou can see it but you cannot trade it. Core reads the protocol and shows it; no marketplace mutation is available.

ChainbitcoinOwnership model: utxo. Decimals: none.

Actions supported3 / 13No trading action is declared supported for this protocol.

Feature gateNoneNo gate stands between the shipped build and the actions below.

Execution model

Reads only. No execution path is deployed.

Registry values

Execution mode

read-only

Owning surface

main

Availability

read-only

Feature gate

null

Aliases accepted

op-namesopnames

Address roles

ordinals

Actions

Action	Supported	Mode, or the reason it is not
View	Yes	Reads only. No execution path is deployed.
View collection	Yes	Reads only. No execution path is deployed.
View activity	Yes	Reads only. No execution path is deployed.
List	No	Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410.
Update listing	No	Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410.
Delist	No	Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410.
Buy	No	Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410. The current UI can reach a broadcast step before registration fails, so buy is not declared supported.
Make offer	No	OP Names has no executable offer workflow on this marketplace surface.
Accept offer	No	OP Names has no executable offer workflow on this marketplace surface.
Cancel offer	No	OP Names has no executable offer workflow on this marketplace surface.
Sell	No	OP Names has no executable offer workflow on this marketplace surface.
Settle	No	OP Names has no executable settle authority on this marketplace surface.
Reconcile	No	OP Names has no executable reconcile authority on this marketplace surface.

Why the rest are unavailable

• ListUpdate listingDelist

  Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410.

• Buy

  Legacy random-key/replay marketplace mutations are retired and fail closed; the backend returns HTTP 410. The current UI can reach a broadcast step before registration fails, so buy is not declared supported.

• Make offerAccept offerCancel offerSell

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

• Settle

  OP Names has no executable settle authority on this marketplace surface.

• Reconcile

  OP Names has no executable reconcile authority on this marketplace surface.

Source of truth

Question	What answers it
Which orders exist	Read-only APIV4/legacy marketplace feed
Who owns the asset	No supported mutation authority
Whether a trade settled	No supported settlement registration
What the protocol state is	APIV4 OP Names API with legacy fallback

Indexer

Primary index

APIV4 OP Names API with legacy fallback

Fallbacks

• Legacy API and static sample fallback data

What a mutation must prove

All legacy replay-key mutations are rejected.

Freshness, confirmation, and reorg policy

Policy	Value	What the registry states
Freshness enforced	No	Read sources expose no enforced node-tip/indexer-tip lag contract.
Maximum index lag	not set	No numeric block-lag ceiling is configured for this protocol.
Maximum observation age	not set	No maximum age is configured for an observation used by a mutation.
Listing confirmations	not set	No supported marketplace mutation reaches a confirmed local state.
Settlement confirmations	not set	No settlement depth applies, because no supported action reaches settlement.
Automatic reorg reconciliation	No	The read-only feed has no local lifecycle reconciliation.

Where else this protocol appears

The Bitcoin Universe registry records actions per product surface. Core is the main surface. The others are named here because a reader who cannot do something in Core may be able to do it in a sibling product.

Surface	Actions recorded
Coremain	viewdiscoverview-collectionview-activityview-transaction
Walletwallet	viewsendreceive

Read this alongside

• The support matrix, for how OP Names compares with the other 28 marketplace protocols.
• How to read a protocol row, for what each value on this page means.
• Market safety, before acting on anything here.