Digital Identity / EUDI Wallet Architecture
What you will do: Walk five sample steps: inspect the wallet, issue a sample PID, receive a sample diploma attestation, present selected attributes to the relying-party exercise, then explore a modelled QTSP-signing workflow.
Worked example: Present a sample PID to see the bank refuse the missing degree. Issue the diploma, compare an audience mismatch with a complete presentation for the intended bank, and inspect which PID fields were shared.
Runtime and privacy: The cryptographic exercise runs in this browser. Review the site privacy terms before entering sensitive material; use synthetic inputs for learning and evaluation.
For your role
- Developer / Engineer
- Walk the five steps, EUDI Wallet, PID Issuer, University, Bank (RP) and QTSP (QES): the wallet's Credentials, Hardware Keys and History tabs show what is issued, where the keys live and what each relying party asked for.
- Security Architect
- The PQC Readiness note on the wallet step says today's credentials use P-256 and P-384 and where PQC is expected in the ARF; the Hardware Keys tab is where an architecture has to place the post-quantum keys.
- Researcher / Academic
- Follow the OpenID4VCI issuance and the mDoc and QES steps with the History tab open: the log records each exchange, which is the material to compare against the ARF and the standards it cites.
EUDI Wallet Architecture
Step 1: EUDI Wallet
View your credentials and secure keys.
EUDI Wallet
Managed by: María Elena García
PQC Readiness
The OpenID4VP and OpenID4VCI specifications use classical ECDSA (for example on a P-256 key) in most of their examples. The eIDAS 2.0 regulation (Regulation (EU) 2024/1183) and ARF texts we checked do not mention quantum computing. NIST has standardised ML-DSA and SLH-DSA as post-quantum signatures. Target: the NIS Cooperation Group Coordinated Implementation Roadmap (2025) asks for high-risk use cases to be migrated by the end of 2030 (it does not name EUDI Wallets) — not ETSI TS 119 182-1, which is the unrelated JAdES JSON-signature format spec.
Look for production wallet and verifier tools that inspect the supported encoded profile and check actual validity fields, signatures, issuer trust and applicable status information.
No credentials installed yet.
This is an educational simulation of the EUDI Wallet Architecture and Reference Framework (ARF). Cryptographic keys are generated in-browser using WebCrypto/WASM (OpenSSL) and stored in memory.
Production Tool Capabilities & Verification Requirements
What this sample check establishes: Demonstrates ISO/IEC 18013-5 mDL Mobile Security Object (MSO) COSE signing and W3C Verifiable Credential selective disclosure using post-quantum signatures.
Browser sandbox limitation (non-certification boundary): Runs in browser memory; it does not test smartphone Secure Element hardware signing speed or physical NFC reader antenna power limits.
What to require and test in your production tools:
- COSE (RFC 9052) and JOSE (draft PQ algorithm registrations) support for post-quantum signatures in issuer backends and mobile wallet SDKs.
- BLE / NFC APDU fragmentation and session-establishment latency measured on physical reader terminals against your own transaction-time target.
- Hardware-backed holder binding (DeviceKey in Secure Enclave / StrongBox) with PQC transition path.
Try it
- 1. Predict before you run it.
- 2. Run or change the tool above.
- 3. Explain what the result shows.
Try to issue the University diploma before the PID. What happens?
Next step
Turn it into a plan: Deployment PlaybookThis tool practises the Digital ID module, phase 5 (Pilots & Migration); Deployment Playbook produces a deliverable of that phase.