Cast by zmzn

Show the cast this replies to

There's another category. Before Zcash Names existed, we built Zcash.me, which was intended to become the profile system for onchain Zcash Names. I gave verified Zcash.me users who joined before May 1 free protection for their usernames. They could keep their identities without paying a reservation fee or joining the queue.

1 likes0 recasts1 replies

1 reply

  • Anyone can suggest a name for protection or dispute an existing protection. Approvals, rejections, and the reasons behind them are public. Why? Because protection lets someone bypass a queue that others paid to join. People should be able to see who's getting that privilege and challenge it. ZcashNames.com/protected/dispute

    No likes or recasts yetRead 1 reply

    There's another reason we take protection seriously. Once someone registers a Zcash Name onchain, we can't take it back. We can't revoke it or assign it to someone else. That's how the protocol is designed. So we have to settle protection disputes before names are registered. github.com/zcashme/zns-whitepaper

    No likes or recasts yetRead 2 replies

    Now, the dispute over `david`. March 10, 2026: Someone registered and verified `david` on Zcash.me. October 9: At the Network State Conference, another David who was helping promote Zcash Names wanted to register `david`. But I'd already protected it for the original Zcash.me user.

    No likes or recasts yetRead 1 reply

    Once a name is onchain and you can't take it back, getting the protection calls right first really matters. The david dispute shows how messy it gets. Do you think most names will be settled cleanly, or is this just the start of the fights?

    No likes or recasts yet