Skip to main content
This page describes the user journey through Soverage Gateway and what your application receives at each stage.

​
User verification flow

​
1. Wallet connection

The user connects a wallet to establish their on-chain identity. This wallet is used to sign credentials and anchor the DID. No funds are transferred. Supported: any WalletConnect-compatible wallet, including HashPack and other Hedera wallets.

​
2. Document verification

The user uploads a government-issued ID. The document is analyzed for liveness, authenticity, and consistency. Processing is ephemeral: the image is analyzed in memory and immediately discarded. The result is a base personhood score and a cryptographic commitment (one-way hash) of the verification outcome. No document data is stored.

​
3. DID creation

A Decentralized Identifier (DID) is created and anchored on-chain. Each DID gets its own consensus topic where the DID document is published and can be independently resolved. The DID is the anchor for all subsequent credentials. Format: did:hedera:testnet:z6Mk...

​
4. Additional attestations

Users complete additional attestations to strengthen their identity profile:
  • Email: ownership verified via one-time code
  • Phone: ownership verified via SMS code
  • Device: possession verified via WebAuthn passkey/biometric
  • Social account: verified via OAuth (e.g. Google)
Each attestation generates a cryptographic commitment and is recorded on-chain. New attestation types may be added over time. The personhood score (0-100) increases with each independent signal. Applications can set their own minimum score thresholds.

​
5. Credential issuance

Once the user completes at least two attestations (document plus one additional), a Verifiable Credential (VC) is issued. This is a W3C-standard credential containing the user’s DID, personhood score, and cryptographic proof (Ed25519 signature), issued via OID4VCI.

​
6. Personhood Token minting

After the VC is issued, the user can mint a Personhood Token: a non-transferable token minted on-chain. One per user, publicly verifiable.

​
What your app can verify

Once a user holds Soverage credentials, your application can verify them through any of the three verification flows:
What you checkWhat you learn
Personhood scoreStrength of identity proof (0-100)
Attestation typesWhich independent checks the user completed
DIDThe user’s unique, self-sovereign identifier
VC proofCryptographic guarantee the credential is authentic
Personhood TokenOn-chain proof the wallet belongs to a verified human
All verification can happen without contacting Soverage directly. Credentials are portable and self-verifiable.