HyperID Use Cases

Simple use cases to show how you can use HyperID
HyperID is a comprehensive decentralized identity and access management platform that enables businesses to automate Web3 wallet creation for customers based on their Web 2.0 accounts such as email or social media. It also allows passwordless authentication, secure verification of user data, and decentralized storage and reuse of KYC data for seamless verification.
With HyperID, users can conveniently operate their personal data on-chain, control how it is shared with others, and create their own Decentralized ID (DID) following the principles of Self-Sovereign Identity (SSI), which results in full regulatory compliance for service providers. Additionally, users can attach off-chain information about themselves with Verifiable Credentials (VCs) and use it across both Web 2.0 and Web3 services.
The platform also offers wallet-to-wallet messaging, gasless transactions, and integration with cross-chain experiences, making it an ideal solution for industry-specific use cases in Metaverses, NFT projects, Gaming, DeFi, DAOs, Platforms, and Enterprises.
Here are some examples of how HyperID can be put to practice:

Case 1: Web 2.0 User Engaging with a Web3 Game/Metaverse

Web2.0 User Onboarding to Web3 Game
A Web 2.0 user that never experienced anything blockchain or crypto related decides to give an exciting new Web3 game a shot. Within minutes, the user registers a HyperID account and signs into the game to begin, seamlessly receiving secure wallet ready to engage with Web3 content, receive NFT rewards, etc.
This case illustrates the usage of the following HyperID platform features:
LEARN MORE [Use Case Technical Description]
  1. 1.
    A Web 2.0 User creates a HyperID account by providing an email and password.
  2. 2.
    HyperID registers a new user and generates a user wallet address during the registration.
  3. 3.
    With the wallet address that is created, the User can easily register to play any Web3 game. If the game integrates the HyperID solution, the User can even use their Web 2.0 credentials to log in: the Web3 game obtains the user wallet address without the User having to do anything.
  4. 4.
    ​
    Web 2.0 User engagement with Web3 applications

Case 2: Web3 User Wants to Buy Music NFT on an NFT Marketplace

