OP_DROP

Source bitcoinuniverseio/core (private)

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

Chain bitcoin

Network mainnet

Lifecycle feature-gated

Verified 2026-09-01

AvailabilityFeature-gatedImplemented, but switched off unless an operator enables its feature gate. Treat it as unavailable until you can see it working.

ChainbitcoinOwnership model: hybrid. Decimals: none.

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

Feature gateopDropTradingEvery action below stays closed until an operator enables this gate.

Execution model

An external marketplace or provider owns the order book and the execution path; Core routes to it.

Registry values

Execution mode

external-execution

Owning surface

main

Availability

feature-gated

Feature gate

opDropTrading

Aliases accepted

op-dropopdrop

Address roles

paymentordinals

Actions

Action	Supported	Mode, or the reason it is not
View	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
View collection	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
View activity	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
List	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Update listing	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Delist	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Buy	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Make offer	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Accept offer	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Cancel offer	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Sell	No	OP_DROP has no executable offer workflow on this marketplace surface.
Settle	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.
Reconcile	Yes	An external marketplace or provider owns the order book and the execution path; Core routes to it.

Why the rest are unavailable

• Sell

  OP_DROP has no executable offer workflow on this marketplace surface.

Source of truth

Question	What answers it
Which orders exist	Durable OP_DROP listings, funded offers, reservations, action intents, request journal, history, and settlement rows in the configured OP_DROP authority
Who owns the asset	Confirmed OP_DROP balance and custody projection, Bitcoin Core prevout agreement, exact BIP-322 actor authorization, and transferability checks
Whether a trade settled	Exact jointly signed PSBT template, post-sign validation, Bitcoin broadcast, finalized-block settlement, and deterministic rollback
What the protocol state is	Configured OP_DROP marketplace v1 authority

Indexer

Primary index

Configured OP_DROP marketplace v1 authority

Fallbacks

None. If the primary index cannot be read, this protocol has nothing to fall back to and the page says the read failed.

What a mutation must prove

Execution requires distinct read and execution credentials, a fresh authoritative checkpoint, exact immutable economic terms, and a compatible durable schema.

Freshness, confirmation, and reorg policy

Policy	Value	What the registry states
Freshness enforced	No	Every mutation is bound to the authority checkpoint; operator readiness must still enforce deployment-specific lag limits.
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 is recorded only when the finalized-block scanner verifies the exact intent transaction and OP_DROP custody transition.
Settlement confirmations	1	A trade is recorded as settled after 1 confirmation.
Automatic reorg reconciliation	Yes	Authoritative rollback removes block-bound settlement evidence, marks the intent reorged, and preserves deterministic recovery and rebroadcast lineage.

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	deployminttransfer

Read this alongside

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