Skip to content
Zerdinals and ZRunes
The product mark: a square split by a diagonal, the transparent half filled, the shielded half outlined

The record of what has been written into Zcash

Zerdinals inscriptions, ZRunes, ZRC-20 tokens, and collections, read from the chain by first-party infrastructure and shown with their proof. This is the documentation for the product at zrunes.io.
Open the productWhat this is

Choose your path

Section titled “Choose your path”
I collectStart with the one way people lose these assets, then learn what your addresses hold and how to watch them.
I createInscribe a Zerdinal or etch a ZRune. The flows, the fees, and exactly what is available today.
I buildRead the public HTTP API, the architecture, and the normative protocol specifications.

What you are looking at

Section titled “What you are looking at”

Read from the chain, by us

Every figure on zrunes.io comes from a Zcash node and an indexer the same team operates. Nothing is quoted from a third party and nothing is estimated. Where the chain has not been read in full, the product says so instead of showing an empty catalogue.

The shielded pool is a state, not a gap

An artifact spent into a shielded pool provably exists and cannot be observed. The product records that as a terminal state and never guesses a shielded owner. How that works.

Two ZRC-20 readings, both named

Two independent rule sets read the same blocks and disagree about some tokens. The product computes both, shows both, and marks every figure with the reading it came from. Why.

Honest availability

Creating and transferring require wallet signing that is still gated; the product and these docs say so plainly rather than showing controls that cannot finish. Current status.

Safety in one paragraph

Section titled “Safety in one paragraph”

An inscription or a ZRune balance lives on one specific transparent output, and that output also holds a small amount of ZEC. A wallet that does not know about inscriptions can spend it as a fee or as change, and the asset goes with it. Keep artifact addresses separate from spending addresses, and check what an output carries before you spend it. The sixty-second version.