Introduction

Soverage Gateway: decentralized proof of personhood for developers

Soverage Gateway is a privacy-first decentralized identity platform that provides proof of unique human identity without storing personal data.

Users verify their identity through the Soverage Gateway, complete multiple attestations, and receive portable credentials that your application can verify. No personal information is retained at any point.

Get started

How it works

Understand the verification flow, from identity check to credential issuance

Key concepts

DIDs, Verifiable Credentials, attestations, and personhood scores

Verification flows

Signed links, Verifiable Presentations (OID4VP), and on-chain token lookup

API reference

Endpoints, request/response formats, and integration examples

Why integrate Soverage?

• Sybil resistance: ensure each participant in an airdrop, vote, or campaign is a unique person
• DAO governance: gate voting rights to verified humans
• DeFi compliance: lightweight identity checks without storing personal data
• Community access: require proof of personhood for membership
• Fair distribution: prevent bots and duplicate accounts

What your application receives

When a user verifies through Soverage, three credentials become available for your application to check:

• Decentralized Identifier (DID): a W3C DID anchored on-chain that serves as the foundation for the user’s identity
• Verifiable Credential (VC): a W3C Verifiable Credential cryptographically signed and linked to the user’s DID
• Personhood Token: a non-transferable token proving the user is human

Each credential includes a personhood score (0-100) reflecting the strength of the user’s identity proof, based on the number and type of attestations completed.

Verification methods

There are three ways to verify a user’s Soverage identity in your application:

1. Signed verification links: browser-based verification via an HMAC-signed URL containing the user’s identity data
2. Verifiable Presentations (OID4VP): programmatic verification via OpenID for Verifiable Presentations, with cryptographic proofs your server can verify independently
3. On-chain token lookup: query the DLT directly to check if a wallet holds a Personhood Token

Standards

Soverage is built on open standards:

Standard	Reference
W3C Verifiable Credentials	w3.org/TR/vc-data-model
W3C Decentralized Identifiers	w3.org/TR/did-core
OpenID for Verifiable Credential Issuance (OID4VCI)	openid.net/specs/openid-4-verifiable-credential-issuance
OpenID for Verifiable Presentations (OID4VP)	openid.net/specs/openid-4-verifiable-presentations
Ed25519 signatures	RFC 8032
WebAuthn (device attestation)	w3.org/TR/webauthn
Hedera Consensus Service (HCS)	docs.hedera.com/hedera/sdks-and-apis/sdks/consensus-service
Hedera Token Service (HTS)	docs.hedera.com/hedera/sdks-and-apis/sdks/token-service

Current status

Soverage Gateway is in active development. The API is available for early access on Hedera Testnet. We welcome developers interested in testing, integrating, or collaborating. Contact us to get started.