Skip to main content

"Decentralized Identity (DID) & Verifiable Credential (VC) Explorer"

"An interactive tool to explore Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs)."

Next.jsReactTypeScriptTailwind CSSWeb Cryptography

Current Status

Personal DID

Not yet generated

Institution DID

Not yet generated

Credential

Not yet created

Verification

Not yet verified

Decentralized Identity (DID) & Verifiable Credential (VC) Explorer

An interactive playground for exploring how digital identity can work without central authorities, using cryptography to ensure trust.

Enhanced DID Methods Explorer

Create, manage, and verify decentralized credentials with advanced features

🔑 did:key - Pure Cryptography🌐 did:web - Custom Domains📜 Credential History🔍 Import/Export

Step 1: Create Your Identity

Choose DID methods that match your use case. Individuals might prefer did:key for privacy, while institutions often use did:web for trust.

Your Personal DID

Institution DID

DID Key Benefits
  • ✓No external dependencies
  • ✓Works offline
  • ✓Instant resolution
  • ✓Maximum decentralization
DID Web Use Cases
  • •Corporate identities
  • •Educational institutions
  • •Government services
  • •Public-facing organizations

Step 2: Issue a Credential (As Institution)

Now act as an institution. Select a credential type and issue it to the recipient.

Step 3: Verify the Credential (As Employer/Verifier)

Now act as a verifier. The verification process works across all DID methods!

Real-World Scenario: How DIDs & VCs Work

Imagine Sarah is graduating from university and needs to prove her degree to employers:

🎓 The Traditional Way (Problems)

  1. •Sarah gets a paper diploma (can be forged)
  2. •Employers must call the university to verify (time-consuming)
  3. •University database could be hacked or go offline
  4. •Sarah has no control over her own credentials

🔐 The DID & VC Way (Solutions)

  1. •Sarah creates her DID - Her own cryptographic identity that she controls
  2. •University issues a VC - They digitally sign her degree with their DID
  3. •Instant verification - Employers verify the signature mathematically
  4. •Tamper-proof - Any changes invalidate the signature
  5. •Always available - No need to contact the university

🚀 Try This Scenario Yourself

Let's simulate Sarah getting her university degree credential:
  1. •Sarah (You): Generate your personal DID and copy it - you'll need to share it with the university
  2. •University: Generate an institution DID to represent the university
  3. •Issue Degree: Manually paste Sarah's DID and issue her a credential, then copy the credential
  4. •Employer: Paste the credential you received to verify its authenticity
The manual copy-paste simulates real-world communication where different parties don't share the same system!

Try It Yourself

The explorer above lets you play all three roles in the credential ecosystem:
  1. •As an Individual - Generate your personal DID (your digital identity)
  2. •As an Institution - Issue a credential to someone by entering their DID
  3. •As a Verifier - Verify the credential's authenticity through cryptography
Watch the animations to see:
  • •How institutions cryptographically sign credentials
  • •The step-by-step verification process
  • •Why tampering is impossible without the private key

Why This Matters

  • •You own your identity - No company or government controls your DID
  • •Instant verification - No phone calls, no waiting
  • •Cannot be forged - Cryptography makes fakes impossible
  • •Privacy-preserving - Share only what's needed
  • •Works offline - No central server required

Learn More

Expand the "Understanding the Cryptography" section below to dive deeper into how public key cryptography makes this system secure and trustworthy.