Skip to content

Current status

Every creation operation was open on mainnet when checked on 23 September 2026. Inscribing single files and batches, sending Zordinals and ZRunes, etching and minting ZRunes, claiming zkMap blocks, and listing and buying on the market were all accepting new orders from a connected wallet. Inscribing, etching, minting and zkMap claims could also be paid from any wallet; sending, listing and buying need your own wallet to sign. Each of them was run end to end on the public Zcash testnet before that release went live.

Availability changes with the chain and the service, so treat the observations below as dated facts, not a promise. The product and https://zordinals.run/api/readiness always say what is open right now.

You will get from this page: the last recorded observations and the endpoints to check current availability. These values came from the product’s public endpoints and were last verified at 2026-11-20T15:37:44Z. They do not establish the current deployment, chain coverage or operation readiness.

FactState
Producthttps://zordinals.run, observed deployed commit f41467301037
Reading the recordWas available when checked at 2026-11-20T15:37:44Z
Chain coverageReported complete: 3,593,506 of 3,593,506 blocks read
Creating and transferringReported enabled
Wallet signingReported unavailable
ZRunes on mainnetReported active

Every row is tied to the recorded verification time. Deployments, chain progress, indexing, wallet qualification and infrastructure availability can change these results. Check the product’s current operation state before creating, signing or paying for an order.

Checking it yourself takes one request, against the same public endpoint this page is generated from:

Terminal window
curl -s https://zordinals.run/api/ready

"ok": true means the service is up and answering right now. Anything else means it is not, and the product will tell you the same thing in plain words when you open it. A healthy answer here does not mean every read is qualified: an answer that needs the complete replayed history can still say it is unavailable (read is not the same as qualified). The indexer’s own view is at the second endpoint:

https://zordinals.run/idx/zcash-metaprotocols/status

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.

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://zordinals.run/api/readiness. The create routes enforce that exact state, so the page and the route cannot disagree. Details.

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 measures activation against its own Zcash node’s height. Reaching activation height is one prerequisite: etching or minting also requires a node level with the network, an open payment or signing path and operation readiness, though not a finished read of the chain. Sending ZRunes also requires current indexed coverage. Activation alone does not establish that an operation can complete. The specification.

ProtocolVersionState
Zordinalsv1Active on mainnet; also reads the pre-existing legacy envelope
ZRunesv1Specified; mainnet activation at block 3,470,000
Collectionsv1Active: parent-by-spend verification live in the product

The honest list of what does not work yet is kept on one page: Known limitations.

The values above live in one data file in this repository. Build checks reject missing fields and snapshots older than the permitted age. Passing those checks does not query the current product or qualify a release. Updating the snapshot requires fresh observations and matching screenshot provenance.

October 24 Grow candidate records local task-search and recovery changes. It is not a deployment or native Testnet acceptance claim.