Size for self-containment
Gave up: large media on chain. Got: an artifact whose content, hash and commitment all arrive together, with no reassembly and no partial states.
Comparison · not a ranking
Compared with adjacent protocols
Every protocol on this page solved a real problem and made a real tradeoff. This page describes those tradeoffs so you can pick the one that matches what you are building. It is not a claim that Drops is better, and it does not describe any of them as insecure.
Attribution first
Of the protocols below, only Drops and OP_DROP originated at Bitcoin Universe. Ordinal inscriptions, BRC-20, Runes, SRC-20 and Atomicals all originated outside this organization, and each is described here as its own ecosystem defines it. Where Bitcoin Universe makes an indexing decision of its own about one of them, that is a Universe decision and is labelled as such elsewhere in the docs platform, not attributed to the protocol's authors.
The axes that actually differ
| Question | Drops | Ordinal inscriptions | BRC-20 | Runes |
|---|---|---|---|---|
| What is recorded | A media artifact or an agreement record | Arbitrary content attached to a satoshi | Token events written as inscribed JSON | Token issuance and transfers |
| Where the data sits | A Tapscript leaf, in the witness | A Tapscript envelope, in the witness | Inside an ordinal inscription | An OP_RETURN output |
| Size of one record | 1 to 256 bytes, hard limit | Effectively bounded by block and standardness limits | Small, bounded by its JSON | Small, bounded by the OP_RETURN |
| Identity comes from | The reveal transaction and input index | Inscription identity plus satoshi tracking | The underlying inscription | An assigned rune identity |
| Ownership follows | Output 0, by explicit rule | The satoshi, by ordinal theory | The inscription's satoshi | Protocol-defined output allocation |
| Commitment check | Required: the leaf must be the leaf the spent output committed to | Envelope recognition within the reveal | Inherited from the inscription layer | Output parsing, no Taproot commitment involved |
| Mempool view | None for artifacts | Commonly shown by indexers | Commonly shown by indexers | Commonly shown by indexers |
| Protocol | Origin | Carrier | The distinctive choice |
|---|---|---|---|
| SRC-20 | Bitcoin Stamps ecosystem, outside this org | Data encoded in transaction outputs | Storing data in outputs rather than the witness makes it unprunable, at a much higher cost per byte. |
| Atomicals and ARC-20 | Atomicals ecosystem, outside this org | Tapscript envelope with a coloured-coin model | Ties token units to satoshis directly, so a unit is a satoshi rather than a ledger row. |
| OP_DROP | Bitcoin Universe | The same five-push leaf as Drops, marker 6269703131302d6f702d64726f70 (OP_DROP marker hex) |
Shares the carrier and nothing else: a token ledger with two-stage transfers. See the summary. |
The three tradeoffs Drops made
Convention for commitment
Gave up: the ability to recognise a record from the reveal alone. Got: a proof that the record was committed in advance by the output that was spent, rather than merely present in a witness.
Immediacy for finality
Gave up: a pending view. Got: a record set with no state that can evaporate, and no interface temptation to show unconfirmed activity as though it counted.
Choosing between them
| If you need | Consider |
|---|---|
| A large image or file recorded on chain | An inscription-style protocol. Drops cannot do this and does not pretend to. |
| A small artifact whose commitment you can verify from one transaction | Drops. |
| A fungible token with a large existing ecosystem | BRC-20 or Runes, depending on your indexer and wallet requirements. |
| A fungible token with strict two-stage transfers and a published decision path | OP_DROP. |
| An agreement whose terms and enforcement boundary are both on chain | Drop Pacts, keeping the reference-only boundary in view. |
| Units that are satoshis | An ARC-20 style coloured-coin model. |
| Data that survives even aggressive witness pruning | An output-based protocol such as SRC-20, at a higher cost. |
One thing that is not a tradeoff
Whatever protocol you choose, verify the implementation you rely on rather than the specification you read. Two indexers for the same protocol can disagree, and the one your money depends on is the one whose rules matter. That advice applies to Drops as much as to anything on this page.