Zcash Engineering Office Hours #8: Zcash Names, Part 2, How Anyone Can Verify a Name
Tue Jun 23, 11 AM ET (15:00 UTC) · Zcash global Discord stage · RSVP: Zcash Engineering Office Hours: Zcash Names and Edge Wallet · Luma
Back in April we introduced Zcash Names: the on-chain .zcash naming service and the Zcash.me identity layer. This session goes one level down, to the part that actually makes a name trustless, and therefore trustworth.
A name-to-address binding in Zcash Names lives inside a shielded Name Note’s commitment, and the chain commits to its hash through the note’s cmx. The randomness (rcm, ψ) is a deterministic hash of (action, name, ua, prev_rcm), so anyone can recompute the Sinsemilla note commitment and check it against what is on-chain. Match means the binding is real; mismatch means it is not. That is the whole trust model, and it fits in a no_std, forbid(unsafe_code) crate with no orchard dependency: zns-verify.
We will also cover wallet integration with members of the Edge wallet team to learn how resolution wires into a real client, what the live Edge beta does today.
Prep: skim the zns-verify README. Try a resolution at zcashnames.com/explorer or cipherscan.app.
Hosted by Mark Henderson (@shieldedmark) with the zcashme team (@zcashme / @zcashnames) and Paul, Matthew, and Jon from Edge.
Recorded with Portuguese translation by Zcash Brazil / ZecHub.