 Hi, good morning. Good afternoon. Good evening to everyone. My name is Wiyaw. I'm currently a PhD student at New Jersey Institution of Technology, which is located at Norwalk, New Jersey, United States. And I really appreciate that I have the opportunity to introduce my mentorship program also. And first of all, I would like to thank you to my mentors, Mr. Vinod and Panitaka and Mr. Ara Parakash. And also I would like to thank to the hyperledger community to give me this opportunity. So my project is, I think I have the longest title of the project, which is Extended Secure DID Registry for Hyperledger Framework GitHub or GitLab. And if you guys have any questions, just feel free to interrupt. So about this project, in this project, we are going to develop a DID registry manager, aka DRMAC, which is a command line utility that can create a secure DID registry on GitHub or GitLab. And this version is on GitHub. So before that, I would briefly introduce some technologies in this. So the DID registry, which is a type of verifiable data registry, which can be used to simply replace a low system, performs to metadata functionalities such as, for example, creating, verifying, updating, and deactivating the decentralized identifier. And this project aims to automate the process of creating the security DID registry on GitHub or GitLab. And also it's going to be some onboarding features for the new organization and also enables user management. So we have three main objectives in this project. So first of all would be the, and you just click it to create the DID registry. So our system, the DRMAC, which has functions to create a DID registry for a specific organization on GitHub. So we named this DID registry as GVCR. And the GitHub organization can have multiple repositories. The same is the case with the DID registry. So the second objective is about onboarding. So we provide the functions to enable, restrict access to the members of an organization to a repository. And the last objective is to provide the function to manager this DID registry. So here are the delivery levels of our project. So the first delivery level would be the architecture design of the GVCR in the verifiable credential model existence. And then we have to, the delivery level two would be the design documents for the internal workflow of the GVCR, which includes the architecture design, and system design, and also some internal workflows. And the last part of the DD verifiable would be our implementation. So we're going to use our DRMAC command to create and update the GVCR. So before I present the command line, I think it's better to understand what are we going to do. I actually have spent a lot of effort to figure out the entire ecosystem. So I guess most of the audience here maybe know this module. This module we call it as verifiable credential data module, which is used to decentralize the identity manager. So this slide describes those of the core actors and the relationship between them in this ecosystem. So you can see that we have a rule. The first rule is a holder, which is a rule where entity might perform like, which is an entity where a person maybe has some of the holds, it holds the verifiable credential for themselves. So some, some example of the holder would be like students, employees, customers. And then the second rule, which is an issuer. So the issuer is a rule where entity performs to issue a verifiable credential to the holder. So examples of the issuers would be some organizations, governments, or even some individuals. And also, there is a verifiable. So verifiable is a rule that who needs to verify whether the credential is, whether the credential is the holder is valid or not. So for example, like if you're your students, you want to get a job, you want to show your identity to your employees. And then your employees need to verify your identity. So in this situation, the employee would be the verify. So, and the most important here is the verifiable data registry. So this is a rule system to which user to, to store the, which is to, about, in the creation, the verification of the identifies the keys and other verifiable data, such as verifiable credential schema, and also some registry. And the public keys of the issuer, and lots of things. So for here are in our project of this. So currently in some existing have ledger project, projects that there are some existing projects. So for example, the verifiable data registry, which is, the happy ledger India has provided a distributed ledger to for this as a verifiable data registry, and also the happy ledger areas. Some, I noticed that some communities use, use a happy ledger areas to build the issue and verify it. Okay, so back to our project. Oh, okay. So, in our project, so we're going to have the issue and so we're going to replace the issue to the issue in organization and also we, we're going to use multiple GBCR plus distributed ledger to build the, the verifiable data registry. And summer. Okay, so the, the GBCR will swap. Okay, so this is the problem that our GBCR can swap. So we use, we use a system to store the recorded the ideas. Now, so we're going to support the retaining date, which is to produce the document. No, so we use some existing graphic open source the solution to to store to further as the trusted solution. So here we have this is a some use case included in this project. I'm done. I want to introduce this in details and everything is posted on the, on the GitHub. So this is a summer, the internal workflows of the whole system. And so the current early progress. So, with the accomplishments. We are, we are I went through a learning map of the self-solving identity system, which, and which I read a lot of specifications and papers, and from the decentralized identifiers and to the specification of the registrations and also the verifiable predation data model. And, and that's how I, I have deployed the integrated and testing a lot of the existing open source project, which are relevant to our project. So, like, have a large areas who saw indy and the end of the real and what kind of all of which is provided by this job. And also, we have, I have completed the architecture design system design of what you will see. So this is for some pending activities and we're going to do the next attack. So, which is the rest of part of the development and also on the API specification API list. And also our markdown tutorial document and swag, swag API document. This is just a screenshot shows that the repository that we use the screen square to to build. So, this is some recommendations for the for our future work. So in the project scan scope, we have to. To complete some the rest of the implementation. And also, the next, we're going to extend the design to accommodate other data provider, such as GitHub. And also, we are sitting as a half ledger project. And we actually we are seeking the opportunities to be a project as part of the hyper ledger labs. And, and for my, like, this is my personal scope, so I'm planning, continue this project for any improvement documentation or integration to any other platform, and also I'm considering to enhance some features. And, and some of the ideas like to check whether the DRD revocation function were decentralized that came into system are, you know, feasible to be integrated into this project. And also, I noticed that some like a research opportunities in this area. So, hopefully, my mentors can continue advice me on this on this area. Oh, some of the the insights I can actually learn. A lot of in the past six months and I think it's just one size is enough to to make a conclusion. So you just some experience and share that. So at times, so you have to do your research first, always check the official documents and use the internet resources that you can find the answer. And never forget to ask questions. So your mentors and other people in the community will help you and start your code to get your hands dirty and have fun to join the big family. Thank you. Thank you for everyone. Thank you. We appreciate your insight about, you know, getting involved in this project is also relevant to your research endeavors at your university and also you're thinking about potentially proposing this as a project to the hyperledger labs. I appreciate your presentation. I, your mentor Arun is on zoom. Do you have anything to comment or add. Yeah, it was a great experience working with way, and he built multiple architectures and never tired of coming up with an advanced version whenever we give feedback. It was an experience for me to work with way as well as with the winner punnaker who is also in the channel I believe so it was like other one thing to appreciate about ways he most of the time he was able to work autonomously. So when we give him he was able to build it and come up with some finished sequence of architectures as he already has exposure towards the ID as a part of his PhD project. And I hope to see you in the future for the research projects to continue working on the same. And hyperledger is hosting a hyperledger areas and indie workshops in January and February. I encourage you to attend to see, you know, what connections you can make to those projects. And we hope to see you. Looks like there's still a lot to be done about your project. So we hope to see you. Thank you. Yeah, sure. Thank you. Thank you so much.