Authentication

When a user wants to login into an application, they will provide their Hive username.
When the user hit the sign-in button, the App will send an authentication request to the HAS and ask the user to start their favorite Private Key Storage Application (PKSA), typically their favorite wallet application installed on their mobile (Hive Keychain for Mobile for example)
The user then opens their wallet and scans the QR code. Alternatively, if the application that the user wants to sign into is a mobile app, the latest can use deep linking and trigger the mobile device to install a wallet app or open it if already installed.
If the wallet stores the keys of the account that want to sign in to, it will ask for approval or refusal of the authentication request by the user.
 
Wallet approval mockup
If the user approves the authentication request, the APP will be informed by the HAS that the user has successfully authentication and that it can proceed with the user sign-in.
The APP has 100% certainty that the account exists and that whoever signs in owns the account's private keys.
Likewise, the user has explicitly identified and approved the application for further interaction.
At this moment, the application session and the users are now registered with the HAS and can communicate with each other through a secure encrypted channel.

Introduction

Signing and Broadcasting Transactions

Last modified 5mo ago

Copy link