🛠️
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
  • Core Components
  • 1. One Click Deployment
  • 2. Issuer Service
  • 3. Verifier Service
  • 4. Reference Wallet
  • EMPE Blockchain Integration
  • Bringing It All Together
  1. EVDI

EVDI Architecture

The End-to-End Verifiable Data Infrastructure (EVDI) provides a standards-based platform for managing decentralized digital identities and Verifiable Credentials (VCs). It is composed of multiple subsystems—each focusing on a distinct role within the Self-Sovereign Identity (SSI) lifecycle—and operates seamlessly to deliver trust, interoperability, and flexibility.

Core Components

1. One Click Deployment

One Click Deployment streamlines the setup and configuration of Issuer and Verifier services. By automating the deployment process, it eliminates much of the manual complexity involved in setting up secure, blockchain-integrated SSI environments. Users gain:

  • Rapid Provisioning: Instantly deploy Issuers and Verifiers, complete with registered DIDs on the EMPE Blockchain.

  • Centralized Management: Easily access, monitor, and maintain deployed components through a unified dashboard.

2. Issuer Service

The Issuer Service is responsible for creating and delivering Verifiable Credentials. Key features include:

  • DID Management: Automatically generates and anchors DIDs on the EMPE Blockchain.

  • Schema Management: Defines the structure of credentials and supports versioning for iterative updates.

  • Credential Issuance: Issues targeted or open offerings for wallets to claim, ensuring authenticity and trust.

  • Lifecycle Controls: Revokes, updates, and deletes credentials as needed.

  • Secure Interactions: Uses OAuth2-like flows for wallets, ensuring the right entities receive the right credentials.

3. Verifier Service

The Verifier ensures that presented credentials meet certain criteria and originate from trusted Issuers. Its responsibilities include:

  • Credential Verification: Validates cryptographic signatures, DID documents, and compliance with specified schemas.

  • OIDC4VP Compatibility: Aligns with OpenID Connect flows for standardization and interoperability.

  • Real-Time Feedback: Uses Server-Sent Events (SSE) to provide immediate verification results to front-end applications.

  • Flexible Queries: Employs a query language that allows fine-grained requirements, ensuring only credentials that match defined conditions are accepted.

4. Reference Wallet

The Empe DID Wallet is a reference mobile wallet application available for iOS and Android. It allows holders to:

  • Store Decentralized Identifiers (DIDs): Securely manage their DIDs and verifiable credentials.

  • Manage Credentials: Receive Verifiable Credentials and store them securely in your wallet.

  • Sign and Present Credentials: Deliver signed credential presentations to verifiers.

Future developments include a Wallet SDK, enabling developers to integrate DID management and credential exchange logic directly into their applications, providing an out-of-the-box solution for seamless integration.

EMPE Blockchain Integration

All DIDs and associated documents are registered on the EMPE Blockchain, serving as a trust anchor. This decentralized ledger ensures:

  • Authenticity: DIDs and their public keys are tamper-evident.

  • Interoperability: Any participant can resolve and verify DIDs using open standards.

  • No Central Authority: Identities remain in the user’s control, not under a single centralized entity.

Bringing It All Together

One Click Deployment kickstarts your ecosystem by deploying fully configured Issuer and Verifier services. The * Issuer Service* then offers credentials to wallets, while the Verifier Service checks those credentials when presented. Both rely on the EMPE Blockchain to verify DIDs, ensuring trust without central intermediaries.

This architecture forms a complete SSI environment:

  1. Issuer creates and publishes credentials.

  2. Wallets (not described in detail here, but integral to user interactions) allow individuals to store and manage their own credentials.

  3. Verifier validates credentials against established criteria.

  4. EMPE Blockchain underpins trust, enabling secure, self-sovereign identity verification at scale.

By adhering to W3C Verifiable Credentials and DID Core standards, and by integrating OAuth2 and OIDC4VP patterns, the EVDI ecosystem ensures that your SSI solutions remain interoperable, future-proof, and user-centric.

PreviousMinterNextSelf-Sovereign Identity

Last updated 3 months ago