ANNEX 2 - High Level Requirements - EUDI Wallet
This annex to the ARF 1.4.0 includes high-level requirements (HLRs) related to the EUDI Wallet ecosystem. The requirements define the responsible actor that should implement each requirement. There are no requirements imposed on the Users. All requirements in this Annex only apply in the context of the EUDI Wallet ecosystem. Attestations that are not bound to or used by Wallet Instances are not included in the scope of this Annex. This annex uses the capitalized key words 'SHALL', 'SHOULD' and 'MAY' as specified in RFC 2119, i.e., to indicate requirements, recommendations and options specified in this annex. In addition, 'must' (non-capitalized) is used to indicate an external constraint, i.e., a requirement that is not mandated by this document, but, for instance, by an external standard or specification. The word 'can' indicates a capability, whereas other words, such as 'will', and 'is' or 'are', are intended as statements of fact. Topics presented in section A.2.3 are ordered by a
ANNEX 2 - High Level Requirements A.2 High level requirements A.2.1 Introduction A.2.1.1 Overview This annex to the ARF 1.4.0 includes high-level requirements (HLRs) related to the EUDI Wallet ecosystem. The requirements define the responsible actor that should implement each requirement. There are no requirements imposed on the Users. All requirements in this Annex only apply in the context of the EUDI Wallet ecosystem. Attestations that are not bound to or used by Wallet Instances are not included in the scope of this Annex. A.2.1.2 Key words This annex uses the capitalized key words 'SHALL'
Explore this link on the map →related reading
- Architecture and reference framework - EUDI Walleteu-digital-identity-wallet.github.io
- eudi-doc-standards-and-technical-specifications/docs/technical-specifications/ts3-wallet-unit-attestation.md at main · eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications · GitHubgithub.com
- eudi-doc-architecture-and-reference-framework/docs/discussion-topics/f-digital-credential-api.md at main · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · GitHubgithub.com
- eudi-doc-architecture-and-reference-framework/docs/discussion-topics/x-relying-party-registration.md at main · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · GitHubgithub.com
- eudi-doc-architecture-and-reference-framework/docs/discussion-topics/g-zero-knowledge-proof.md at main · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · GitHubgithub.com
- eudi-doc-standards-and-technical-specifications/docs/technical-specifications/ts4-zkp.md at main · eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications · GitHubgithub.com
- Magic Labs | The fastest way to build onchainmagic.link
- Topic G - Zero Knowledge Proof · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · Discussion #408 · GitHubgithub.com
- thesis.pdfaayushg.com
- Privacy-preserving Solution Using BBS+ for Digital Identity and Walletblog.worldline.tech
- The Hitchhiker's Guide to Ethereum - Delphi Digitalmembers.delphidigital.io
- The MPC-ZKP Architecture | Renegadedocs.renegade.fi