The Drops protocol

Five values. Four drops. One exact artifact.

The Drops protocol is a compact canonical OP_DROP leaf. The format keeps the artifact body, its hash, and the Taproot proof in one clear Bitcoin commitment.

Read canonical rules Verify a Drop

Marker+MIME+Body hash+Body+Key

dropsCanonical leaf

Marker: drops
MIME: canonical MIME
Body hash: SHA256(body)

Small on purpose

The protocol makes a promise that any compatible verifier can check.

You do not need to read the script below to benefit from it. It gives every wallet and verifier the same simple answer: this is the exact record Bitcoin confirmed, and here is the proof.

PUSH "drops"           OP_DROP
PUSH <canonical MIME> OP_DROP
PUSH SHA256(body)      OP_DROP
PUSH <body, max 256B> OP_DROP
PUSH <x-only pubkey>  OP_CHECKSIG

Canonical

One reading

Fixed order, minimal pushes, bounded body, and explicit MIME type leave no room for a permissive parser to invent meaning.

Immutable

One commitment

The body hash ties the displayed content to the exact bytes committed in the confirmed Bitcoin transaction.

Portable

One ID

The reveal transaction and input index form a stable Drops ID for wallets, explorers, and independent services.

DropsNative artifact

A compact generic artifact has its own grammar and explicit Taproot proof.

BIP-110Separate parser

A compatibility carrier remains distinct from native Drops meaning.

Product layersClear boundaries

Clear carrier boundaries keep product layers interoperable without merging their meaning.

Compatibility without ambiguity

One carrier does not borrow another carrier's meaning.

A generic Drop, an op-drop event, and a Pact record can share an application experience without becoming interchangeable. Each stays attached to its own grammar, parser, and proof rule.

Drops recognizes the bip110-op-drop compatibility carrier through a strict, separate parser. That application compatibility does not promise Bitcoin consensus activation, relay, mining, or third-party support. A compatible marker is never silently treated as a native Drops record, and a generic artifact is never mistaken for a token event.

Drops: compact generic artifact with an explicit Taproot proof.

BIP-110 carrier: a separately parsed compatibility format.

op-drop and Pacts: each adds its own strict grammar and validation path.

Read it. Verify it. Make it yours.

The best protocol is one people do not have to take on faith.

Explore the canonical rules, follow a Drop's proof, or see how the carrier registry keeps Bitcoin artifacts clear.

Verify a Drop See carriers