Page Properties | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Description
A DID registry is a type of verifiable data registry that can be simply referred to as a role, a system performs to mediate the functionalities like create, verify, update, and deactivate the decentralized identifiers. This is the extension of the in-progress work handled during the last summer (can be accessed here). The project aims to automate the process of creating a secure DID Registry on Github/Gitlab, facilitating easy on-boarding of new organizations and enabling easy management. Decentralized ID (DID) tokens or we can call cryptographically-generated proofs of the organizations can be stored in the verifiable credential registries in an encrypted fashion to achieve the secure DID registry with zero infrastructure cost. The shell script is used to create the initial codebase. This project expects a mentee who is self-motivated and has a lot of passion for cryptography, decentralized identity, and open source.The project DRman has an end goal of developing a stand-alone utility to provision Verifiable Credential Registries [VCR]. The utility can also be used to administer the registry containing credentials issued by the organizations. The functionalities like creation, verification, modification, and revocation of credentials, form the core of this project as it enables the administrator to manage the VCR with ease.
The significant aspects to be considered here are Creation, Onboarding (Enable/Restrict Access) of members, and Management(add/update/revoke) of DIDs.
a) Creation (of DIDRegistryDID Registry): Function to create a DIDRegistry DID Registry for an organization on Github. GitHub Organization can have multiple repositories, same is the case with DID RegistriesGit. 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 (GitHub repo users can be made members of an Organization, with different roles and privileges).e.g., using a combination of GitHub private tokens, GitHub username & users DID).
c) Manage: Function to list APIs that are needed to add/update/revoke access DID’s or (DID DocumentsDocument) saved as files on the repo.
This summer, the project holds a variety of 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.
Additional Information
You can access the current issues at https://github.com/DIDman/DRman/issues
Learning Objectives
The mentee will have an opportunity to learn
- The application and automation process of the Decentralized Identity
- Hyperledger Aries and Ursa code base
- Public key cryptography
- Application of Hyperledger Ursa in enabling Zero-Knowledge proofconverting the architecture into an executable code.
- Hands-on usage of Hyperledger Aries, Ursa, Indy.
- Git, Shell Scripting, RUST.
- Open-source contribution, documentation, and sense of ownership.
- Opportunity to contribute to articles, blog posts or white papers related to the project.
Expected Outcome
- CommandEnhance the existing command-Line utility to automate the process of creating a DID Registry for the members of organizations utilizing Github/Gitlab as Verifiable GitHub Verifiable Credential Registry, On-boarding organizations, and features for easy management
- Proper test cases and documentations
- Codebase maintained with proper read me document
- .
- Features like Onboarding members to the registry, Manage functionality to add/update/revoke access DID’s are expected.
- Markdown tutorial documentation, Swagger API Documentation.
- Present the work at Hyperledger forums.
Relation to Hyperledger
GithubGitHub/Gitlab GitLab based DID registries registries that can be used by Hyperledger Ursa, Hyperledger Aries, or any other Hyperledger Framework that needs to interact with DID Registries
Education Level
Graduate or Masters students master's students preferred. Please do take a look at the skills.
Skills
Exposure to Hyperledger Ursa, hands-on with shell scripting, knowledge of Git, GitHub, or Gitlab is expectedLanguages: Shell Scripting, RUST, <Freedom to choose your own tech stack>
We are looking for someone who has an interest in making things faster, reliable, and manageable by utilizing the power of automation. Also, 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 enhance the potential of DRMan to manage a full-featured DID Registry on Github. GitHub and integrate it with GVCR. The project is expected to be seeded in Hyperledger Labs in future.
Preferred Hours and Length of Internship
Part-time (20 hours a week for 24 weeks, starting in summer and ending in fall)
Mentor(s) Names and Contact Info
Vinod Panicker ( vinod.panicker@wipro.com)
Arun Prakash Jothimani ( arunprakashpj@gmail.com)
Wei Yao (weiyaobiz@outlook.com)