Coverage matrix
This table is generated from the Bitcoin Universe protocol registry, which is itself generated from the protocol contracts module in Core. The operations listed for each protocol are exactly the ones the registry records Inscribe implementing. Nothing here is typed by hand, and the build fails if a page on this site claims an operation the registry does not carry.
- 38protocols in the registry
- 27with a creation surface in Inscribe
- 11with none, so not creatable here at all
Creation is not trading
Section titled “Creation is not trading”A protocol being creatable in Inscribe says nothing about whether it is tradeable in Core, and the reverse is also true. They are separate surfaces with separate availability, and this site never imports one to imply the other.
Of the protocols below, the registry records marketplace availability across four different states, including read-only and feature-gated. None of that changes what you can make here. For trading availability, read the Core documentation on the central platform.
The matrix
Section titled “The matrix”| Protocol | Chain | Creation operations | Released | Workspace |
|---|---|---|---|---|
| Alkanesalkane | Bitcoin | mint | Released | /alkanes |
| ARC-20arc-20 | Bitcoin | deployminttransfer | ReleasedA build must switch it on | /arc20 |
| Atomicalsatomical | Bitcoin | minttransfer | ReleasedA build must switch it on | /atomicals |
| Atomicals NFTsatomicals-nft, atomicals_nfts | Bitcoin | minttransfer | ReleasedA build must switch it on | /atomicals-nfts |
| AVMavm-assets, atomicals-avm | Bitcoin | deploy | Not released | /avm-studio |
| Bitcoin Stampsstamp, btc-stamps | Bitcoin | inscribetransfer | Released, ungated | /stamps |
| Bitmapbitmaps | Bitcoin | transfer | Read-only in Inscribe | None |
| BLOCK-20block-20 | Bitcoin | deployminttransfer | Released | /block20 |
| BRC-20brc-20 | Bitcoin | deployminttransfer | Released, ungated | /brc20 |
| CAT-20cat, cat-20 | Bitcoin | mint | Not released | /cat20 |
| ChainBloomchain-bloom | Bitcoin | inscribe | ReleasedA build must switch it on | /chainbloom |
| Doginalsdoginal | Dogecoin | inscribe | ReleasedA build must switch it on | /tap-doge |
| DRC-20drc-20 | Dogecoin | mint | Read-only in Inscribe | None |
| DROPSdrops-protocol | Bitcoin | inscribetransfer | ReleasedA build must switch it on | /drops |
| DUST-20dust-20 | Bitcoin | deployminttransfer | Released | /dust20 |
| Mezcal | Bitcoin | etchminttransfer | Released, ungated | /mezcal |
| OP_DROPop-drop, opdrop | Bitcoin | deployminttransfer | ReleasedA build must switch it on | /op-drop |
| OP-20op-return, op20, op-20 | Bitcoin | inscribedeployminttransfer | Released, ungated | /op-return |
| Ordinalsordinal, inscriptions, inscription | Bitcoin | inscribetransfer | Released, ungated | /inscribe |
| Realmsrealm, atomicals-realms | Bitcoin | minttransfer | ReleasedA build must switch it on | /atomicals-realms |
| Runesrune | Bitcoin | etchminttransfer | Released, ungated | /runes |
| SRC-101src-101 | Bitcoin | minttransfer | Released, ungated | /src101 |
| SRC-20src-20 | Bitcoin | deployminttransfer | Released, ungated | /src20 |
| Subrealmssubrealm, atomicals-subrealms | Bitcoin | minttransfer | ReleasedA build must switch it on | /atomicals-realms |
| TAPtap-protocol | Bitcoin | deployminttransfer | Released, ungated | /tap |
| TAP on Dogetap-on-doge, doge-tap, tap-doge | Dogecoin | mint | ReleasedA build must switch it on | /tap-doge |
| UNATtap-unat, tap_unat | Bitcoin | transfer | Read-only in Inscribe | None |
Reading the columns
Section titled “Reading the columns”Creation operations are the registry’s own words:
| Operation | What it does |
|---|---|
inscribe | Write content onto the chain as an inscription |
deploy | Create a new token, defining its ticker and supply |
etch | Create a new rune, the Runes equivalent of a deploy |
mint | Claim an amount of an existing token or rune |
transfer | Move an asset you already hold to another address |
Released carries Inscribe’s own production classification. See status and lifecycle for what each state means. In short: released and ungated is available; released means a deployment decides; not released means do not rely on it; read-only means Inscribe recognises the protocol but cannot create it.
Workspace is where the operation lives in the app. Three protocols with a registry surface have no workspace of their own and are handled inside another one, which is noted in the cell.
What is not creatable here
Section titled “What is not creatable here”Eleven protocols in the registry have no creation surface in Inscribe at all. They appear in Bitcoin Universe elsewhere, in discovery and wallet surfaces, but there is no way to make one here:
| Protocol | Chain | Surfaces it does appear on |
|---|---|---|
| Bitcoin | bitcoin | main, wallet |
| Bitcoin Names | bitcoin | main, wallet |
| CAT-721 | bitcoin | main, wallet |
| DMT | bitcoin | main, wallet |
| OP Inscriptions | bitcoin | main, wallet |
| OP Names | bitcoin | main, wallet |
| Ordex | bitcoin | main, wallet |
| Rare Sats | bitcoin | main, wallet |
| Runes (Native) | bitcoin | main, wallet |
| Zerdinals | zcash | main |
| ZRunes | zcash | main |
Provenance
Section titled “Provenance”| Field | Value |
|---|---|
| Registry source | {coverage.provenance.repository} |
| Source path | {coverage.provenance.sourcePath} |
| Source commit | {coverage.provenance.sourceCommit} |
| Snapshot generated | 2026-08-31T08:40:37Z |