LogoLogo
ProductsCommunityGitHubShare Feedback
Wallet Kit
Wallet Kit
  • What is the Wallet Kit?
    • Introduction
    • Transition To The Community Stack
    • Self-Sovereign Identity
      • SSI | Basics
      • Technology & Concepts
    • Wallet Kit
      • Wallet Kit | Basics
        • Overview
        • Functionality
      • Architecture
    • Issuer & Verifier Portals
      • Functionality
      • Architecture
  • Getting started
    • Quick Start
    • CLI | Command Line Interface
    • REST APIs
      • Issuer Configuration
      • Credential Templates
      • Credential Issuance
      • Credential Verification
    • Dependency (JVM)
    • Frontend
    • Public deployments
    • Demo
    • Build
      • Docker Build
        • Docker
      • Local Build
  • Configuration and Setup
    • Wallet backend setup
    • Issuer portal setup
    • Verifier portal setup
  • Concepts
    • OpenID Connect (OIDC)
      • OIDC for Credential Issuance
      • OIDC for Verifiable Presentations (SIOP)
      • Issuance via OIDC for Verifiable Presentations (SIOP)
  • Ecosystems
    • IOTA
      • Tutorials
        • Login With IOTA
  • Community
    • Discord
    • Twitter
    • Newsletter
    • GitHub Discussions
  • DEVELOPER RELATIONS
    • Roadmap
    • Contribute
    • Share Feedback
    • Contact
  • Product Editions
    • Open Source | Always Free
    • Enterprise
    • Cloud Platform
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. What is the Wallet Kit?
  2. Wallet Kit
  3. Wallet Kit | Basics

Functionality

The Wallet Kit makes it easy for you to build and launch your own wallet. Now, you can think of wallets as secure data hub for organizations and individuals which allows them to act as "Holders", i.e. they can store, manage and share keys, identity data (e.g. Verifiable Credentials) and other secrets.

Practically speaking, a wallet is a tool that allows anyone to collect and present identity data in order to access services (e.g. sign up, login, check-out) or procure products in a seamless and privacy preserving fashion.

Since there are different types of wallets, it is important to mention that our Wallet Kit enables so-called custodial wallets, which means that keys and data are ultimately stored by the wallet provider (e.g. by you). While this means less control for end-users, it also means a better user experience (e.g. no need to handle private keys or seed phrases) and less risk (e.g. loss of data). Also, end-users enjoy full data portability, which means that they can switch wallets (and take their keys and data with them) at any time without having to fear lock-in effects.

The Wallet Kit provides various high-level functionalities. For example:

  • Web app

    • Web-based user interface (UI) for managing credentials and DIDs.

  • User context separation

    • Separation of user contexts in the data stores (key store, credential store, DID store).

  • User data management

    • DIDs

    • Credentials

  • Ecosystems integrations

    • did:ebsi

      • DID creation

      • DID registration

    • did:web

      • DID creation

      • DID web registry

    • did:key

      • DID creation

  • Verifiable Credential and Presentation exchange

    • Support for credential and presentation exchange based on the OIDC and SIOP specs

      • OIDC4CI - OIDC for credential issuance

      • OIDC4VP - OIDC for verifiable presentations (SIOP)

      • Credential issuance via SIOP protocol (custom protocol)

PreviousOverviewNextArchitecture

Last updated 2 years ago

Was this helpful?