# Protocols

One page per token family BTI measures: how it writes to Bitcoin, how its bytes are attributed, and its live share.

URL: https://blockspace.wiki/protocols/

Every token family [BTI](https://blockspace.wiki/glossary/bti/) measures.

- [Ordinal Sats](https://blockspace.wiki/protocols/ordinal-sats/): The sat family: inscribed sats, bitmaps, sat names and CAT-21 sats. How ord binds files to sats, how BTI books them, and the family's live share.
- [Runes](https://blockspace.wiki/protocols/runes/): Fungible tokens whose messages, runestones, ride an OP_RETURN output. BTI decodes them itself; ord is only its audit oracle.
- [BRC-20](https://blockspace.wiki/protocols/brc-20/): Tick ledgers written as JSON inscriptions, and since 2026-08-11 also on bare OP_RETURN. A BRC-20 mint has two claimants, the sat and the tick. BRC-100 is covered here too.
- [Alkanes](https://blockspace.wiki/protocols/alkanes/): Contract tokens called through protostones inside a runestone. metashrew's trace is the record; every contract that ran claims the bytes.
- [Omni](https://blockspace.wiki/protocols/omni/): The Mastercoin-lineage ledger, TetherUS included. BTI decodes Class C messages in OP_RETURN itself; a ledger token's bytes are its operations.
- [ARC-20 and Atomicals](https://blockspace.wiki/protocols/arc-20-and-atomicals/): Atomicals' fungible ARC-20 tickers, whose units ride sats, and its NFTs (containers and dmitems). One definitional indexer, one quarantine, one named gap: realms.
- [Counterparty](https://blockspace.wiki/protocols/counterparty/): XCP assets, the first blockspace tokens (2014), with Stamps and Counters as subsets: one asset, one claim, however many sources sight it.
- [TAP](https://blockspace.wiki/protocols/tap/): TAP ticks and DMT, catalogued through tap-reader, a mirror of Trac's feed, with two hops of derived trust.
- [SRC-20 and SRC-101](https://blockspace.wiki/protocols/src-20/): SRC-20 ticks written in the Stamps carriers, and SRC-101 names, both catalogued by the stamps adapter.
- [Open Assets](https://blockspace.wiki/protocols/open-assets/): An asset protocol of coloured outputs that BTI decodes itself with a coloured-UTXO walk; B/A 0.72 in the July 2026 measurement run.
- [CoinSpark](https://blockspace.wiki/protocols/coinspark/): A coloured-output asset protocol whose default route moves units with no CoinSpark bytes at all: the most extreme free-ride measurement recorded.
- [EPOBC](https://blockspace.wiki/protocols/epobc/): Colours written into the nSequence field every input already has: zero carrier bytes, the limiting case of the free-ride index.
- [Colu](https://blockspace.wiki/protocols/colu/): Colored Coins 2.0: a coloured-UTXO protocol over two carriers, OP_RETURN and bare multisig, whose identity is a pure function of chain data.
- [SPOOL](https://blockspace.wiki/protocols/spool/): ascribe's edition registry in OP_RETURN, from 2014 to 2017: editions are tokens, pieces are labels, and fuel transactions are enablers.
- [Charms](https://blockspace.wiki/protocols/charms/): A zero-knowledge token protocol whose spells state the resulting charms in the clear; it moved from witness to OP_RETURN, and its Bitcoin-side supply is a lower bound.
- [Pipe](https://blockspace.wiki/protocols/pipe/): A September-2023 OP_RETURN token protocol, the Runes precursor, with art in tapscript; no indexer has ever existed, so BTI's replay is the record.
- [BRC-100](https://blockspace.wiki/protocols/brc-100/): An inscription-borne tick ledger with a two-step transfer; its only mirror died, so BTI was ruled its indexer on 2026-08-11.
- [Mezcal](https://blockspace.wiki/protocols/mezcal/): Runes-lite JSON mezcalstones in OP_RETURN from block 898,750; BTI's decoder transcribes the author's reference indexer, quirks and all.
- [OP-20](https://blockspace.wiki/protocols/op20/): BRC-20's JSON shape on OP_RETURN plus a required credit address; no indexer has ever existed, so BTI's replay is the record.
- [Bitmap](https://blockspace.wiki/protocols/bitmap/): Bitmap districts are labels on inscribed sats: BTI's opi-bitmap adapter adds a source under Ordinal Sats, never a family of its own.

Sources:

- Blockspace Holdings records
- block.space protocols API · https://block.space/api/protocols

Updated: 2026-10-20