Skip to content

Release Notes

  • v0.19.0
    • add MDVM Operations overview (6.2) listing all MDVM operations and their authentication
    • add Revoke Vulnerable Device Classes operation (6.2.5), which allows the MSA to report the device classes affected by the vulnerability database and to revoke the Wallet Instances affected by unfixable vulnerabilities (3.1.3)
    • add the Mobile Security Analyst (MSA) as a role (2.1.1) and to the MDVM decomposition (2.1.7)
    • add application-level encryption for wi_rwsca_pin_pubk and the signature of wi_rwsca_pin_prvk to the RWSCA (5.2.2, 5.5) to prevent offline guessing of the RWSCA-PIN
    • identify the Wallet Instance by mdvm_wi_id instead of wi_mdvm_auth_pubk_jkt in revocation, push notification and purge events (3.1.3, 3.1.4, 4.2, 5.2, 6.2, 7.2, 8)
      • the WPB (4.2.1, 4.4) and the RWSCA (5.2.1, 5.4) store the mdvm_wi_id from the mdvm_token at account creation and hold at most one account per mdvm_wi_id
      • remove wi_mdvm_auth_pubk_jkt from the data register (2.2) and the account databases of all backends (4.4, 5.4, 6.2, 7.3)
    • add the privacy notice and the acceptance of the terms of use to the wallet activation before the registration at the MDVM and WPB, and the acceptance of amended terms of use at subsequent start-ups (3.1.1)
    • add the Feature Flag Service (FFS) providing feature flags to the WI, e.g. to enforce a minimum app version (2.1.2, 2.1.4, 2.4, 3.1.1)
    • align the order of the user interactions in the initial start-up with the apps (3.1.1)
    • specify the Android encryption at rest (3.1.1): EncryptedSharedPreferences with AES-256-SIV for preference keys and AES-256-GCM for values, and a SQLCipher database (AES-256-CBC with HMAC-SHA512) whose random passphrase is stored in the encrypted preferences
    • raise the minimum supported iOS version to iOS 26.4 to comply with the BSI TLS requirements (2.5)
    • require security patches not older than 7 months on Android and iOS (2.5)
  • v0.18.0
    • derive wi_rwsca_pin_prvk by rejection sampling according to FIPS 186-5 (5.5): PBKDF2 over user_rwsca_pin and wi_rwsca_pin_salt with a counter, accepting the first valid P-256 private key
    • rename the PID Presentation and EAA Presentation flows to Remote PID Presentation (3.2.2) and Remote EAA Presentation (3.3.2)
    • specify the content of the Key Binding JWT and the mdoc DeviceAuthentication and the RP's verification of the presentation in the Remote PID Presentation (3.2.2), add the access_denied error response if the user denies the presentation (3.2.2, 3.3.2)
    • fix assets in the data register (2.2) and the cryptography chapter (2.3), specify AES256-KWP for rwscd_master_key with plain encryption instead of AEAD (5.2.3)
    • add the information displayed to the user when entering the Transaction Code in the EAA issuance flow (3.3.1), the WI tries a Transaction Code only once
    • add key and token lifetimes for WIA/WTE PKI, update lifetimes for challenge signing keys (2.3)
    • revoke WTEs by manually informing the PID Provider instead of requesting the ecosystem PKI to revoke the WTE signing certificate, and adapt the revocation chaining accordingly (3.1.3)
    • minor fixes and clarification in the PID issuance flow (3.2.1)
    • remove the WIA renewal and the wpb_client_instance_id from the Create WIA operation (4.2.2) and the data register (2.2), the WPB uses a new Status List entry wpb_wia_status for every WIA (2.3, 4.4)
  • v0.17.0
    • add a list of all occasions when the mdvm_token is renewed to the MDVM Token section (6.2)
    • enforce the one-time use of the authentication challenges (2.3.4): the WB (4.2.1, 4.2.2), the RWSCA (5.2.1, 5.2.2, 5.2.3), the MDVM (6.2) and the PNS (7.2.1) store a challenge that was used in a request until it expires and reject any further request using the same challenge
    • add Wallet Invocation to the Wallet Activation chapter (3.1.1) listing the supported custom URL schemes
    • rename Wallet Backend (WB) to Wallet Provider Backend (WPB)
    • name the JWK thumbprint of wi_mdvm_auth_pubk as wi_mdvm_auth_pubk_jkt, the canonical identifier of a WI across all backends (2.2, 8)
    • various fixes of miss-named data assets in sequence diagrams and descriptions
    • use PBKDF2 instead of HKDF to derive wi_rwsca_pin_prvk (5.2.2)
  • v0.16.0
    • add Design System chapter (9.4) linking the Figma Design System for the EUDI Wallet DE App
    • fix decomposition graphic (2.2) to connect Message Queue to RWSCA instead of RWSCD
    • fix assets in the cryptography chapter (2.3)
    • simplify the lifecycle dependencies of the WB's internal artifacts (2.4)
    • abort the Create Key and Sign Data operations (5.2.3) if the rwsca_pin_retry_counter has reached 0
    • mark the blocklist of trivial RWSCA-PINs as not supported during the initial launch (5.2.2, 5.5)
    • add note to the EAA issuance flow (3.3.1) that the WI will not support key attestations initially, the Wallet Instance Attestation assures the EAA Provider that key-bound EAAs are bound to the strongest local HKS
  • v0.15.0
    • add Wallet Dashboard chapter (3.1.2) with credential overview, credential inspection and transaction log
    • add Wallet Deletion flow (3.1.4), including app deletion and backend data retention strategy
      • add the last-seen timestamp to the MDVM account database (6.2), which is evaluated by the MDVM to identify the accounts that exceeded the data retention period
      • renew the mdvm_token during subsequent start-ups (3.1.1), if the last renewal is older than one month, to keep the last-seen timestamp up-to-date
      • add the purge queue (8.3) that propagates the deletion of stale accounts between the backends
      • add Purge Account operation (6.2.4) to the MDVM chapter and trigger the Purge Account operations of the WB (4.2.3), the RWSCA (5.2.5) and the PNS (7.2.3) by purge events
    • add EAA presentation flow (3.3.2) with same-device and cross-device flow as well as cryptographic and claims-based holder binding
    • add EAA deletion flow (3.3.3) as a local deletion of the EAA credentials and local key material
    • remove Play Integrity from the MDVM, Android Key Attestation and RASP remain the platform integrity mechanisms on Android (6)
      • remove the App Attestation Guidelines appendix
    • remove the status information of the Wallet Trust Evidence (rwsca_wte_status), WTE revocation is done by revoking the WTE signing certificate (5.6)
    • add cipher TLS_CHACHA20_POLY1305_SHA256 as a deviation from BSI TR-02102-2 (2.4.1)
    • add CT log monitoring of Wallet Provider domains (2.4.2)
  • v0.14.0
    • add EAA issuance flow (3.3.1) with initial issuance (Authorization Code and Pre-Authorized Code Flow); re-issuance is tbd
      • add Presentation during Issuance (3.3.1) describing the nested OpenID4VP flow used within the Authorization Code Flow until OpenID4VCI 1.1's Interactive Authorization Endpoint is supported
    • add Push Notification Service (PNS) (7)
      • add PNS component to the decomposition (2.1.2)
      • add Create, Update and Delete Account (7.2.1) and Send Push Notification (7.2.2) operations
      • register the push notification token during Wallet Activation (3.1.1) and renew it monthly on subsequent start-ups
    • add Message Queue (MQ) component (8)
      • add MQ component to the decomposition (2.1.2)
      • link usage of push notifications event and revocation events to the message queue component
    • add Wallet Instance self-locking in the Wallet Revocation chapter (3.1.3)
      • add opt-in push notifications to trigger the Wallet Instance self-locking
    • rename pp_wia_pop_nonce to pp_wia_pop_challenge
  • v0.13.0
    • add overview of standards and design choices to the introduction of the PID issuance flow (3.2.1) and PID Presentation flow (3.2.2)
    • add Communication Channels chapter (2.4) with a register of communication channels, transport security and authentication properties, add TLS requirements (2.4.1)
    • add minimum mobile device requirements (2.5)
    • add details on access certificate and registration certificate for signed metadata and consent screen in the PID issuance flow (3.2.1)
    • add details on access certificate and registration certificate for signed presentation request, over-asking and consent screen on the PID presentation flow (3.2.2)
  • v0.12.0
    • add optional PID re-issuance to PID Presentation flow, due to low number or expiry of remaining PID Credential batch, define conditions and thresholds for refresh
    • remove the duplicate Wallet Trust Evidence (WTE) section from the PID issuance flow
    • revocation events are propagated between the backend services through a shared revocation queue
    • add Revoke Account operations to the WB, RWSCA and MDVM chapters
  • v0.11.0
    • restructure Wallet Backend (WB) chapter
      • add Delete Account operation
      • add details about revocation with Status List
    • make the revocation code static
    • updates to decomposition with regard to components and communication links related to revocation
    • add revocation with Token Status List to the Wallet Trust Evidence (WTE)
    • add details DPoP parameters and contained key attestations in the PID issuance flow
    • clarifications on encryption at rest
    • editorial changes on MDVM
  • v0.10.0
    • define encryption at rest for the Wallet Instance
    • provide details on Platform Authenticator
    • RWSCA PIN retry counter allows a maximum of 3 tries
  • v0.9.1
    • restructure documentation
    • provide chapter/section numbering
    • add changelog inside the documentation
    • smaller editorial fixes
  • v0.8.0
    • add section for key and token lifecycle to cryptography chapter
    • add UI/UX section on accessibility
    • add section for key attestation and chain revocation (for PID)
    • updates to align WIA and WTE with ETSI draft 119 476-3
    • minor fixes of example data
  • v0.7.0
    • add wallet revocation
      • user-initiated wallet revocation
      • MDVM-initiated wallet revocation
    • minor editorial fixes
  • v0.6.0
    • add PID deletion flow
  • v0.5.1
    • editorial fixes
  • v0.5.0
    • redesign of Remote WSCA flow
      • PIN session token to remove client side caching
      • direct PKCS#11 calling HSM instead of external KMS
      • wrapped keys are stored on the Wallet Instance
      • integration of MDVM token
    • small changes and fixes for MDVM flows
    • clearly mark sub flows in sequence diagrams
  • v0.4.0
    • added UI sitemap / user flow chapter
      • App Onboarding (Wallet Activation)
      • PID Issuance
      • Set eID Card PIN
      • PID Inspection
      • PID Presentation
  • v0.3.1
    • splitting Remote WSCD into Remote WSCD and Remote WSCA
      • updating decomposition diagrams
      • updating data register, flows and other occurrences
  • v0.3.0
    • wrapped keys from Remote WSCD are bound to Wallet Instance accounts and stored on the Wallet Instance app
    • update cryptography chapter to clarify boundaries of WSCD and WSCA
  • v0.2.2
    • editorial changes (moving MDVM flows to the MDVM chapter)
  • v0.2.1
    • editorial fix
  • v0.2.0
    • add mobile device vulnerability management (MDVM) to decomposition as a separate service
    • add MDVM flows for registration and renewal of MDVM token
    • integrate MDVM token into RWSCD registration, RWSCD operations, WB registration and WB wallet attestation
  • v0.1.1
    • fix plantuml diagrams to be included
  • v0.1.0
    • initial release using versioning of Gitlab pages generated with mkdocs
  • v0.0.3
    • add MDVM section with MDVM signals
    • updates on overall decomposition
    • updates on RWSCD decomposition
    • updates on MDVM decomposition
    • fixes on WIA content and description
  • v0.0.2
    • removing deploy steps from index file
  • v0.0.1
    • added UI/UX process description
    • updated terminology regarding WSCA / WSCD
  • 1st of October 2025
    • added wallet activation flow
    • added PID presentation flow
    • added Mobile Device Vulnerability Management in the decomposition
    • added Mobile Device Vulnerability Management in the Remote WSCD flows
  • 10th of July 2025
  • initial release