See how a website can gate access to verified humans using Soverage Verifiable Presentations.
Score ≥ 60 · At least 2 attestations
Community Forum
Members-only discussions
DAO Governance Proposal #47
Vote on the new treasury allocation. Only verified humans can participate to prevent sybil attacks on governance decisions...
Airdrop Claim - Season 2
Claim your share of the community distribution. Proof of personhood required to ensure fair per-person allocation...
Verified Marketplace
Buy and sell with confidence. All participants must prove their humanity to protect against fraud and automated bots...
This content is restricted to verified humans. Present your Soverage credential to gain access.
Minimum personhood score: 60 · At least 2 attestations
Share this link with the credential holder, or let them scan the QR code to open the Soverage Gateway.
In production, this URI is encoded as the QR code for native OID4VP wallet scanning.
Polling every 3 seconds.
Tip: Click "Simulate Response" to auto-submit a VP from your local Soverage session data.
Access Granted
Human identity verified via Soverage VP
Community Forum
Verified Access
DAO Governance Proposal #47
ActiveVote on the new treasury allocation. 147 verified humans have voted so far.
Airdrop Claim - Season 2
ClaimableYour allocation: 500 tokens. One claim per verified human.
Verified Marketplace
23 listingsBrowse verified listings from real humans. Zero fraud, zero bots.
Configure your access requirements in the left panel, then click "Verify with Soverage" to create a VP request via the API.
Share the generated URL with a credential holder, or open it yourself in a separate browser with an active Soverage session.
The demo polls the API until the holder submits their Verifiable Presentation. Once received, it validates the score and grants access.
Demo note: This demo uses a relay pattern where the holder's VP is submitted through the Soverage API and the verifier polls for the response.
In the full OID4VP specification, the wallet POSTs the VP directly to the verifier's response_uri.
See the Verification Flows docs for the spec-compliant flow.
For the full integration guide, API reference, and code examples, see the developer docs.