Total to date

[IMPACT]

What are DIDs and credentials? Why do we need them?

We all have physical real world credentials already. Your paper passport and plastic card drivers license are good examples. They are physical documentation that you are a legal resident of the country you come from, and proof that you can drive a car. The problem though, is that these cannot be used as proof when you need them on the internet. They are only usable in the physical real world.

Digital credentials are digital versions of these documents in a form that can be used in the (non-physical) internet world.

The DID is your digital identity, to which you can receive these digital proofs and link to you as a digital person.

Why would you want to create a digital credential?

Perhaps you are the manager of a sports club? Perhaps you are a University professor and want to send digital proof to your graduate students for passing a course? You could then make use of DIDs to let your club members or students receive these digital proofs. The possibilities are endless.

What we propose, is to give you the power of creating, receiving and sending digital proofs yourself, without any need for development skills.

Atala PRISM is Cardano's platform for DID and credentials. The functionality is however only available for developers today. We want to make it available for everybody.

-----------

To make sure Atala PRISM platform performs great and grab market-shares in the global DID ecosystem, we need tools that let the non-technical user start making use of DID functionality without being a developer. Adoption and market-share is not achieved by developers, but the number of non-technical users using the technology on a daily basis. Currently, you will need to be a developer to create and issue DIDs and credentials. We propose to create a decentralised application (dapp) to enable regular users to create, issue and receive verifiable credentials to help spark mainstream adoption of DID. The tool will enable this with an intuitive graphical user interface (GUI) that will incorporate drag and drop and other window based functionality the modern user demands of their applications.

Main features of application

• Create new DID or import existing one
• Manage credentials
• Create, issue and revoke credentials

All of this with no need for developer knowledge, in an intuitive window based application.

The application can be run on Windows, Linux and Mac

The main goal of this tool is to abstract away technological details and intricacies and instead let users focus on benefits and usage. The tool will therefore be a general solution needed by many actors mentioned by the challenge statement.

Usability and adaptability of the PRISM platform compared to competing platforms is achieved because we deliver an easy to use tool that can be used without knowing about technical details. Easy to use tools like this, will unlock exponential growth and adoption and give non-technical users a playground for exploring DID and credentials. Being available to everyone will lift the creation of new use cases out of development labs and over to everyone else. This will be a catalyst for real-world implementations on Cardano and Atala PRISM.

Being so user friendly, this tool also will give large benefits to the Small Producer Problem and Last-Mile Problem, as this tool will make DID and credential maintenance achievable for non-technical personnel so they can participate in the global industrial supply chain market without becoming blockchain developers.

The final solution will be for Holders, Issuers and Verifiers. As can be seen in project roadmap, a mobile app for Holders and Verifiers is planned as well.

As a pioneer of the Atala PRISM pioneer first cohort, we have seen that the process of issuing credentials to the blockchain is very time consuming because of having to wait for a specified number of blocks to be produced by the blockchain before the operation is confirmed by Atala PRISM. Tools that do not take this into account will be unusable and will inhibit adoption. We will make sure the user will be unaware of this waiting time because of the functionality we put into the application. Users will instead get subtle notifications when an operation is confirmed. How the user is notified, is of course configurable to put the user in control.

Why desktop application? Why not web application or mobile app?

Both mobile and web applications have been considered and might come in the future for some of the functionality. The desktop application brings best of both alternatives while being the easiest to develop into a fully functional application. We therefore propose desktop application.

Reasons for not doing web application now: In short - decentralisation considerations. We don't want to create a centralised web solution when a clear and better decentralised alternative is available. Having personal data stored safely on your own computer instead of in a centralised web solution, means putting the ID owner in control of their digital identity files. Web applications also need to support the load from potentially thousands of concurrent users and must be available 24/7. Decentralised desktop application is available when you need it and you work with it alone. (Publish times will of course be determined by blockchain load and congestion, but this will only affect time before receiving notifications and confirmations)

Reasons for not doing mobile app now: small screen space and need for typing text might make some of the functions we want to create painful for users without keyboards. As can be seen on the proposed timeline, we are planning to create a mobile app for verification, but full management suite is best solved with a desktop application.

Will installation be difficult? Installation will be as easy as installing regular window applications. No development experience needed or knowledge to build executables from GitHub site. No need for running any other external programs like cardano-node. You can expect a simple "Next"..."Next"..."Finish" install experience.

Risk: Uncertainty regarding when PRISM publication to mainnet

Mitigation: The tool will be created to work with testnet and will be available for community testing once completed. The project will deliver a working tool either way. When PRISM goes mainnet, the tool will be made to work with mainnet as well.

Risk: Change or removal of functionality in PRISM API

Mitigation: The proposal is written with regards to current functionality of the PRISM API. The tool will be updated as new versions of the API are made available. Changes to the API might result in changed functionality of the tool

[FEASIBILITY]

0 - 3 months: Create proof of concept application and demo for the community and get feedback.

The following milestones are planned:

Milestone 1: Proof of concept client application

• Basic PRISM communication protocol
• Concept client layout and design
• Logging and history features

Milestone 2: DID management module

• Create / restore DID
• Key management, add / revoke DID keys
• Local DID vault

Milestone 3: Credential management module

• List of owned credentials
• Credential details
• The visual credential builder (editor)
• Credential issuing
• Credential revoking

3 - 6 months: Documentation and further addition of new functionality based on feedback and feature requests.

12 months: Publish to mainnet when Atala PRISM moves to mainnet

Long term: Extend the application portfolio with mobile app for DID verification (DIDComm)

We ask for funding of the first 6 months of development of proof of concept application. The goal is to provide a MVP to the community by the end of October 2022. The tool will be available for mainnet use when Atala PRISM moves to mainnet.

The attached application design / concept drawing is provided to illustrate what we want the Visual DID and Credential Builder to evolve into. We do need to follow the functionality provided by Atala PRISM platform at any given time and this might result in functionality or user interface of finished product being slightly different than the mockup.

$20000 - Development costs & Documentation. Development of the client application. Documentation and help material will be made available in the client application to provide guidance to the user while using the tool and to get help relevant to the action currently being done in the tool.

$5000 - Public Test, Catalyst community demos and project management. Participate in Catalyst After Town-hall breakout rooms and IOG Developer Discord to demo the library and usage.

The developer will be Andre Brunsal, Elementary Software.

Andre has prior experience from developing a similar type of client application. Keen interest with secure handling of personal information from his background in the defence industry.

Please see full profile on LinkedIn: https://www.linkedin.com/in/andrebrunsal

[AUDITABILITY]

Periodic KPI reports and progress reports sent the Catalyst team will give full insight into project development and progress.

List of KPI we will monitor

• Number of remaining items to develop
• Number of items developed
• Number of downloads by community
• Number of DIDs created with the tool
• Number of credentials issued with the tool

This tool is not targeted towards one particular part of the challenge, but it will be vital for supporting the community with non-developer tools in all of the sub-challenges. Developers are great creators, but the real magic happens when non-developers start making use of the technology in everyday life. Use cases evolve from everyday usage. We are therefore firm believers that this tool will have a large impact for the PRISM community as a whole and drive adoption of DID and credentials.

New proposal.

Please also consider voting the related proposal, Standard SSI Template Library (https://cardano.ideascale.com/c/idea/398478). This library will be tightly integrated with the Visual DID & credential builder tool to give you reusable standard templates to use as starting points for your credentials or be inspired by.