Accredit in the Issuers Registry
Obtain a Verifiable Accreditation to Accredit to register in the Issuers Registry.
The Issuers Registry is a registry containing a list of Legal Entities that are authorised to issue certain types of credentials. After you have received the Verifiable Accreditation to Accredit, you must complete the invitation by registering the credential into the Issuers Registry. The following steps will guide you through this process.
Consult the Issuers Registry API page for API instructions on how to register your DID on the Issuers Registry.
Step 1. Request Verifiable Accreditation To Accredit
To receive an invitation from the EBSI Credential Issuer, you must first request a VerifiableAccreditationToAccredit Verifiable Credential.
The Credential Issuer will then invite you to join the Trust Chain, reserving a location and issuing the VerifiableAccreditationToAccredit for that specific location.
Step 2. Obtain issuers-registry:invite access token from the Authorisation Service to write into the Issuers Registry
To request a issuers-registry:invite access token, you need to present proof of ownership of your Verifiable Accreditation to Accredit to the Authorisation Service.
Follow this sequence of API calls to request a issuers-registry:invite access token:
- GET DCQL query: Begin by fetching the DCQL query for the issuers-registry:invite scope.
- POST Token Endpoint: Create and submit a presentation according to the fetched DCQL query that contains proof of ownership of your Verifiable Accreditation to Accredit
For further details, please consult our Access Control guide.
Upon successful submission, the Authorisation Service will issue a short-lived, OAuth 2.0 compatible issuers-registry:invite access token.
Step 3. Register your Verifiable Accreditation to Accredit
The invitation is accepted by registering your Verifiable Accreditation to Accredit into the Issuers Registry.
The Verifiable Authorisation has a reservedAttributeId that defines the location where the authorisation must be registered into. You should build a setAttributeData transaction with attributeId from reservedAttributeId.
The following endpoint must be used to register your Verifiable Accreditation to Accredit into the Issuers Registry:
- Ledger Service - eth_sendRawTransaction - Issuers Registry's setAttributeData method: Begin by fetching the DCQL query for the issuers-registry:invite scope.
Upon successful submission, the Ledger Service will broadcast the transaction to the ledger. In return, you will receive the transaction hash.
You can get the receipt of the transaction by calling the eth_getTransactionReceipt method of Ledger Service.
Receipts for pending transactions are not available, therefore you will have to wait until the transaction has been processed � usually a few seconds. We recommend you to poll the eth_getTransactionReceipt method until the receipt is available.
Once the receipt is available, you can check the status field to know if the transaction succeeded (0x1) or failed (0x0). If the transaction failed, the revertReason field will give you insights about the reason for the failure. You can learn more about the format of the revert reason in Besu's documentation.
The following endpoint must be used to send a signed transaction:
The following endpoint must be used to check the status of the transaction:
After the transaction has been completed, you are officially onboarded as a TAO.
Congratulations!