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. Altme Saas
  2. Beacon integration

Overview

Beacon is an awasome protocol to allow wallets and dApps to exchange data and sign transactions. All you need about Beacon is available there : https://docs.walletbeacon.io/

Integration with Beacon is extremely simple and you can test it in minutes. To initiate the protocol, it suffices to send a payload of RAW type to the signature of the wallet.

This payload will contain a message to your liking and an URL that you will obtain on the Altme Sandbox platform : https://talao.co

The URL is given just after the fragment β€œ#” with no space. Example with a RAW message :

'Get your Welcome card ! #https://talao.co/sandbox/op/beacon/ormmcdomjv?id=1234'

User will be asked to sign the payload as usual but just after Altme wallet will start a process to request a credential to an issuer or present a credential to a verifier.

User will be asked to sign the payload then to accept or reject the credential offered by an Issuer (or to select the credentials requested by a Verifier).

Those verifiable credentials (https://www.w3.org/TR/vc-data-model/) are json signed file stored in the smartphone.

A verifiable credential of a natural person (user) is stored off-chain as it is personal data. The subject of the credential is the Decentralized IDentity (DID) attached to the wallet. This identity is protected by a private key stored in the wallet aside the crypto privates keys.

Basically Beacon is used to initiate a Self Sovereign Identity standard protocol to request or present verifiable credentials/ verifiable presentations to issuers or verifiers. Other protocols like OpenId 4 SSI or WACI exist.

PreviousBeacon integrationNextVerify the age of your users (+13, +18) in a dApp

Last updated 2 years ago

☁️
πŸ–₯️