🛠️
Technical Documentation
  • Introduction
    • About Empeiria
  • Empe Blockchain
    • Overview
    • Chain Architecture
      • Auth
      • Authz
      • Bank
      • Distribution
      • Governance
      • Staking
      • IBC
      • DidDoc
      • Vesting
      • Minter
  • EVDI
    • EVDI Architecture
    • Self-Sovereign Identity
      • Technical Foundations
      • Roles in the SSI framework
      • Protocols and Standards
  • User Guide
    • Empe DID Wallet
      • Intro
      • Download and first launch
      • Create or import did
      • Main screen overview
      • How to claim credential from issuer
      • How to use credential with verifier
      • Settings and other options
    • Keplr Wallet and Blockchain Operations
      • How to Connect Keplr Wallet
    • Ping Pub operation
    • Staking Tokens Guide
    • Voting on Governance Proposals Guide
    • Sending Tokens Guide
  • Developer Guide
    • Tutorial: Credential Issuance & Verification
      • Overview
      • Understanding Key Concepts
      • Project Setup
      • Deploying the Issuer
      • Uploading the Credential Schema
      • Issuing Credentials
      • Frontend for Credential Issuance
      • Testing Credential Issuance
      • Deploying the Verifier
      • Setting Up the Verification Flow
      • Creating a Verification Endpoint
      • Creating a Protected Dashboard
      • Testing the Verification Flow
      • Summary & Next Steps
    • One-click deployment
      • Introduction
      • Registration
      • Login
      • Creating an Issuer
      • Issuer Data Description
      • Creating a Verifier
      • Verifier Data Description
    • Verifier
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • Query Language
      • Frontend Integration
      • Client Configuration
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • FAQ
    • Issuer
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • DID Document Management
      • Schemas Management
      • Issuing Credentials
      • Interacting with Wallets
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • FAQ
    • Wallet SDK (Coming soon)
    • Introduction to cosmwasm
  • Validator Guide
    • Important links
    • Validators Guide
      • New validator
      • Hardware requirements
      • Required software installation
      • Go installation
      • Install prebuild binary
      • Install binary from source code (option B)
      • Configure a node
      • Cosmovisor setup
      • Sync with state-sync
      • Full state sync from archive snapshot
      • Latest snapshot
      • Run a Validator
      • Migration to v0.2.2
      • Migration to v0.3.0
    • FAQ
  • Appendix
    • Glossary
Powered by GitBook
On this page
  1. EVDI
  2. Self-Sovereign Identity

Technical Foundations

Self-Sovereign Identity (SSI) relies on a blend of innovative technologies to empower user control and decentralize identity management. Here’s a breakdown of the key innovations that make self-sovereign identity possible:

Blockchain Technology: Blockchain plays a crucial role in SSI. It provides a tamper-proof ledger for recording critical events like the issuance and ownership of Verifiable Credentials (VCs). Imagine a public registry where everyone can verify the authenticity of a credential without relying on a central authority. Transactions on the blockchain are secured through cryptography, making it highly resistant to tampering or fraud.

Public-Key Cryptography: This creates a key pair — a public key for sharing information and a private key for secure access. VCs are typically signed with the issuer’s private key, and anyone can verify the signature using the corresponding public key. This ensures the authenticity of the credential.

Digital Signatures: Similar to signing a physical document, digital signatures provide cryptographic proof that a specific entity (e.g., university) issued a VC. This allows relying parties (e.g., employers) to trust the information without contacting the issuer directly.

Hash Functions: These are one-way mathematical functions that transform data into a unique fingerprint. Any change to the data will result in a completely different hash, making it easy to detect alterations. Hash functions are used to ensure the data within a VC hasn’t been tampered with.

Decentralized Identifiers (DIDs): Imagine a unique web address for your identity, not tied to any specific platform or service provider. DIDs provide this functionality. They are globally unique, user-managed identifiers, offering greater control over how their identity is represented online.

Verifiable Credentials (VCs): These are tamper-proof digital documents containing a user’s verifiable claims about themselves, such as educational qualifications or work experience. VCs are issued by trusted entities (e.g., universities) and stored securely in the user’s digital wallet. When needed, users can selectively share specific VCs with third parties for verification. Cryptographic proofs are used to demonstrate the validity and authenticity of the credential without revealing any unnecessary underlying data.

This combination of technologies empowers users to control their identity data, securely share verified credentials, and interact online with greater trust and transparency.

PreviousSelf-Sovereign IdentityNextRoles in the SSI framework

Last updated 10 months ago