🛠️
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

Self-Sovereign Identity

Empeiria's End-to-End Verifiable Data Infrastructure (EDVI) builds on the foundation of Self-Sovereign Identity (SSI), expanding its utility and enabling wider adoption.

SSI is a concept in digital identity, where individuals have full ownership and control over their personal identity information. Unlike traditional identity systems relying on centralized authorities, SSI allows users to own, manage, and share their data. This approach enhances privacy, security, and user autonomy by enabling individuals to authenticate themselves without depending on external entities.

Key Features of SSI

Here are the key features and principles of SSI:

  • User-Centric: In SSI, users have access and control over their identity data. They can decide what information to share, with whom, and for how long.

  • Privacy-Enhancing: SSI is designed to prioritize privacy. SSI uses technologies like blockchain to allow users to prove their identity without revealing unnecessary personal information. Disclosure of claims must be minimized.

  • Decentralized: Traditional identity systems are controlled by central authorities, while SSI is built on decentralized principles. The holder keeps all his data within the wallet.

  • Interoperable: SSI systems aim to be universally applicable, allowing users to use their identity across different services and platforms without separate credentials.

  • Secure: These systems use advanced cryptographic techniques to ensure that identity data is secure and cannot be tampered with.

  • Consent-Based: Any sharing of personal data in SSI systems is based on the user’s explicit consent, providing greater control over personal data.

  • Portable: Users can carry their identity across different platforms and services without depending on a single provider.

  • Transparent: System and algorithms are transparent so that other entities can verify.

PreviousEVDI ArchitectureNextTechnical Foundations

Last updated 10 months ago