Wallet Compatibility

Users usually mean one of two different things when they ask whether a wallet “supports ZcashNames”:

1. can the wallet broadcast a ZNS claim or update transaction?
2. can the wallet resolve alice.zcash in the recipient field?

Those are different features.

Current state

• names can be claimed today
• wallet resolution is not live in any wallet yet
• Edge and Unstoppable are implementing support

So if your name does not resolve in a wallet today, that does not mean the claim failed.

Wallets that can send ZNS transactions

Any wallet that does these three things should be able to broadcast a ZNS transaction generated by the web app:

1. parse ZIP-321 payment URIs
2. send Orchard shielded transactions
3. preserve memo bytes exactly as provided

Examples of wallets in the modern shielded Zcash category:

• Cake Wallet 
• Edge 
• Unstoppable 
• Zodl 
• Zkool 
• Zingo! 

Wallets that are implementing resolution

Name resolution is the extra wallet-side work that lets a user type alice.zcash directly into the recipient field.

Implementing now:

• Edge 
• Unstoppable 

If you are a wallet team

The integration surface is small:

1. detect that input is a ZNS name
2. call resolve
3. substitute the returned unified address
4. continue through the normal send flow

Start with Wallet: Resolve a Name.

Wallets to avoid for ZNS operations

• legacy unmaintained Zcash wallets
• hardware wallets that cannot send to shielded Zcash recipients
• Sapling-only wallets
• wallets that rewrite or normalize memo bytes

Reporting wallet issues

If a wallet should work for claim transactions but does not, report:

• wallet name, version, and platform
• the ZIP-321 URI the site generated
• the memo bytes the wallet actually sent
• the txid if broadcast