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

Introduction

Internet applications suffer from the lack of proper identity management. TCP/IP was designed as a network of networks with the sole purpose of identifying machines and not their users. The rise of the web in the 90s favored the emergence of servers that concentrated user access and capitalized on stored data to the point of being today the identity providers of a significant part of humanity. The GAFAMs implemented an identity layer above TCP/IP because there was none and we all missed it.

For about ten years now, the concern for the protection of personal data has become a major subject for policies and new paths have been opened up, such as in particular the concepts of Self Sovereign Identity (SSI) which allows everyone to have their data in the format electronically as is done for paper data.

Web3 suffers like web2 from the lack of proper identity management. On the other hand, there are particularities which make SSI integration even more difficult:

  • The users of web3 applications are even less docile than those of internet applications. they are more concerned with the management of their data because decentralized finance has already done its work.

  • Web3 applications require on-chain data integration but the verifiable credentials we use in the SSI are off-chain data container by construction so we have to find solutions, tricks to make a bridge that allow both to use the technology provided by the blockchain while guaranteeing the protection of user data.

NextWhat is Self Sovereign Identity ?

Last updated 2 years ago

🧾