zkNS

Claim a single handle that travels with you across chains. Start by searching for an available name, then choose which networks you want it to work on. In one flow, you map the same handle to different wallet addresses (e.g., your EVM, non-EVM, and L2 accounts). Confirm the registration, pay gas, and your handle is live. Set a primary name so wallets and dapps recognize it automatically, and decide where incoming transfers should route by default. Because it’s built on LayerZero, your handle can point to destinations on multiple chains without manual bridging.

Next, turn your handle into a usable profile. Add an avatar, bio, and links to socials, GitHub, or your site. Attach records for email, Telegram, or “content” references that point to your portfolio or docs. If you manage multiple wallets, define per-chain routes—USDC to Chain A, NFTs to Chain B—so senders only need your name. Create subnames for teammates or alt wallets (e.g., dev.yourname, ops.yourname) and delegate permissions to let others update specific records without full control. For recoverability, assign guardians or a multisig to regain access if you lose a key. You can update records from any supported chain, and changes propagate through the omnichain transport.

Use your handle everywhere you interact onchain. Share it in your bio so collaborators can pay you on the network they prefer—funds arrive where you’ve routed them. Sign in to integrated apps using your name to auto-populate your profile. Set a reverse record so your handle appears in wallets, explorers, and dapps instead of raw addresses. For teams, give each contributor a subname and track roles without exposing primary keys. Creators can set a tip address, publish a link hub, and rotate payout routes as campaigns change. DAOs can assign function-specific subnames (treasury.dao, grants.dao) and update destinations as signers rotate, avoiding address churn.

For builders, integration is straightforward. Resolve a name to addresses on any chain with the SDK or API, cache results for performance, and verify reverse records for display names. Add a name field to checkout flows so users can pay by handle rather than pasting addresses, then honor chain-specific routing with a single lookup. In smart contracts, reference the resolver to fetch a recipient’s preferred destination, reducing failed sends. On the front end, show profile metadata (avatar, links) to humanize activity feeds and comments. Test on supported testnets, monitor events for record changes, and surface warnings before a name renewal lapses. With LayerZero under the hood, you avoid custom bridging logic while giving users a consistent identity across ecosystems.