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

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

Last updated 2 years ago

CtrlK

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.