Drops

Media-first artifacts and agreements recorded through the OP_DROP carrier, including Drop Pacts.

Chain

Bitcoin

Carrier

OP_DROP payloads

Ownership model

hybrid

Operations

drop, pact, transfer

Also written

drops-protocol

Where it came from

An original Bitcoin Universe protocol, published 2025.

The application protocol built on the OP_DROP carrier.

Where the specification lives

The specification and reference documentation for Drops live in bitcoinuniverseio/drops-protocol-docs and are published at https://bitcoinuniverseio.github.io/drops-protocol-docs/. That site is the authority. This page exists so you can find it and compare it with the rest of the estate.

Bitcoin Universe indexes or implements it in bitcoinuniverseio/index-drops-and-opdrop.

Support in Bitcoin Universe products

Feature gated

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

Execution model: Executed through an external venue or protocol service. This surface sits behind the dropsMarketplaceV1 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
• Inscribe: inscribe, transfer

Implemented

• viewexternal-execution
• view-collectionexternal-execution
• view-activityexternal-execution
• listexternal-execution
• update-listingexternal-execution
• unlistexternal-execution
• buyexternal-execution
• make-offerexternal-execution
• accept-offerexternal-execution
• cancel-offerexternal-execution
• settleexternal-execution
• reconcileexternal-execution

Not implemented, and why

sell

DROPS has no executable offer workflow on this marketplace surface.

Operational behaviour

Indexing

State is read from Configured DROPS marketplace v1 authority.

What must be true before any change is accepted: Execution requires distinct read and execution credentials, finalized dual-Core agreement, complete composite inventory, and exact immutable terms.

Confirmation

Settlement is recorded only when the finalized-block scanner verifies the exact intent transaction and custody transition.

Settlement requires at least 1 confirmation.

Reorganisation

Authoritative rollback removes block-bound settlement evidence, marks the intent reorged, and preserves deterministic rebroadcast lineage.

Freshness

Every mutation is bound to the authority finalized checkpoint; operator readiness must still enforce deployment-specific 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.