Description 

The project aims to store the Decentralized ID (DID) tokens in a verifiable credential registry to facilitate easy creation, onboarding, and management. This project was kickstarted earlier and a basic setup is already in place which you can access here. At the moment, we have a strong architecture of GVCR in the Verifiable Credential Model ecosystem, a design document demonstrating the internal workflow of the GVCR (can be accessed here), and the development of a Command-Line utility is in progress which can be accessed here. This project has an end goal of creating a stand-alone utility that could be used to provision and administer DID-based Verifiable credential registries for various organizations utilizing the git infrastructure.  The basic functionalities like creating, verifying, updating, and deactivating DIDs, form the core of this project as it enables the user to manage the DIDs with ease.  The project has a solid use case architecture in place that explains the GVCR Setup, GVCR update, creation, and verification.  The design document at GitHub could give a broader picture to the reader.

The significant aspects to be considered here are Creation, Onboarding(Enable/Restrict Access), and Management(add/update/revoke) of DIDs.

a) Creation (of DIDRegistry): Function to create a DIDRegistry for an organization on Git. The automation is already done for this part and can be tracked at https://github.com/DIDman/DRman/issues/3

b) Onboarding: Function to add enable/restrict access to members of an organization to a repository (e.g Using a combination of GitHub private tokens, GitHub user name & users DID ). 

c) Manage: Function to list APIs that are needed to add/update/revoke access DID’s or (DID Documents) saved as files on the repo.

The creation part is already automated but more scope to make it work flawless once integrated with the system. This summer the project holds interesting automation issues to be addressed that focus more on onboarding and management of the organizations that intend to add themselves to the DID-based Verifiable credential registry.

Feel free to check the parent project DRman.

Additional Information

You can access the current issues at https://github.com/DIDman/DRman/issues

...

• The process of converting the architecture into an executable code
• Hands-on usage of Hyperledger Aries and Ursa code base
• Git, Shell Scripting, RUST
• Open-source contribution, documentation, and sense of ownership

Expected Outcome

• Complete command-Line utility to automate the process of creating a DID Registry for the members of organizations utilizing GitHub Verifiable Credential Registry.
• End to end executable code for the command-Line utility
• Markdown tutorial documentation, Swagger API Documentation
• Expected to record the knowledge via forums, articles, blog posts frequently to demonstrate the findings to other open-source enthusiasts
• Present the work at Hyperledger forums
• Making the project part of Hyperledger Labs

Relation to Hyperledger 

GitHub/Gitlab based DID registries that can be used by Hyperledger Ursa, Hyperledger Aries, or any other Hyperledger Framework that needs to interact with DID Registries 

...

Graduate or master's students preferred. Please do take a look at the skills.

Skills

We are looking for someone who has an interest in automating and the ability to understand the existing architectures that the project holds but don't worry if you are stuck anywhere, we are always there to help. Any high-level understanding of Decentralized Identity is also desirable to some extent. 

Future plans

The plan is to further enhance this as an open-source utility and add more capabilities required to manage a full-featured DID Registry on Github. 

...