Ecosystem

A snapshot of what is deployed, what is shipping, and what is open. This page is updated as the project moves.

Status

Component	State
Zcash testnet	Active. Registrations open, marketplace working, OTP verification working.
Zcash mainnet	Beta. Indexer running, treat as experimental software. Claim pricing is currently 1/100th of intended production tiers.
Indexer	Open source at `zcashme/ZNS`. Public endpoints at `https://light.zcash.me/zns-testnet` and `https://light.zcash.me/zns-mainnet-test`.
Web app	Open source at `zcashme/zcashnames`. Hosted at zcashnames.com .
ZVS (verification service)	Running on testnet and mainnet. Same repo as the web app.
Live explorer	Hosted at zcashnames.com/explorer . Server-rendered, talks to the public indexer.

SDKs

Eight first-party language ports, all wrapping the same JSON-RPC API. They live in zcashme/ZNS/sdk and track the same version.

Language	Package	Status
TypeScript / JavaScript	`zcashname-sdk`	Published
React Native	`zcashname-sdk-react-native`	Published
Rust	`zns-client` (git)	Published
Python	`zcashname-sdk`	Published
Kotlin / JVM / Android	`com.zcashme:zns-sdk`	Published
Swift	`ZcashNameSDK`	Published
Go	`github.com/zcashme/zns-sdk-go`	Published
Dart / Flutter	`zcashname_sdk`	Published

For language-by-language details see SDKs. For developers integrating directly without an SDK, see Direct RPC.

Wallets

ZcashNames resolution lets a wallet user type alice.zcash in the recipient field instead of pasting a full unified address.

Wallet	Resolution support
Edge	Implementing
Unstoppable	Implementing

No wallet has shipped ZNS resolution yet.

For the integration list and the wallets that handle ZNS transactions (every modern shielded Zcash wallet that supports ZIP-321 and verbatim Orchard memos), see Wallet Compatibility.

What is open

The whole stack is MIT or Apache licensed and lives in two repos:

zcashme/ZNS - the Rust indexer, the OpenRPC spec, and the SDK ports
zcashme/zcashnames - the web app, ZVS, and the docs site you are reading

Trust assumptions, in one paragraph

Every state-changing action in ZNS is signed by an Ed25519 admin key held by the maintainers. That key gates writes to the registry. It does not gate reads, because anyone can run an indexer with the published UIVK and arrive at the same database. It does not control user funds. The full picture is on the Trust model page.

Where to engage

File issues at zcashme/zcashnames or zcashme/ZNS
Wallet integration questions: open a GitHub issue or join the community Signal group linked from the FAQ