Verifier ID: ownership-social
Prove a person controls a social account, then reuse that receipt across your apps. OAuth runs on NEUS — you never handle tokens.
Use cases
- Trust pages and reputation
- Community onboarding and gating
- Linking a social handle to a wallet or profile
Flow type
Interactive, hosted-only. The user authorizes the provider on NEUS and returns with a receipt. This verifier cannot be submitted directly from your backend, and it cannot be combined with other checks in one request.
Supported providers
discord, github, facebook, x, linkedin, telegram, coinbase.
The simplest path
Send the user to Hosted Verify, then read the receipt back:
You get a qHash. Store it and reuse it — don’t re-run the flow on every visit. Never collect raw OAuth tokens.
Fields
internalSocialToken is produced by the hosted flow — your app does not create it. For almost all integrations, use Hosted Verify or VerifyGate and skip direct submission.
Full schema: ownership-social.json. Last modified on July 13, 2026
