EBSI (European Blockchain Services Infrastructure) is a permissioned blockchain operated by the European Commission and Member States. It provides distributed trust registries for cross-border use cases that need decentralised verifiable data. DC4EU was the EU-funded large-scale pilot, concluded in 2025, that built the educational and social-security sectoral implementations on top of EBSI + EUDI Wallet.
EBSI core registries
- TIR — Trusted Issuers Registry: which legal entities are accredited to issue what credential types
- TSR — Trusted Schemas Registry: the JSON / ELM schemas to which credentials must conform; append-only (never deleted, only superseded)
- DID Registry:
did:ebsimethod — DIDs anchored on-chain, resolvable by any verifier - Status registries: revocation and suspension status (W3C Bitstring Status List)
How an EBSI credential is verified
- Fetch the credential’s
issDID - Resolve the DID on EBSI (or a country mirror — e.g. RedIRIS for Spain) to get the issuer’s public key + accreditation
- Verify the cryptographic signature on the credential
- Check the issuer’s TIR record — is this issuer authorised for this credential type?
- Check the credential’s status against the issuer’s status list — is it currently valid?
All five steps can be performed offline once registries are cached. No central authority is contacted at verification time — the trust comes from the on-chain registries that all verifiers can independently read.
DC4EU — Digital Credentials for Europe
DC4EU was the EU DIGITAL programme large-scale pilot for credential issuance and verification in education and social security. It concluded in 2025. It tested the wallet-oriented EDC lineage in real institutions ahead of the EUDI Wallet roll-out; it is not a production service.
- 14 European universities and authorities issuing credentials during the pilot
- Sectoral catalogue of attestations: diplomas, transcripts, microcredentials, student cards, EHIC, enrolment certificates — see Sectorial EAA Catalogue for the schema-level rulebook
- Open-source reference implementations:
uself-agent(issuer/verifier),uself-authentic-source(data provider),learner-credential-wallet(holder) - EBSI Conformance v3.2 — the test suite that validates implementations against EBSI requirements
- Protocols: OID4VCI / OID4VP draft 24+, with W3C-VCDM JSON-LD and SD-JWT VC payloads
The DC4EU operational triangle
- Educational authority (institution) → issues attestations
- Citizen → holds them in EUDI-compatible wallet
- Relying party (another institution, employer, public service) → verifies independently
What carries over to the EUDI Wallet
The pilot’s blueprints, the Sectorial EAA Catalogue and its final report are the legacy. Which of its credentials reach the EUDI Wallet in production depends on the formats the implementing acts bind. Since Implementing Regulation (EU) 2026/1731 (in force 11 August 2026), the binding annexes of the EUDI Wallet implementing acts name SD-JWT VC and ISO/IEC mdoc for person identification data and for attestations (ETSI TS 119 472-1 profiles). W3C VCDM is not among them today, but the regulation’s recitals state that wallets should also support it, as the reference format for attestations in education, once new W3C VCDM profiles are available. ARF v3.0 currently treats W3C VCDM as optional and for non-qualified attestations only. See EUDI Wallet.
DC4EU was the proving ground for the wallet-oriented EDC lineage.
Its SD-JWT VC work sits closest to today’s binding wallet formats; its W3C-VCDM work depends on the new W3C VCDM profiles arriving.
