Testnet Guide

Try Soverage Gateway on Hedera Testnet

Soverage Gateway is live on Hedera Testnet. This guide walks you through the full verification flow using test credentials.

Prerequisites

You need a Hedera-compatible wallet with testnet HBAR. The gateway uses WalletConnect so any compatible wallet works.

1. Install a wallet

HashPack

Browser extension and mobile. Most popular Hedera wallet.

Blade

Browser extension and mobile. Developer-friendly.

2. Create a testnet account

In your wallet settings, switch to Testnet network. Create or import an account.

3. Get testnet HBAR

You need a small amount of HBAR to cover transaction fees (DID creation, attestations, token minting). Use the official faucet:

• Hedera Portal faucet: request testnet HBAR for free

DID creation and attestations cost fractions of a cent each on Hedera, so a small amount is enough.

Walkthrough

Open gateway.soverage.com and follow these steps:

Step 1: Connect wallet

Click Connect Wallet. A WalletConnect modal appears. Scan the QR code with your mobile wallet or approve in your browser extension.

Once connected, your account ID appears in the dashboard.

Step 2: Verify identity

Upload a government-issued ID (passport, national ID, driver’s license). The document is analyzed by AI for liveness, authenticity, and data consistency. A personhood score (0–100) is computed.

Document images are processed in memory and immediately discarded. No personal data is stored by Soverage at any point.

Step 3: Create DID

After verification, create your Decentralized Identifier. This generates an Ed25519 key pair and anchors a DID Document on Hedera Consensus Service.

Your wallet will prompt you to approve two transactions:

1. Topic creation: creates an HCS topic for your DID
2. DID Document publish: writes your DID Document to the topic

Step 4: Complete attestations

Strengthen your identity profile with additional attestations:

Attestation	What happens
Email	Enter your email, receive a one-time code, verify
Phone	Enter your phone number, receive an SMS code, verify
Device	Register a passkey or biometric via WebAuthn
Google	Sign in with Google OAuth

Each attestation generates a cryptographic commitment (SHA-256 hash) recorded on-chain. Your personhood score increases with each independent signal.

Step 5: Issue credentials

Once you have at least two attestations, you can issue:

• Verifiable Credential (VC): W3C-standard credential anchored on-chain
• Personhood Token: a non-transferable token minted to your wallet (one per user)

Step 6: Share and verify

Use the dashboard to generate a signed verification link or initiate an OID4VP presentation to share your credentials with third parties.

Verify on-chain

Everything created during the flow is publicly verifiable on HashScan:

Artifact	Where to find it
DID Document	Search your HCS topic ID. The DID Document is the first message
Attestation commitments	Search your HCS topic ID. Attestation events appear as subsequent messages after the DID Document
Personhood Token	Search your account. The token appears under your token balances

Testnet limitations

• Testnet is reset periodically by Hedera, so your DID and tokens may disappear after a reset

Need help?

For issues or questions, visit the FAQ or reach out.