sander / hierarchical-deterministic-keys

Hierarchical Deterministic Keys for the European Digital Identity Wallet
3 stars 0 forks source link
digital-identity eudi-wallet wallet

Hierarchical Deterministic Keys for the European Digital Identity Wallet

The EU Digital Identity Regulation requires privacy-preserving cryptography in wallet solutions. The regulatory requirements bring several implementation challenges:

  1. How might a wallet solution protect a root key with a high level of assurance?
  2. How might an issuer protect many identity document presentations with this root key in an unlinkable way?
  3. How might a wallet solution present such protected documents?
  4. How might a relying party verify that such a presentation describes a single subject?
  5. How might a wallet solution protect qualified electronic signature or seal creation data using the root key?

The European Commission and Member States are developing a Wallet Toolbox to enable interoperable solutions to challenges such as these. This Toolbox includes the Architecture and Reference Framework. The Large Scale Pilots are implementing and testing the wallet to generate feedback on this Toolbox.

In this repository, Pilot participants contribute to a concrete interoperable solution based on the idea of Hierarchical Deterministic Keys (HDKs) and blinded key proof of possession. This approach is introduced in the Analysis of selective disclosure and zero-knowledge proofs (ETSI TR 119476 version 1.2.1). The Pilot participants aim to evaluate various options, present an appropriate solution, and develop a common specification to enable testing interoperability.

[!NOTE] This information is shared by participants of the Digital Credentials for Europe (DC4EU) Consortium, the EU Digital Identity Wallet Consortium (EWC), and the Potential Consortium. Views and opinions expressed are those of the authors only and do not necessarily reflect those of all Potential members.

Approach

We aim to specify minimum requirements to address challenge 1. To illustrate these requirements, we may refer to some example solutions. Several solutions involve proprietary technologies. A complete discussion is out of scope for this repository.

To address challenges 2–4, we aim to specify an HDK architecture. Quality criteria for this architecture are:

Challenge 5 is out of scope at the moment since the Pilots currently focus on remote qualified signature creation devices. Such solutions may already be built upon the existing common standards. However, the insights regarding challenge 1–4 may lead to valuable insights about alternative solutions to challenge 5.

The challenge of revoking identity documents is relevant to take into account, but designing revocation solutions is out of scope for this work.

The technical reports and specifications in this repository may eventually be used to contribute to open standards. For the current repository, we apply practices inspired by the Community Cryptography Specification Project.

To enable reuse, new contributions to the technical reports and specifications must be provided under either CC BY 4.0 or CC0 1.0.

Contents