.jpg)
Proof of ownership
A user need not reveal the asset and quantity of asset to the
application he can only provide a proof proving that he holds the said asset or has enough assets that is needed for the application to proceed.
Selective visibility
ZK proof of Data Source ownership (e.g. Ethereum wallets, GitHub,
Twitter or Telegram accounts).
Platform Agnostic
Any type of Identification services can be aggregated in the
repositories and generate proof of ownership.
.png)
Smooth and safe user onboarding and authentication
Message signing and transaction routing
Specifications
Data
repository
Allows users to import data and generate proofs for it.
Client
Authentication
This is an application library that allows AleoGuard to be integrated to any Dapp and use the proofs for Sign in.
.png)
Application ID
The ID returned after the repository generates a proof for requested data which will act as representative of the user on that application.
Repository factory
Allows users to create repositories for their data
User Flow
-
User creates a data repository and adds data locally(not stored in any servers). Each dataset has a proof generated which signifies ownership of each data in global scope after verification. These proofs are stored on-chain.
-
User goes to the application that has integrated AleoGuard and connects their repository first which allows the application to know if the required domain is available in the datasets.
-
After which the user is prompted to connect to the site and generates aunique application ID for the user.
-
The user can choose to reveal a specific data set after connecting to the application.
