About • Contributing • Approved RFCs • Implementers • Licensing
This repository is created to align the implementation of digital wallets across the EWC LSP consortium wallet providers. This also ensures all wallet providers can self-test and sign off against the EWC Interoperability Test Bed (ITB).
Feel free to improve the plugin and send us a pull request. If you find any problems, please create an issue in this repo. Once implemented and aligned with the RFCs, wallet providers can raise a PR.
RFCs progress through the following process towards the Large Scale Pilots (LSPs):
To ensure interoperability with other wallets (issuer/holder/verifier) within the European Wallet Consortium (EWC), all wallets, issuer-only, or verifier-only applications must comply with the EWC RFC and complete compliance testing with the EWC Interoperability Test Bed (ITB). For guidance and support, please use the #wallet-support channel in the EWC Slack Workspace.
These are the approved RFCs identified to be specified towards wallet providers, producing reference codes and the EWC Interoperability Test Bed (ITB). The supported verifiable credentials and presentations are specified in the EWC supported format csv file.
| RFC # | RFC Title |
|---|---|
| RFC-001 | Issue Verifiable Credential - v2.0 |
| RFC-002 | Present Verifiable Credentials Workflow - v1.0 |
| RFC-003 | Issue Person Identification Data (PID) - v1.1 |
| RFC-004 | Individual Wallet Unit Attestation - v1.0 |
| RFC-005 | Issue Legal Person Identification Data (LPID) - v1.0 |
| RFC-007 | Payment Wallet Attestation - v1.0 |
| RFC-100 | EWC Interoperability Profile Towards ITB - v2.0 |
Following are the candidates' RFCs taken up. Note that the title, etc, may change.
| RFC # | RFC Title |
|---|---|
| RFC-006 | Organisational Wallet Unit Attestation |
| RFC-008 | Payment Data Confirmation - v0.9 |
| RFC-009 | Payment Transaction Initiation |
| RFC-010 | Document Signing using Long-Term Certificates |
| RFC-011 | Payments with verifiable receipts |
NOTE: The wallets scheduled to be compliant with EWC release 2.0 based on the survey concluded on 15 October 2024 are as given:
Date of availability: 15 October 2024
| Wallet | Link | Holder | Issuer | Verifier |
|---|---|---|---|---|
| iGrant.io Data Wallet | iOS, Android | ✅ | ✅ | ✅ |
| Lissi ID-Wallet | iOS, Android | ✅ | ||
| ValidatedID | iOS, Android | ✅ | ✅ | ✅ |
| Digidentity | iOS, Android | ✅ | ✅ |
Date of availability: 15 November 2024
| Wallet | Link | Holder | Issuer | Verifier |
|---|---|---|---|---|
| iGrant.io Organisation Wallet | Organisation Wallet - Dashboard, DevDocs | ✅ | ✅ | ✅ |
| SICPA Digital Trust Suite | https://docs.dip.sicpa.com/ | ✅ | ✅ | ✅ |
| Archipels | https://app.archipels.io/ | ✅ | ✅ | |
| ValidatedID | https://staging-studio.vidchain.net/login | ✅ | ✅ | |
| Mini Suomi (Vero, Finland) | https://wallet.minisuomi.fi, Api | ✅ | ✅ | ✅ |
| Signicat | ✅ |
The project is co-funded by the European Union. However, the views and opinions expressed are those of the author(s) only and do not necessarily reflect those of the European Union or the granting authority. Neither the European Union nor the granting authority can be held responsible.
Licensed under the Apache 2.0 License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. The IP is handled as part of the EWC IP agreement. Please note that some of the RFCs (Like payments) are not based on Apache 2.0 license.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the LICENSE for the specific language governing permissions and limitations under the License.