ZNS Connect

Open ZNS Connect and claim a handle you can carry anywhere. Pick a name, bind one or more wallets, and choose a default address for signing. Add basic profile fields, set what’s public, and keep the rest private. Link social proofs like GitHub or X so people can verify it’s you. Set up account recovery with guardians or a backup key; if you rotate a wallet later, update your bindings without losing your profile. Everything you change syncs to your address-bound identity, so the same handle works across apps.

Use your handle to sign in without passwords. On any supported site, hit “Sign in with ZNS,” approve the signature, and select the data you want to share (just a pseudonymous ID, or name and socials if needed). Grant time-limited access, create app-specific keys for mobile sessions, and revoke permissions from your dashboard at any time. Share contact details by scanning a QR code that updates automatically when you change wallets. When you join a community or claim a role, your access list follows you across chains, so you don’t repeat the same checks in every app.

Creators can prove authorship and keep projects organized. Publish posts, newsletters, or repos with a signed identity so readers and collaborators know the source is genuine. Gate premium content with roles tied to your handle, sell tickets that unlock to verified holders, and collect submissions that include verifiable profiles instead of throwaway emails. Teams can assign roles (editor, reviewer, finance) to a shared space, onboard new members by linking their handles, and switch permissions in seconds when responsibilities change. For DAOs, proposals, votes, and payouts can reference a single, portable profile instead of scattered wallet IDs.

Developers add ZNS Connect with a few lines. Install the SDK, drop in the sign-in button, and request scopes for what your app needs. Resolve a handle to wallets and metadata, verify signatures server-side, and subscribe to webhooks for role or credential changes. Use the API to issue badges, read proofs, and enforce access lists on-chain or in your backend. Bridge Web2 with an OAuth-style flow, or keep it pure wallet-based. Test in a sandbox, move to main networks when ready, and ship with clear examples for Node, Python, and front-end frameworks. You control what you request; users control what they share.