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

Interacting with Wallets

Wallets are integral to the SSI ecosystem, enabling end-users to:

  • Authenticate and Retrieve Credentials: Wallets scan QR codes or follow secure links to claim credentials. For targeted offerings, wallets must present cryptographic proofs (Verifiable Presentations) to prove DID ownership.

  • Authorization Code Flow: The Issuer Service uses an OAuth2-like pattern:

    1. POST /api/v1/authorize

      Creates an authorization request.

    2. POST /api/v1/authorize/verify

      Verifies the submitted Verifiable Presentation.

    3. On success, a code is issued and exchanged at:

      POST /api/v1/connect/token
  • Retrieving the Credential: With a valid access token, wallets call:

    POST /api/v1/issue-credential/{id}
    Authorization: Bearer JWTAccessToken

    to obtain the Verifiable Credential.

  • Storage and Presentation: Once obtained, the wallet stores the credential locally and can present it to verifiers as needed.

Example Token Exchange:

POST /api/v1/connect/token
Content-Type: application/json

{
  "authorization_code": "validAuthorizationCode"
}

Response:

{
  "access_token": "JWTAccessToken",
  "token_type": "Bearer",
  "expires_in": 3600
}

Retrieving Credential:

GET /api/v1/issue-credential/{id}
Authorization: Bearer JWTAccessToken

Example Response:

{
  "id": "credential-id",
  "type": "ProofOfPurchase",
  "recipient": "did:empe:123456789",
  "credentialSubject": {
    "ticket": "ticket123",
    "seat": "A12",
    "description": "Concert ticket"
  },
  "vc": {...}
}

This sequence provides a secure, user-friendly experience aligned with SSI standards, preserving user privacy and control.

PreviousIssuing CredentialsNextSecurity Considerations

Last updated 4 months ago