Supported carriers

Every Bitcoin artifact deserves one clear meaning.

The Drops carrier registry keeps formats distinct, strict, and verifiable. That means an app can support compact artifacts, BIP-110-compatible records, token events, and Pacts without confusing one for another.

One marker+One grammar+One validator=One meaning
dropsGeneric artifact

Exact body, MIME type, creator key, and Taproot proof.

bip110-op-dropCompatibility carrier

A separate strict decoding path preserves its registered meaning.

drops-pact and DPC1Pact records

Immutable Seeds and transition commitments follow their own verification route.

Interoperable by being exact

Compatibility works best when no parser has to guess.

For you, this means the name of a record tells a wallet how to read it. A Drops artifact, an op-drop event like $DROP, the first token on op-drop, and a Pact record stay distinct instead of blending into one confusing data type.

CarrierWhat it carriesWhat stays clear
dropsCompact generic artifactExact body, MIME type, creator key, and Taproot proof.
bip110-op-dropRegistered compatibility carrierIts own strict decoding path, separate from native Drops meaning.
drops-pactImmutable Pact SeedAgreement identity, ruleset, policy, and initial-state commitment.
DPC1Pact transition commitmentCompact pointer to a verified Cell state change and Proof Pack.
Generic DropNot a token

Generic artifacts do not create balances without op-drop validation.

op-drop eventStrict decoder

Token rules stay separate from Pact actions and generic records.

DPC1 commitmentVerified transition

Strict carrier boundaries let products evolve without rewriting an existing Bitcoin record.

BIP-110 ready

Support compatible records without dissolving their boundaries.

The registered bip110-op-drop carrier is available to products that need it. Drops keeps that compatibility explicit: a generic record is not automatically a token, and a token event is not automatically a Pact action.

No accidental token balances: op-drop rules must pass their own strict decoder.
No accidental Pact transitions: a DPC1 commitment must verify against its Cell and Proof Pack.
No retroactive rewriting: a confirmed marker retains the meaning its registered grammar defines.

Clear formats create better experiences

Create a richer Bitcoin record without giving up unambiguous proof.

See how the canonical Drops carrier works, then explore the Pacts and Studio experiences that grow from it.