Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Identify Snap connects to your currently connected Metamask account by default. To learn how apps can connect to Identify Snap using a non-metamask(external) account, refer to this documentation.
Then, depending on whether you're trying to connect to a metamask account or a non-metamask account, you can call the snap API in the following way:
Notes:
There is no need to pass in options
if you want to store the VC in the Metamask snap state as this is the default behavior however, for storing it in googleDrive
, you will need to specify via this parameter. In order to use googleDrive
, you first need to first configure your google account.
Each VC will automatically be of type VerifiableCredential
by default but if you want to add additional credential types, you can define that with the credTypes
parameter.
The key for the credentialSubject
of the VC will be called vcData
by default but if you want to define your own value for this key, you can pass it in the vcKey
parameter.
Identify Snap currently supports generating VC using jwt
proof format however, there are plans to support additional proof formats such as lds
and EthereumEip712Signature2021
in the future.
Retrieves the currently connected account and the blockchain network the user has selected on Metamask. If it's the first time, the account info is also saved in snap state.
Generates a Verifiable Credential(VC) for the specified value based on the parameters defined. The expiration date is always set to 1 year in the future from the time of its issuance date. The proofformat for the VC will be jwt
by default.
Returns the newly generated VC back to the application.
Some example responses:
Creating a new VC for an EVM address: 0x2e5ff0267b678a0faf9a9f5b0fbf7ac9638b5b57
Creating a new VC for a hedera account id: 0x7d871f006d97498ea338268a956af94ab2e65cdd
Note: Even if the DID for this hedera account is based on its EVM address 0x7d871f006d97498ea338268a956af94ab2e65cdd
, it has an additional field called hederaAccountId
as part of the issuer
and credentialSubject
in the VC which is set to 0.0.15215.
To ease the integration of Identify Snap on an application, we have created a template web application that you can run locally and check out the code in its entirety to learn how you can integrate and interact with various APIs exposed by Identify Snap. Check out the full source code at template application github repository.
You can also check out the API reference to learn how each API works.
Before you can call this API, you will need to first .
Identify Snap connects to your currently connected Metamask account by default. To learn how apps can connect to Identify Snap using a non-metamask(external) account, refer to this .
Then, depending on whether you're trying to connect to a metamask account or a non-metamask account, you can call the snap API in the following way:
Retrieves the currently connected account and the blockchain network the user has selected on Metamask. If it's the first time, the account info is also saved in snap state.
Retrieves the VCs from google drive
Retrieves the VCs from the local Metamask snap state
Compare the VCs from both stores and figure out what VCs are missing in snap state that are present in google drive and what VCs are missing in google drive that are present in snap state
Import the missing VCs from google drive onto Metamask snap state
Export the missing VCs from Metamask snap state onto google drive
Some example responses: