Current status
You will get from this page: the authoritative answer to what works today. Every other page that mentions availability defers to this one. Values come from the product’s public endpoints and were last verified at 2026-08-31T22:49:23Z.
The product today
Section titled “The product today”| Fact | State |
|---|---|
| Product | https://zrunes.io, deployed commit 618800fbfc62 |
| Reading the record | Was available when checked at 2026-08-31T22:49:23Z |
| Chain coverage | Complete: 3,467,533 of 3,467,534 blocks read |
| Creating and transferring | Disabled, pending wallet signing qualification |
| Wallet signing | Not yet available in any wallet |
| ZRunes on mainnet | Not yet active; activation is at block 3,470,000 |
Which of these rows can go out of date
Section titled “Which of these rows can go out of date”Most rows above change only when someone ships a change, so a dated reading of them stays true until the next one. Reading the record is not one of those. It is a live condition: the product depends on infrastructure that can be down for maintenance or under load, and when that happens the site says so on the page itself rather than pretending. So treat that row as an observation with a timestamp, not as a promise about this minute.
Checking it yourself takes one request, against the same public endpoint this page is generated from:
curl -s https://zrunes.io/api/ready"ok": true means the record is readable right now. Anything else means it is
not, and the product will tell you the same thing in plain words when you open
it. The indexer’s own view is at the second endpoint:
https://zrunes.io/idx/zcash-metaprotocols/statusWhat each row means
Section titled “What each row means”Reading the record
Section titled “Reading the record”Browsing, searching, and inspecting artifacts, tokens, collections, addresses, blocks, and transactions. This is the product’s core and it is read-only: nothing about reading requires a wallet.
Creating and transferring
Section titled “Creating and transferring”Each create page states, in one place before its first control, whether that operation is open and what is holding it if not. The form appears only when the deployment will accept the order it produces, so no control pretends an action can finish when it cannot, and nothing is created, signed or broadcast while a flow is closed.
The product publishes the same answer the pages read, one state per
operation, at https://zrunes.io/api/readiness. The create routes enforce
that exact state, so the page and the route cannot disagree.
Details.
ZRunes activation
Section titled “ZRunes activation”The ZRunes protocol ignores mainnet data outputs below its activation height by rule, so before that height nothing can be etched or minted and no ZRune exists. This is a protocol fact that any independent node reading the chain reproduces, not a setting on the product’s side.
The product reads the height from its own indexer rather than holding it as a constant, and the ZRune pages state the exact block and how many remain. When the height arrives those pages open on their own: there is nothing to install and nothing to redeploy. The specification.
Protocol versions
Section titled “Protocol versions”| Protocol | Version | State |
|---|---|---|
| Zerdinals | v1 | Active on mainnet; also reads the pre-existing legacy envelope |
| ZRunes | v1 | Specified; mainnet activation at block 3,470,000 |
| Collections | v1 | Active: parent-by-spend verification live in the product |
Known limitations
Section titled “Known limitations”The honest list of what does not work yet is kept on one page: Known limitations.
How this page stays true
Section titled “How this page stays true”The values above live in one data file in this repository. A build fails if any field is missing, undefined, or stale, so an outdated status cannot ship silently. When the product changes, one reviewed change to that file updates every page that references it.