Ordinals

Source bitcoinuniverseio/core (private)

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

Chain bitcoin

Network mainnet

Lifecycle enabled

Verified 2026-09-01

AvailabilityEnabledSwitched on in the shipped build. The actions marked supported below are the ones Core can execute.

ChainbitcoinOwnership model: utxo. Decimals: none.

Actions supported12 / 13Trading actions are declared supported for this protocol.

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

Execution model

Core builds and validates the transaction; your wallet signs it.

Registry values

Execution mode

in-app-execution

Owning surface

main

Availability

enabled

Feature gate

null

Aliases accepted

ordinalinscriptionsinscription

Address roles

ordinals

Actions

Action	Supported	Mode, or the reason it is not
View	Yes	Core builds and validates the transaction; your wallet signs it.
View collection	Yes	Core builds and validates the transaction; your wallet signs it.
View activity	Yes	Core builds and validates the transaction; your wallet signs it.
List	Yes	Core builds and validates the transaction; your wallet signs it.
Update listing	Yes	Core builds and validates the transaction; your wallet signs it.
Delist	Yes	Core builds and validates the transaction; your wallet signs it.
Buy	Yes	Core builds and validates the transaction; your wallet signs it.
Make offer	Yes	Core builds and validates the transaction; your wallet signs it.
Accept offer	Yes	Core builds and validates the transaction; your wallet signs it.
Cancel offer	Yes	Core builds and validates the transaction; your wallet signs it.
Sell	No	Ordinals has no executable offer workflow on this marketplace surface.
Settle	Yes	Core builds and validates the transaction; your wallet signs it.
Reconcile	Yes	Core builds and validates the transaction; your wallet signs it.

Why the rest are unavailable

• Sell

  Ordinals has no executable offer workflow on this marketplace surface.

Source of truth

Question	What answers it
Which orders exist	Universe SQL generic marketplace order book
Who owns the asset	Seller-signed listing PSBT plus exact Ord inscription/output and Bitcoin prevout/outspend agreement
Whether a trade settled	Confirmed exact listed-outpoint spend, signed payout, and indexed buyer inscription receipt
What the protocol state is	Configured Ord server output and inscription views

Indexer

Primary index

Configured Ord server output and inscription views

Fallbacks

• Configured mempool/Esplora providers for UTXO and settlement reads

What a mutation must prove

Every mutation requires one confirmed, unspent, single-inscription output with no co-located Runes; Ord and Bitcoin value/outpoint/owner state must agree.

Freshness, confirmation, and reorg policy

Policy	Value	What the registry states
Freshness enforced	No	Exact state is checked per mutation; the current Ord endpoints expose no numeric tip for a lag comparison.
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	Settlement requires at least one confirmation by default; operators may configure 1-100.
Settlement confirmations	1	A trade is recorded as settled after 1 confirmation.
Automatic reorg reconciliation	Yes	Authoritative Esplora evidence drives deterministic dropped, replacement, conflict, and reorg reconciliation for generic orders.

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-transactionlistupdate-listingunlistbuymake-offeraccept-offercancel-offersettlereconcile
Walletwallet	viewsendreceive
Inscribeinscribe	inscribetransfer

Read this alongside

• The support matrix, for how Ordinals 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.