The Trust Bridge: Real-World Identity Beyond Compliance and Code
summary
eIDAS 2.0 implementation focuses on concrete requirements: Omnibus (protocols, architecture) defines wallet–relying‑party interactions, national registration of relying parties issues certificates, and the sandbox tests integrations. Remote onboarding must use electronic digital documents (video‑ID of a physical card is not enough) and bind proofs to applicants within minutes or seconds. Anti‑money‑laundering rules (AMLD6) feed directly into eIDAS, requiring an audit trail and no storage of raw biometrics; qualified electronic signatures can be issued from the wallet.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:05Shift to mandatory regulations
- 2:30Key regulations for identity trust
- 6:05New authority and standards
- 7:54Technical specs for remote onboarding
- 9:21Digital wallets for verification
- 11:09eIDAS and AMLD6 bridging
- 13:58Compliance steps for participants
- 14:41Closing and sandbox
related talks
21mCombining Self-Sovereign Identity and eIDAS
13meIDAS Remote Signing: Lessons from Trust Service Provider Cases
48mEverything Everywhere All at Once: The European ID Wallet Ecosystem
38mDigital Identity - Improving the necessary evil
16mHow eIDs are already changing the insurance industry (or could)
50mEurope Gets its Identity Back
20mIdentification modules in the eIDAS context – use cases and opportunities
18mElectronic Signatures, Seals and ID Wallets – What You Need to Know for Your Projects Now