Status and lifecycle
The product
Section titled “The product”| Property | Value |
|---|---|
| Lifecycle | Stable |
| Versioning | Continuous. There is no version number to quote; each release is built from an exact commit with recorded evidence |
| Chains | Bitcoin, and Dogecoin protocols behind a release gate |
| Network you can spend on | Bitcoin mainnet |
| Custody | None. Nothing is held on your behalf |
The build you are looking at is named in the footer of every page of the app itself. See release evidence for how a release is sealed and what is checked before one is published.
What “released” means here
Section titled “What “released” means here”Inscribe’s own production contract classifies every protocol surface. This site uses those words rather than inventing softer ones.
| State | What it means for you |
|---|---|
| Released, ungated | Available. Covered by the release health and smoke checks, so if it is broken the release is broken |
| Released | Available in principle. A deployment still decides whether to switch it on, so a given build may have it off |
| Not released | Do not rely on it. The work exists in the codebase and is not finished |
| Read-only in Inscribe | The protocol is recognised and shown in your portfolio, but Inscribe has no workspace for creating it |
Released and ungated
Section titled “Released and ungated”The eleven surfaces the release contract treats as core:
BRC-20, Bitcoin Stamps, Mezcal, OP-20, Ordinals, Runes, SRC-101, SRC-20, TAP.
These cover the everyday cases: inscriptions and collections, BRC-20, Runes, Stamps, SRC-20, SRC-101, TAP, OP_RETURN inscriptions, OP-20 and Mezcal.
Released, but a deployment decides
Section titled “Released, but a deployment decides”ARC-20, Alkanes, Atomicals, Atomicals NFTs, BLOCK-20, ChainBloom, DROPS, DUST-20, Doginals, OP_DROP, Realms, Subrealms, TAP on Doge.
A gated workspace stays visible and reachable by its URL when its flag is off. What stops is reading, writing, payment and order recovery, so the page can be open and still refuse to act. It says which it is. Two surfaces are the exception and return the 404 page instead: Recover Sats, and the Dogecoin BlockPad.
The reason a workspace stays visible rather than disappearing: a missing workspace looks like a product that never had the feature.
Not released
Section titled “Not released”AVM, CAT-20.
These are reachable in the app and are not finished. CAT-20’s transaction features stay fail-closed while the Fractal data and signing dependencies they need are unavailable, and market discovery reports that dependency state directly rather than returning an empty market that looks like an answer. AVM Studio’s editor and academy are usable; deploying a contract is not a released operation.
Alongside them, four workspaces the app carries are also unfinished and are not documented on this site as things you can rely on: Witness Circles, Tandem, Patina, and the RBF operation inside Witness Circles, which is unrelated to the fee-bumping tools that are released.
Recognised but not creatable
Section titled “Recognised but not creatable”Bitmap, DRC-20, UNAT.
These appear in your portfolio, in inscription search, and in the asset inventory for an output. Inscribe has no workspace for making them.
Chains and networks
Section titled “Chains and networks”| Chain | Network | What you can do |
|---|---|---|
| Bitcoin | mainnet | Everything on this site |
| Dogecoin | mainnet | TAP on Doge and Doginals, where a deployment has switched the Dogecoin feature on |
Inscribe also has non-mainnet modes used in development. This documentation describes mainnet, because that is the network where a mistake costs money.
Live service status
Section titled “Live service status”Release state is not the same as whether a source is answering right now. The app reports that itself: the service status panel names each source, the block it has reached against the chain tip, and the workspaces that read it.
Read where the data comes from for the six states a source can be in and what each one blocks.
How this page stays true
Section titled “How this page stays true”The lists above are generated from two data files in this repository, one derived from the Bitcoin Universe protocol registry and one checked against Inscribe’s own production contract. A build fails if a page claims an operation the registry does not record, or if a protocol is marked as unreleased without saying what a reader sees instead.