Use NEUS to make creator handles portable and verifiable. A user claims a handle, NEUS binds it to their wallet with the ownership-pseudonym verifier, and your app gets a reusable qHash you can badge, link, and gate.
When to use this
- Creator platforms, media networks, or launchpads that need handle ownership proof.
- Pseudonymous identity without legal identity exposure.
- Gating drops, founders tables, or premium calls behind a verified handle.
What you need
- A published NEUS gate with
ownership-pseudonym enabled (or use direct verification with in-app signing).
- The user’s wallet address.
- A
namespace to isolate your handles from the default neus namespace.
Flow
- User claims a handle in your app.
- Your app asks NEUS to bind
handle + namespace + walletAddress.
- NEUS returns a
qHash and a proof URL.
- Your app stores the
qHash with the user record.
- Surface a verified badge that links to the public proof page.
- Before any privileged action, check the receipt on your server.
Direct verification (in-app signing)
Use NeusClient.verify() when your app already handles wallet signatures.
pseudonymId must match ^[a-z0-9][a-z0-9._-]{1,30}[a-z0-9]$.
Hosted Verify (no in-app signing)
Send the user to NEUS and get the qHash back on return.
Read the qHash from the callback URL or popup message and store it.
Show the badge
Drop the SDK widget next to the handle.
The badge links to https://neus.network/proof/{qHash} and shows live proof status.
Gate creator actions on the server
Always check the receipt server-side before allowing privileged actions.
Or call the HTTP API directly:
Namespace policy
Namespaces other than neus require the namespace owner to prove DNS control with ownership-dns-txt, or NEUS admin approval. Contact NEUS to reserve a production namespace for your platform.
Optional: link social accounts
Layer ownership-social to also prove a linked X, Discord, Telegram, GitHub, or other social account. Social verification is interactive and hosted-only, so it is typically run through VerifyGate or Hosted Verify rather than direct signing.
Full example
See the verified-handle-react example for a complete React + Vite app.
Next
Last modified on July 14, 2026