Help Center/Ecosystem Fundamentals/Understanding Decentralized Identifiers (DID) & Sovereign Keys
Ecosystem Fundamentals•Last updated: 2026-09-18•5 min read

Understanding Decentralized Identifiers (DID) & Sovereign Keys

How I8 uses W3C-compliant Decentralized Identifiers (did:i8:...) to decouple user identity from centralized database authorities.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Locating Your Sovereign DID

Navigate to the top header bar or visit /app/profile. Your DID appears formatted as did:i8:<genesis-hash>...<referral-code>.

2

Public vs Private Key Material

Your public key is broadcast across the network for cryptographic signature verification. Your private key remains encrypted locally on your device or in your hardware vault.

💡 Pro Tip: Never disclose your private key or seed recovery phrase to anyone, including platform administrators.
3

DID Resolution & Verification

When you interact with smart contracts or sign merchant orders, the platform verifies your DID signature against the sovereign root node registry on i8Chain.

Expected Operational Outcome

Full understanding of your cryptographic identifier and key management best practices.

Was this guide helpful?

Help us refine our platform documentation