General

• eIDAS Trust framework
• GDPR

• The EU Digital Identity Wallet Consortium (EWC)is a joint effort to leverage the benefits of the proposed EU digital identity in the form of Digital Travel Credentials across the Member States. The EWC intends to build on the reference wallet application to enable uses related to Digital Travel Credentials.

Covers and test these there usecases: 

1. The storage and display of digital travel credentials
2. Payment credential
3. Organizational Digital Identity (ODI) and legal person ID (PID)

2025/ Mar 7th: EWC (LSP) Trust List (https://github.com/EWC-consortium/ewc-trust-list)

2025/ Mar 7th: EWC Wallet Conformance Backend (https://github.com/EWC-consortium/ewc-wallet-conformance-backend) → Implemented RFCs: 

• RFC001: Implements the OID4VCI (OpenID for Verifiable Credential Issuance) workflow for credential issuers.
• RFC002: Implements the OIDC4VP (OpenID for Verifiable Presentations) workflow for verifiers (relying parties).

2025/ Mar 5th: EWC LSP - EUDI Wallet Rulebooks and Data Schemas Electronic Attribute Attestations (https://github.com/EWC-consortium/eudi-wallet-rulebooks-and-schemas).

2025/ Feb 25th: EWC EUDI RFCs (https://github.com/EWC-consortium/eudi-wallet-rfcs).

Insights and deliverables

• POTENTIAL aims to foster innovation, collaboration and growth in six digital identity sectors — governmental services, banking, telecommunications, mobile driving licenses, electronic signatures, and health.

Cover and test these 6 Scenarios:

1. Governmental Services
2. Banking
3. Telecommunications
4. Mobile Driving Licenses
5. Electronic Signatures
6. Health(e-prescriptions) 1

Press

• NOBID is a set of Nordic and Baltic countries who, together with Italy and Germany, will pilot the use of the EU Digital Identity Wallet for authorising payments of products and services.

The project will focus on a single use-case: the use of the EUDI wallet for the authorisation of payments for products and services by the wallet user.

1. Wallet issuing
2. Payment means issuance
3. Payment Acceptance

It includes WP6, WP7 and WP8.

The main goal of Work Package 6 (WP6) in the NOBID project is to demonstrate the ability to issue and revoke Qualified Electronic Attestations of Attributes (QEAAs) of national and international interest.

WP7 is responsible for the detailed design and development of the payment use case in line with the proposed EUDIW Architecture Reference Framework (ARF). This includes identifying high-level solutions in terms of scope, user journey and technical specifications. 

WP8 specific activities include:

• the provision of specifications for the piloting of the signature; 

• the development according to these specifications; 

• the pilot of the implementation for specific use cases (in cooperation with other WPs in NOBID). 

WP7 is currently in the development phase and has set the timeline for the implementation phase. Additionally, it has set out the structure of the impact assessment analysis. 

The second milestone of WP8 targets full technical readiness by the end of Q1 or early Q2 of 2025 for piloting with the defined use cases, the actors involved in the needed roles, and the functionality in place. 

WP6 has no milestone.

• DC4EU provides tangible support to the public and private sectors in the educational and social security sectors by deploying and accessing state-of-the-art trans-European interoperable digital service infrastructures and their integration in a cross-border trust framework.

Cover and test use of the EUDI wallet in these two Areas:

1. The educational sector 
2. The social security domain

WP5 focuses on several critical use cases, including:

1. Cross-border enrolment: Facilitating student enrolment in universities across EU member states using verifiable digital credentials
2. Professional qualification verification: Enabling seamless verification of qualifications for professionals moving between EU countries.
3. Lifelong learning recognition: Supporting the accumulation and recognition of credentials from various learning experiences throughout an individual’s career

DC4EU Wallet Credential Issuance Demo: DC4EU Credential Acquisition (https://www.dc4eu.eu/dc4eu-wallet-credential-issuance-demo-dc4eu-credential-acquisition/)

Timeline on the top of this page

Reports

• Contributions from Identity Foundations (e.g., OpenID Foundation, DIF, Trust Over IP)
• Standardization (W3C, ETSI, ISO)

• W3C DID Core Specification (W3C): Defines a format and methods for Decentralized Identifiers (DIDs), allowing for cryptographic proofs and verifiable control without centralized authorities.
• JSON Web Tokens (JWT), JSON-LD, CBOR, and SD-JWT (IETF): Used for secure, verifiable, and compact digital identity assertions.
• W3C Verifiable Credentials (VC) Data Model (W3C): Specifies a model for issuing, presenting, and verifying credentials in a decentralized manner.
• Decentralized Identity Foundation (DIF) Standards (DIF): Works on interoperability solutions such as DIDComm and secure messaging.
• European eIDAS 2.0 & EBSI (European Blockchain Services Infrastructure): Defines a regulatory framework and infrastructure for trusted digital identity in the EU.
• GNAP (Grant Negotiation and Authorization Protocol): A modern alternative to OAuth 2.0, designed to offer more flexibility, including decentralized architectures. It can work with DIDs (Decentralized Identifiers) and Verifiable Credentials, making it a better fit for distributed identity models.
• ARF (EU commission)
• ISO/IEC 18013-5:2021 establishes interface specifications for the implementation of a driving licence in association with a mobile device. It also  specifies the interface between the mDL and mDL reader and the interface between the mDL reader and the issuing authority infrastructure.

• OIDC
• OIDC4VC (OpenID Connect for Verifiable Credentials) is an extension of OpenID Connect (OIDC) designed to support the issuance, presentation, and verification of Verifiable Credentials (VCs) within decentralized identity ecosystems. It bridges traditional authentication systems (like OAuth 2.0 and OpenID Connect) with Self-Sovereign Identity (SSI) principles by leveraging existing identity protocols to issue, present, and verify Verifiable Credentials (VCs) in a decentralized and user-centric manner.
• OIDC4CI(OpenID Connect for Credential Issuance) is an extension of OpenID Connect (OIDC) that enables the issuance of Verifiable Credentials (VCs) in a decentralized and interoperable way. It is designed to allow identity providers to issue credentials directly to users' digital wallets, bridging the gap between traditional authentication systems and Self-Sovereign Identity (SSI) principles.OIDC4CI follows a process similar to traditional OIDC authentication flows, but instead of issuing an ID token, it issues Verifiable Credentials (VCs).
• Self-Issued OpenID Provider (SIOP v2) (OIDF): Extends OIDC for user-controlled identities without relying on a central identity provider.