Issue shielded assets on Zcash.
Create an asset, issue its supply, send it or burn it, all from your browser. The supply is public and anyone can check it. The holders stay shielded, the name and image are sealed into the asset id.
Assets on the register
-
live from the public ZSA testnet
The registry
browse all →Your keys.
Your assets. Verifiably.
- 1
Mint
Name your asset, set a supply, attach an image. Cachet builds a real v6 transaction with zero-knowledge proofs and commits it to the ZSA chain.
- 2
Bind
The metadata is hashed into the asset id itself, so the name and image are part of what the asset IS. Nobody, including us, can swap them afterwards - changing either would be a different asset. The registry stores it; the chain guarantees it.
- 3
Verify
Your browser recomputes the asset id from the description it was served - a registry can serve any description, but not one that derives the right id - then re-hashes the metadata against it. Trust the math, not the registry.
- 4
Hold & spend
Your browser downloads public blocks and finds your own notes inside them, on your machine. Nobody is asked which assets are yours - not even us: the registry serves the same bytes to every visitor and cannot tell what you hold.
Read before believing
- Are ZSAs on mainnet?
- Not yet, and not scheduled. It takes a network upgrade.
- What does this site run on?
- The public ZSA testnet, run by QEDIT, not by Cachet.
- What if that testnet is reset?
- Every asset on it is gone, and it has happened more than once. What you sealed is kept, and your seed mints it back under the same asset id.
- So what is real here?
- The proofs, the blocks and the assets: all of it.
We build as if the protocol could ship tomorrow. If it does, Cachet is ready. Every claim above is measured or checkable: read the working paper.