On this proposal you will constantly see a relation between RootsWallet and WAL-CLI. This is because to build a DID ecosystem different types of wallets are necessary. At one side we need the holder wallet; It takes the form of a mobile application that individuals will use to receive, store and present credentials. On the other side we require the organization wallet; It’s a more intricate application used by institutions and organization to manage the issuance, revocation, and verification of holder’s credentials.
RootsID team is working on RootsWallet to cover the holder wallet and WAL-CLI to fill the organizational wallet gap. The first release of WAL-CLI was funded on the last campaign and is available here.
The presentation and exchange protocols refer to the messages interchanged between wallets to perform an action, such as, request the issuance of a credential or request the presentation of a credential.
This proposal covers the development of the functionality required to perform proof presentation and credential issuance between a WAL-CLI instance and RootsWallet. We will implement the latest specifications and protocols from DIF and Aries Interoperability Profiles, specifically:
- DIF Presentation Exchange 2.0
- DIF WACI Presentation Exchange
- Hyperledger Aries RFC 0454 - Present Proof Protocol 2.0
- Hyperledger Aries RFC 0453 - Issue Credential Protocol 2.0
The produced code will be open sourced with Apache 2.0 licensing and uploaded to our public repository. Documentation will be provided with build and run guidelines and tutorials.
To foster a decentralized identity ecosystem there are several technical components that must exist for solutions to be realizable. IOG has done a great job providing Atala PRISM sdk and PRISM Nodes, but that is not enough, there are gaps that need to be covered before a DID ecosystem can be built. The purpose of WAL-CLI is to work in conjunction with RootsWallet and complete the missing parts that we need to get the ecosystem going. The way we address the challenge is by providing open source technology required to start building.
We have identified and analyzed two potential risks:
- Protocol standardization: We are implementing protocols that should be standard and well adopted. However, as we are in the early stage of the industry, some of the protocols are in the process of being standardized and are subject to change, or even be replaced. In WAL-CLI scenario our concern is to be interoperable with RootsWallet so to mitigate the risk this project will be closely aligned with RootsWallet development.
- Time allocation: the other challenge we may face is the ability to allocate enough time to deliver the project in time. To mitigate the risk we have enlisted another community member to work on this proposal.