Skip to content

Protocol Atlas

One row per protocol in the public estate. Each repository is the home of that protocol’s specification; dossier pages on this portal are built from those repositories at pinned commits.

Lifecycle wording follows the shared terminology. A protocol listed here is documented; whether a Universe product currently supports it live is a separate, evidence-backed claim made in that product’s capability matrix, never inferred from this table.

ProtocolCarrier familyRepositoryLifecycle
OP_DROPWitness-data carrier (OP_DROP)op-dropSee repository
BRC-20Inscription (JSON)brc-20See repository
RunesOP_RETURN (runestone)runesSee repository
SRC-20Stamps (bare multisig / OP_RETURN)src-20See repository
SRC-101Stamps namingsrc-101See repository
AlkanesProtorunes / WASM metaprotocolalkanesSee repository
Atomicals and ARC-20Atomicals envelopeatomicals-and-arc-20See repository
TAPInscription (TAP envelope)tapSee repository
BLOCK-20Inscriptionblock-20See repository
DUST-20OP_RETURNdust-20See repository
OP_RETURNData carrier referenceop-returnSee repository
MezcalOP_RETURN (JSON)mezcalSee repository
OrdexOrdinals-based exchange semanticsordexSee repository
ChainbloomGenerative on-chain artworkchainbloomSee repository
Witness CirclesWitness-based membership recordswitness-circlesSee repository
TandemPaired-transaction semanticstandemSee repository
PatinaArtifact provenance layerpatinaSee repository
ProtocolCarrier familyRepositoryLifecycle
TAP on DogeInscription (TAP envelope)tap-on-dogeSee repository
ProtocolCarrier familyRepositoryLifecycle
Zerdinals v1, ZRunes v1, Collections v1Zcash transaction datadocs-zerdinals-and-zrunesSpecified and live at zrunes.io
ProtocolRepositoryStatus
SentrysentryArchived; kept for reference

The carrier-family column above is descriptive orientation, not a specification. The normative rules for each protocol live only in its repository’s specification documents.