🛠️
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. Developer Guide
  2. Issuer

Terminology and Concepts

Self-Sovereign Identity (SSI): A user-centric approach to digital identity, allowing individuals and organizations to control their identifiers and credentials without centralized authorities.

Decentralized Identifier (DID): A globally unique identifier resolvable via the EMPE Blockchain. A DID Document includes public keys and endpoints for trust and verification.

Verifiable Credentials (VCs): A cryptographically signed credential that attests to certain attributes of an entity. VCs follow W3C standards, ensuring integrity and authenticity.

Credential Schema: A JSON-based template defining the structure, properties, and required fields of a credential type. Ensures consistency and interoperability.

EMPE Blockchain: The ledger where DIDs are anchored, providing a trust layer that wallets and verifiers rely on for DID resolution and verification.

One-Click Deployment Portal: A provisioning tool that automates deployment, DID registration, and initial configuration of the Issuer Service.

Targeted Offering vs. Open Offering:

  • Targeted Offering: Restricted to a specific recipient DID.

  • Open Offering: Accessible to any wallet scanning the offering’s QR code or link.

Authorization Code Flow (Wallet Flow): A process where the wallet authenticates and proves DID ownership, exchanging authorization codes for access tokens and, ultimately, retrieving the credential.

These concepts form the foundation for understanding the Issuer Service’s APIs, credential flows, and integration with other ecosystem components.

PreviousIssuerNextArchitecture Overview

Last updated 4 months ago