zkNS

Claim one handle, use it everywhere you transact. zkNS lets you register a single human-readable name and connect it to wallets on many networks. Start by linking the wallet you use most, search for an available handle, pick a term, and confirm the registration. After you own it, open your profile settings to attach addresses for each chain you use—Ethereum, Arbitrum, Optimism, BNB Chain, Polygon, Avalanche, and more. Add an avatar (NFT or image), a short bio, and links you want others to see. Set default receive rules so payments to your name route to the right chain. All updates propagate across chains through LayerZero messaging, so the same handle resolves consistently wherever people look it up.

Use your name in day-to-day crypto tasks. When a wallet or dApp supports resolution, friends can pay you by entering your handle instead of pasting a long address. Share a QR code or link to your profile for tips, invoices, and donations. If you bridge funds or change the wallet you use on a chain, update that chain’s mapping once and it syncs for everyone. You can create subnames for teammates or devices (e.g., ops.yourname) and delegate control to each owner. For frequent payments, define token-specific preferences—like routing stablecoins to a low-fee network—so senders don’t need to ask which chain you prefer.

Creators and organizations use zkNS to standardize identity across campaigns and communities. Issue subnames to members, partners, or event attendees to streamline access and attribution. Publish a profile card that embeds your avatar, links, and donate button on sites and newsletters. For token-gated perks, reference name ownership in your community tools where supported. During launches and airdrops, point participants to your handle for a single, verifiable destination instead of maintaining multiple addresses. Analytics from your wallet tools show which networks your supporters use most, helping you set smarter routing rules.

Developers can integrate name resolution in minutes. Use the zkNS resolver libraries or the HTTP API to turn a handle into the correct address for a requested chain and token standard. Implement reverse lookup so users see their handle next to balances and activity where supported. Rely on LayerZero to mirror record updates across chains and subscribe to events to keep caches fresh. In UI, add a name search field with suggestions, availability checks, and clear ownership badges. On the backend, enforce chainId-aware routing, validate signatures when updating records, and provide fallbacks if a chain is not mapped. Test end-to-end on supported testnets before going live.