Creating an Interop Issuer
A zero to sixty guide on this
Last updated
Was this helpful?
A zero to sixty guide on this
Last updated
Was this helpful?
This guide assumes the following:
You have a web application, such as an online learning platform.
You would like to issue Verifiable Credentials from your platform into a learner wallet, such as LearnCard.
You are a participant in JFF's Plugfest II, and/or you would like to follow the major, interoperable standards in the larger ecosystem for issuing credentials.
If that all sounds true, let's get started 🎉
For the purposes of plugfest, we can use the. If you'd like to customize it, these are the 4 main fields you will want to tweak for each achievement:
Name: the primary name for identifying your Verifiable Credential.
Achievement Name: the granular name for the particular achievement claim in your Verifiable Credential.
Description: common description of what this achievement represents.
Narrative: description of how someone earns this achievement.
Image: a picture representation of this achievement.
Ideally, these credentials would be mapped to credential-able items in your platform i.e. for completing a course in your platform.
On the client side, you will need to prepare your web application for issuing credentials. An easy way to achieve interoperability is to use CHAPI.
When you use learnCard.invoke.storeCredentialViaChapiDidAuth(vc)
to send the signed credential to an interoperable wallet, your LearnCard will now use your VC-API endpoint for signing the Verifiable Credential! ✅
Don't have access to the Github Discussions yet? Click here.
Once you've established what credentials you would like to issue, you can checkout the , then return here.
from pnpm, yarn, or npm into your project.
. Reference the
Replace the Test VC with the newCredential()
you defined in .
as your VC-API endpoint. (🚧 guide coming soon).
Configure your upon initialization.
Need extra help, or have a question? Engage in our !
💡
💖
🙌