ownership-basic when the user has a browser wallet. Social, human, or org flows: Hosted Verify. Before production: Get started (app link, billing).
1. Install
2. Create a proof
client.verify() defaults private. VerifyGate defaults differ - Widgets, Security and trust.
proofId. Same value is qHash in some API paths - Verification results. Check before asking the user to verify again.
Other verifiers: SDK verifications. No in-page wallet: Hosted Verify.
3. Poll
4. Gate (React)
5. Server check
gateCheckaddress= wallet that signedverify().- Prefer a stored id + check before a new verify.
- Verifier list must match what you issued.
See also
| Get started | App, billing, production |
| Choose a path | SDK, widgets, API, MCP |
| Integration | Check, verify, save, reuse |
| Examples | Repositories |