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

On-chain and off-chain access with TezID

PreviousReceive the Verifier data with a webhook in your backendNextVerify other data with other credentials

Last updated 2 years ago

The solution offered by TezID and Altme now provides the developer of a Web3 application on Tezos with this β€œturnkey” solution. The Verifier therefore becomes an off and on chain module providing the Web3 developer with an access point through APIs and entry points on a dedicated smart contract.

It allows the implementation in a few minutes of complex use cases such as multi-criteria onboarding (age group x location x KYC, etc.) while respecting user privacy.

It is possible to access on-chain and off-chain the addresses status through TezID.

At it’s core TezID is a Smart Contract with registered addresses and verified proofs for each address.

TezID is composed of smart contracts to store the list of addresses associated with an on-chain verifier (proof type) and APIs to consult these off-chain addresses.

The documentation is available here

Example of the on-chain view on Ghostnet

For our Over13 example the verifier proof type is tuaitvcrkl , see transaction

In order to guarantee the protection of personal data, the criteria (proof type) are accessible only through the platform .

☁️
πŸͺ™
https://blog.tezid.net/tezid-9d82efbba006
https://github.com/tezid/docs#the-oracle-api
https://ghostnet.tzkt.io/KT1N2HacRzgmKZNmJ6DzRJ9q5bLVUvT6ZdnB/views
https://ghostnet.tzkt.io/tz1iAAJhH465Cf3BnsKQ744XHypQGY1v7Ps9/operations/
https://talao.co