Wallet 2 Wallet flows

I would like us to consider the eidas regulation, which enables a wallet to be eligible to request credentials from another wallet.

The definition of RP includes Wallets, as evidenced in the text I report below

Article 5a

4. European Digital Identity Wallets shall enable the user, in a manner that is user-friendly, transparent, and traceable by the user, to:

(c) securely authenticate another person’s European Digital Identity Wallet, and receive and share person identification data and electronic attestations of attributes in a secured way between the two European Digital Identity Wallets;

This provides me with the rationale to issue X.509 Certificates or Verifier Attestations to a Wallet Unit, enabling it to function as a Relying Party and allowing OpenID4VP to meet this requirement.

Verifier Attestations could therefore be issued in the form of a Digital Credential (see: GitHub Issue #343) by a trusted third party or be issued by the wallet instance for another subject. This would satisfy the delegation use case, where a holder delegates another holder to act on their behalf, such as driving their car through a shared credential (a proper use of the verb "to share") in a decentralized manner without the need for a third-party auditor.

Start by reviewing the Article 5a excerpt and the referenced OpenID4VP wallet-to-wallet requirement, then compare the proposed X.509 Certificates and Verifier Attestations with GitHub Issue #343. Done would require an agreed design for wallet-to-wallet credential requests and delegation, including how the relying-party role is established.