Altme's documentation
  • 🧾Introduction
    • πŸ“‹What is Self Sovereign Identity ?
    • πŸ•΅οΈAltme solution suite is made up of 3 components
      • πŸ—‚οΈAltme Wallet
      • πŸ“‡Altme Saas
      • πŸ“‡Altme Web3 issuer
    • πŸ—‚οΈGive an Identity to your crypto wallet
    • πŸ› οΈTechnical considerations
  • ☁️Altme Saas
    • Quick start
      • ⬇️Download Altme Wallet from Apple or Google store
      • πŸ“Get more credentials in your wallet
      • πŸ”’Connect to the Altme Saas platform to setup a SSI verifier
      • πŸ“²Integration in your app
    • Beacon integration
      • πŸ–₯️Overview
      • πŸ…Verify the age of your users (+13, +18) in a dApp
      • πŸ“²Receive the Verifier data with a webhook in your backend
      • πŸͺ™On-chain and off-chain access with TezID
      • πŸ’ΎVerify other data with other credentials
      • πŸ“‡Issue a Welcome card in a dApp
      • βœ…Check user data of your Issuer (no code)
      • βœ…Check user data of your Issuer with a webhook
      • πŸ•΅οΈUnder the hood : the process flow of a Beacon Verifier
    • OpenID integration
      • πŸ–₯️Overview
      • 1️Example 1 with an β€œimplicit flow” with no code
      • 1️Example 1 with an β€œauthorization code flow” in Python
    • EBSII integration
  • πŸ—‚οΈAlme Wallet
    • Protocols overview
      • πŸ”‘Collecting a verifiable credential
      • πŸ”‘Requesting a verifiable presentation
    • Credential offer protocol
      • πŸ§˜β€β™€οΈMotivation
      • πŸ“–Issuer implementation
    • πŸ–₯️Credential manifest of the credential offer protocol
    • πŸ’°Wallet rendering
      • πŸ“Input descriptors
    • Presentation request query types
      • πŸ§˜β€β™€οΈMotivation
      • πŸ“–Verifier implementation
      • πŸ”DIDAuth
      • QueryByExample
      • QBE Examples
    • βœ…Issuers and Verifiers return codes accepted by wal
    • πŸ”—Universal link
      • πŸ–₯️Access from a desktop viewer
      • πŸ“±Access from smartphone viewer
  • *️Others
    • πŸ“‚Flow between wallet, dApp and Verifier
      • πŸ“±Hybrid dApp onboards a user with VCs
      • πŸ“±dApp onboards a user with VCs
      • πŸ“±dApp adds a user in whitelist
    • πŸ“Indices and tables
      • πŸ“Index
      • πŸ”Search
    • πŸ‘¨β€πŸ’»Show source
Powered by GitBook
On this page
  1. Alme Wallet

Protocols overview

PreviousAlme WalletNextCollecting a verifiable credential

Last updated 2 years ago

For the interaction of the wallet with Issuers and Verifier, which is a decisive function in the implementation of this type of solution, we have retained the specifications of the W3C Presentation Request as well as the Spruce protocol for the management of the QR Code on a HTTPS transport layer. This protocol has the advantage of being quick and easy to implement while providing most of the necessary functions. There are currently several very promising protocols that are being defined or even in production but these seemed to us too complex and ultimately unnecessary for the current use cases which remain simple.

This protocol is described by Spruce: . Talao has enhanced this protocol to adapt it to its own use cases (business logic, governance requirements, etc.).

This protocol occurs when a user wishes to use his wallet to collect credentials or to present them to access resources.

In the following document we will noted the options added by Talao as β€œTalao build”.

πŸ—‚οΈ
https://github.com/spruceid/credible#supported-protocols