Welcome back. The first ZcashNames closed beta proved the core flows: claiming names, updating them, listing or delisting them, and releasing them back into the wild.
This next round is about what comes after that. We are testing wallet-connected behavior: resolving names to shielded addresses in wallets, buying and selling names end to end, receiving proceeds, and sending ZEC to names instead of raw addresses.
Edge Wallet is already using the SDK to resolve the Zcash namespace, which makes this round the first serious pass over the full wallet-facing experience.
Want in?
Apply for the next beta cohort and tell us whether you want to test wallet flows, SDK integration work, or both.
Get Started
- Apply at /beta/apply.
- If selected, you will receive an invite and passcode through your preferred contact method.
- Use that passcode to unlock the beta when your access window opens.
- Work through the wallet and SDK flows below, then report what breaks, what feels sharp, and what still confuses real users.
How It Works
ZcashNames maps short names like pacu.zcash to real Zcash identities and addresses. In the first closed beta, that meant proving the namespace itself worked. In this round, the goal is proving that the namespace behaves correctly once it is embedded inside wallets and sale flows.
Edge Wallet is the flagship integration for this phase. If the wallet can resolve names, route ZEC to them, and surface sale flows correctly, the namespace becomes meaningfully usable outside the demo environment.
Beta Structure
- Closed beta one validated the core protocol operations.
- Beta two validates wallet resolution, wallet-side UX, and sale proceeds behavior.
- We still want both user-flow testers and SDK-minded testers in the cohort.
- Priority goes to applicants who can give precise reproduction notes, environment details, and repeatable results.
What to Test
This round centers on the flows that were not complete in the first beta:
- Resolve ZcashNames entries to shielded addresses in Edge Wallet.
- Buy a name through the wallet-connected flow.
- List a name for sale and confirm the listing state is correct.
- Complete a sale and verify the transfer finishes cleanly.
- Receive proceeds from the transaction in the correct wallet.
- Send ZEC directly to names and confirm the resolution target is correct.
SDK testers should focus on resolution behavior, identity verification, edge cases, and any differences between wallet output and raw JSON-RPC behavior.
The Feedback Panel
The reporting expectation stays the same: when you are invited in, document the wallet, version, operating system, network, and exact steps you took. Reports that include the expected result, the actual result, and any txid or screenshots are the most useful.
For this round, we care as much about confusing UX and mismatched wallet behavior as we do about outright bugs. If a flow technically works but a normal user would misread it, report that too.
Confidentiality
Treat invite codes, unreleased wallet behavior, and any incomplete sale or proceeds flows as beta-only information until we say otherwise. Public bug reports are fine after coordination, but not before we have had a chance to reproduce and classify them.
Bug Bounties
We are especially interested in bugs that misroute value, misreport sale state, fail to deliver proceeds, or resolve names incorrectly. Clear reports that isolate those failures will be prioritized for follow-up and may qualify for bounty handling where applicable.
What You Need
- A reliable way to test Edge Wallet behavior.
- Enough familiarity with Zcash to describe shielded-address expectations accurately.
- If you are applying as an SDK tester, enough development context to compare wallet behavior against the SDK or JSON-RPC directly.
Timeline
Applications are open now. Invites will go out in batches, and the first people in will shape how aggressively we expand the cohort. If you are invited later, that does not mean we are less interested; it usually means we are pacing access against fixes.
Get In Touch
Use the form to tell us how to reach you. If you need to contact us outside the application flow, these are the channels we watch most closely during beta: