createVC

How to call the API from an app

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:

const snapId = `npm:@hashgraph/hedera-identify-snap`

const externalAccountParams = {
  externalAccount: {
    accountIdOrEvmAddress: '0.0.12345',
    curve: 'ED25519'
  }
}

const vcValue = {
  name: 'KP'
}
const options = {
  // If you want to auto save the generated VCs to multiple stores, you can pass an
  // array like so:
  // store: ['snap', 'googleDrive']
  store: ['snap']
}
const params = {
  metamaskAddress,
  vcKey: 'profile',
  vcValue: vcValue,
  credTypes: ['ProfileNamesCredential'],
  options
  /* 
    Uncomment the below line if you want to connect to a non-metamask account
  */
  // ...externalAccountParams
}

const handleCreateVCAPI = async () => {
  await window.ethereum.request({
    method: 'wallet_invokeSnap',
    params: {
      snapId,
      request: {
        method: 'createVC',
        params: params
      }
    }
  })
}

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.

How the API is handled between the app and snap

What the API does

1. 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.

2. 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.

3. Returns the newly generated VC back to the application.

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.

Live Demo on CodePen

Some things to keep in mind while interacting with the above demo

• If you're getting any errors with the live demo, make sure you go through the FAQs section to learn about what you may be missing. You need to install Metamask in your browser for the live demo to work
• Whenever there is a new version of the IdentifySnap, always make sure to first uninstall the old version of the snap from Metamask and only then try the above demo so it can install the latest version

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.