Web3 User Buys Music NFT on NFT Marketplace Requiring KYC
A Web3 user discovers that their favorite music artist has dropped a new single in limited quantity of 100. The single is available on a Music NFT Marketplace and available only for customers passed KYC check. User decides to upgrade his HyperID account to pass KYC only once and then use it for all kind of services, including on-chain ones. That's why user claims their MultiPass NFT proving their KYC info, connects wallet to NFT Marketplace, marketplace automatically confirms KYC through MultiPass and allows user to easily purchase the NFT single.
This case illustrates the usage of the following HyperID platform features:
LEARN MORE [Use Case Technical Description]
  1. 1.
    When logging in to HyperID, a User passes KYC (it doesn't matter if he signs in via Web 2.0 or Web3).
  2. 2.
    The User claims an MultiPass NFT:
    2.1 The User navigates to the MultiPass web page.
    2.2 The User initiates the claiming process and provides the desired blockchain ID. HyperID forms the [Claim MultiPass] transaction by filling in the user's KYC information.
    2.3 The User signs the [Claim MultiPass] transaction and sends it to a blockchain (no one but the user can send their MultiPass to the blockchain).
    2.4 The User's MultiPass NFT is presented on-chain (MultiPass smart contract guarantees the data is valid (see the Merkle Tree structure for data verification below).
  3. 3.
    The User goes to an on-chain Marketplace and starts a [Purchase NFT] process (the user proceeds with the same wallet they used to claim a MultiPass).
  4. 4.
    The wallet's KYC status is validated by the marketplace through the use of the getUser method from the HyperID MultiPass NFT collection smart contract. The marketplace confirms the user's KYC status by checking if it meets the required criteria.
  5. 5.
    The User purchases the music NFT (automatically passing the KYC check).
  6. 6.
    ​
    A Web3 User is purchasing an NFT on an NFT marketplace
__

*HyperID ensures MultiPass NFT information is valid using Merkle Tree:

  • MerkleRootHash is calculated for all users who passed KYC
  • MerkleRootHash is updated every time a user passes KYC (whether it's a new KYC or an update of the existing KYC information)
  • HyperID keeps MerkleRootHash up to date on the MultiPass NFT collection smart contract
  • The MultiPass NFT collection smart contract verifies merkleProof before minting a new MultiPass NFT
  • The User receives valid merkleProof from HyperID only: HyperID froms the [Claim NFT] transaction in the [2.1] step of this use case.

Case 3: User Needs to Connect with Their Doctor for a Medical Appointment

User Connects with their Doctor for a Medical Appointment
HyperID user has a medical appointment scheduled with their doctor. They need to discuss their medical test results and receive professional medical advise on their condition and get medical test results. Both the Hospital and the doctor have passed KYB verification. Doctor logs into the chat using HyperID Web 2.0 sign in and confirms their sign-in using their fingerprint.
The user signs into HyperID using their Web3 wallet, creates their account, connects to the chat and proceeds to have their appointment the doctor. The doctor pulls the medical test results from the Lab's secure storage and sends them into the chat with the user. Then user and the doctor are able to join mutual secure chat and exchange sensitive medical information with advanced encryption knowing their communication remain both confidential and compliant.
This case illustrates the usage of the following HyperID platform features:
LEARN MORE [Use Case Technical Description]
  1. 1.
    Both Healthcare Services -a Laboratory and a Doctor- obtain their HyperID accounts and pass KYB.
  2. 2.
    Both the Laboratory and the Doctor have their public certificates in HyperID’s PKI. This means they can establish end-to-end encryption based on their own private key and partner’s public key (using Diffie–Hellman Key Exchange). Healthcare Services use HyperID shared storage to exchange user data with each other.
  3. 3.
    A User signs up in to HyperID with their wallet address and automatically obtains a guest account (as well as a certificate in HyperID's PKI).
  4. 4.
    The User passes KYC to interact with Healthcare Services.
  5. 5.
    The User communicates with the Doctor via end-to-end encrypted chat, using the previously mentioned Diffie–Hellman Key Exchange algorithm based on the User’s and Doctor’s certificates.
  6. 6.
    ​
    A User communicates with a doctor via End-to-End encrypted chat
​

Case 4: Gamer Plays Web 2.0 and Web3 Games and Uses Leaderboard Service to Show Off Their Achievements

A gamer enjoys both traditional Web 2.0 and new Web3 titles. The gamer uses HyperID to access their complete video game library and play any of their favorite game. Games save user progress and achievements into the user profile with the ability to publish them to blockchain.
The gamer also uses (on-chain or off-chain) Leaderboard service to track their achievements, view high scores on the global leaderboard and set new goals to beat the scores of their friends. To do that, the user allows their in-game data saved in HyperID to be shared with Leaderboard.
This case illustrates the use of the following HyperID platform features:
LEARN MORE [Use Case Technical Description]
  1. 1.
    A User signs in to HyperID (Web 2.0 or Web3).
  2. 2.
    The SSO session is established with an end-user device.
  3. 3.
    To sign in to games, the user employs SSO. This eliminates the need for the user to re-enter credentials as they are using the same device. The SSO feature is safeguarded with MFA verification. For each new login attempt, users are required to confirm their actions using the HyperID MFA application (e.g. via biometric authentication).
  4. 4.
    Games can store their data in the HyperID user profile: score, achievements, etc. In this scenario, utilizing HyperID provides the advantage of giving the user complete control over which services and what information they wish to share.
  5. 5.
    Games offer users the option to publish their in-game achievements on-chain.
  6. 6.
    Any third-party service can read and process published user data. One example is a Leaderboard Service, which can organize cross-game tournament and display the latest results based on the user's published in-game data.
  7. 7.
    ​
    A User plays Web 2.0/Web3 games