#Overview

The European Blockchain Services Infrastructure (EBSI) is a standardized blockchain framework initiated by the European Commission and the European Blockchain Partnership to enhance digital identity and public services across Europe. Its use case families include Verifiable Credentials for secure identity verification, Track and Trace for traceability, and Trusted Data Exchange for tamper-proof information exchange.

EBSI leverages blockchain technology to improve interoperability, security, and trust in managing digital identities, ensuring these identities align with regulatory requirements and are universally recognized across member states.

EBSI Verifiable Credentials Family includes:

• VC Exchange Framework
• Trust Chain Model
• Trusted Registries
• Revocation Frameworks
• Specifications

Using the walt.id Issuer & Verifier APIs you can issue and verify EBSI v3 compliant credentials based on the W3C credential data model.

#Requirements

#Accreditations and Trust Chains

Accreditations and Trust Chains are crucial components of the EBSI Trust Framework, ensuring the integrity and reliability of data exchanges within specific scopes. Entities looking to create or participate in EBSI trust chains must first register and get accreditation. We can help you to becoming trusted issuers, participating on trust chains or creating your own on the EBSI conformance / pilot enviroment.

#Issuance Of Credentials

To issue EBSI v3 compliant credentials, simply utilize our regular W3C issuance endpoints as outlined in this guide. Date-related credential attributes, such as "issuanceDate", "issued", "validFrom", and "expirationDate", must follow the format YYYY-MM-DDThh:mm:ssZ. Generating timestamps with the required format can be easily done using our pre-built EBSI data functions. For more info on data functions in general, please go here. The following sub-sections describes the parameters that you need to set up based on your use-case

#Without Trust Framework

You can issue EBSI compliant credentials without specifying any trust chain or framework. You can simply use a did:key with jwk_jcs-pub multicodec.

• issuerKey must correspond to the did:key
• issuerDid must correspond to issuerKey

#Including Trust Framework

You must provide the did:ebsi and the correspoding issuerKey

• issuerKey must correspond to the key registered as a trusted issuer on the EBSI blockchain.
• issuerDid must correspond to issuerKey

Also you might want to specify the term of use and the schemas in the credentialData object

• termsOfUse must correspond to the the value of Accreditation.
• credentialSchema must correspond to the credential schema that you Issuer is accredited for