To begin, let's revisit the actors in the EBSI ecosystem:
| Actor | Description |
|---|---|
| Root Trusted Accreditation Organisation (RTAO) | Legal Entity (LE) that can self-accredit and accredit other legal entities to issue certain types of VCs. |
| Trusted Accreditation Organisation (TAO) | Legal entity that accredits issuers with the ability to issue certain types of VCs. |
| Trusted Issuer (TI) | Legal entity that issues verifiable credentials to holders. |
| Holder | Individual or organisation that owns the issued VC and has full control over its handling, use and verification. |
| Verifier | Party who requests and verifies VCs. |
Each actor plays a key role and has unique capabilities within ESBI's Issuers Trust Model, contributing to the ecosystem's trustworthiness and efficiency.
EBSI defines a set of Verifiable Credentials, that allow Legal Entities to register themselves, as well as their different roles in EBSI. Below is a summary of the VCs needed for registration. Please read Issuers Trust Model for more details.
If you need to refresh your knowledge, we recommend revisiting Chapter 5: Issuers Trust Model of the Verifiable Credentials Explained series.
The following subsections will offer a detailed walkthrough on how to become operational in each role, how to issue and revoke credentials, and how each actor's interactions occur within the ecosystem. Additionally, each subsection includes links to instructions and specifications to help you develop these capabilities. We will outline all procedures in a step-by-step format to ensure smooth implementation.
By the end of this section, you will be able to:
- Create a capability map from your collection of user journeys and user stories,
- Draft a comprehensive blueprint,
- Identify the missing capabilities,
- Assess the effort required to build your solution,
- Define your roadmap and timelines,
- Build your first project with EBSI.
Note: During the piloting phase, Root Trusted Accreditation Organisation, Trusted Accreditation Organisation and Trusted Issuer can be onboarded to EBSI by submitting a request to the Support office.