 So, I am Harsh from North Korea, India. I did my beauty tech from BIT University, Belarus, and I'm currently working as a blockchain developer at Anworks. The project that I was involved in was to give Ares the functionality to support fabric as a ledger. And the hyper ledger project that I worked with in this mentorship project was the Fabric and Ares. I was mentored by Kamlesh Nagwari, sir. So I would just first give a project description. Ares is basically a wrapper around Indy and Ursa, such that it enables businesses to build self-solving identity solutions. Now in these solutions, an issuer can issuer credential to a user. And this credential would only and only be kept in a wallet. And this user can verify to the verifier without even revealing the whole credentials through zero knowledge proofs. This works in two ways. Suppose say I'm a user and I have a credential of name Harsh and age 25. Now it's my choice that I can reveal that my name is Harsh to the verifier. And at the same time, it's my choice that I don't want to reveal my age. So the verifier would only check whether if my age is less than 30 and if my age is less than 30, it would be successful or else it won't be. This is what Ares, Indy and Ursa supports. These can be any types of, there can be any type of credentials and various types of verification can happen. Now businesses that are developing blockchain solutions using fabric, say suppose supply chain solutions or solutions in telecom industry, they also want to carry out some sort of verification process. And their need is that they don't want to separate the data that they're putting into the blockchain. So they don't want their domain related transaction to be in fabric and the identity related transaction to be in Indy. Once this project is developed, they would be able to use this Ares wrapper and only one blockchain platform they can use that is fabric for all their needs. It would work for supply chain transactions as well and also identity related transactions. So my objective here was to first develop a chain code in the fabric network and integrate that chain code with AFJ. Then I also had to write the test cases in Ares framework JavaScript that would test the module that is written in AFJ that is integrated with fabric. And the third objective was to demo whole, this whole process of issuance and verification with fabric as a ledger. One of my first deliverable was, see there are three transactions, there are three types of transactions that happen in the Indy ecosystem. One is domain, second is pool and third is config. So as fabric has its own similar types of pool and config transaction, we didn't need to support those transactions here. We only needed to support the domain transactions which are these, dead, atreps, schema, credit devs, revocation registry entry and revocation registry definition. So we needed a chain code of that to be present in fabric. My second deliverable was that there would be a module in AFJ that would interact with the chain code that was that we deployed in deliverable way. My third deliverable was to write test cases that would test this whole module and chain code thing. And the fourth one was to demo the issuance and verification with fabric as a ledger. So we have been able to write the chain code and the module. This project that I was involved with, first it motivated me to look into how the Indy Ares and Ursa ecosystem work and replicate some of that functionality in fabric. So we didn't need to entirely copy paste what Indy does. We picked up the SSI related part that Indy does and how it does it and tried to replicate that in fabric. So it gave me an understanding of how Indy works. And at the same time as I was working on fabric as a ledger and Ares framework JavaScript as a framework, I had to go and dig deeper into that also and to understand it. One challenge that I faced here was while establishing connection from AFJ to fabric, but this when we later solved it, it improved my understanding of how a fabric network works and gave me an understanding of what Docker networks are and how they work. We have some future work for it, like right now the domain specific transactions that I was talking about, there are six transactions. And currently Ares framework JavaScript only supports three of them, like dead schema and credential definition. They have plans for revocation and atrip transaction as well. Once that those are done, we would add that to fabric as well as AFJ. One thing here that we are doing is as we are using Indy wallet to store secret and non-secret records of credentials that are of credentials that are related to SSI solution to work and we are using fabric wallet to store client credentials. So we need to integrate, we can integrate that in the future and create only one wallet for it. And in the future, if the need arrives that any business that is using other blockchain platforms and if they want to do that identity verification process in it, we can add those ledger as well. Now this module would be added to AFJ. We have had a chat with the team and the chain code would be submitted to hyper ledger labs and it would be taken forward from there. Now, as I said, I had two deliverables that I was talking about earlier. I had to write a test case and the demo of issuance and verification through fabric. The second demo of issuance and verification, we are still working on it, but I have the test case prepared. So I would give a demo of it. Okay. So I am running fabric in my local system. This is logs of one of the peers and this is the logs of order. So I will just run the test cases here. Okay. So here it would write the DID schema and credential definition transaction in the fabric blockchain. And so you would be able to see the logs of three transactions occurring here. This gave me a minute. So now the process has started just now. Yeah, so just a second. Yeah. The order has created block six and it has come to the peer logs. The seventh block, the same year, we see block seven and committed block seven. Now one more block could come. Yeah. So the eight block. And here we can see that all the test cases have passed. It has registered the DID schema and credential definition on fabric legend. We are in the process of creating the issuance and verification demo. So now the insights that I gained from this project was whatever you're doing, first research on it and document the whole idea and a plan of how are you going to do it? Then plan it and then implement it. Then the implementation becomes very easy and in short, your life becomes very easy afterwards. And then try to have regular meetings with your mentor and exchange minutes of meeting emails from them with him or her. It would enable you to be in loop of what is happening in the project and what we are going to do forward. And if you're facing any issue, first try to debug it and if it is not being able to solve, approach the open source community through GitHub issues or Rocket Chat, they're easily approachable and very helpful. Last but not the least, thanks to my mentor, Kamlesh sir. He was available at various times and he was also looking at my issues and researching with me and also to the AFG team for the easy response, quick response for my issues, especially to Timo and Bernard. Any, I'm over with my demo. Any question and answers? So actually Kamlesh here, I want to add like because I was the mentor of the project. So working with us is really great and he's very dedicated, committed, even via schedule over meetings on the weekends, Sunday, every Sunday, 12 p.m. And idea about the project like because in the hyper ledger, we have number of projects, number of DLTs and we have libraries and the end goal of all these libraries and projects to work together. And able to use this as a library, like for example, Explorer currently we only use for fabric. So it should support like Beisu and Eroha and other sort of kind of project. Similarly, this AFJ, this Eris framework, Java, JavaScript only support the indie and indie as a ledger. So having a fabric as a ledger is really good move and that's why we started and we proposed this project. And as a future goal, I heard and I'm thinking to propose this as one of the hyper ledger labs. So yeah, thank you. Thank you both so much for presenting and Kamlesh for mentoring and supporting your mentee. And it's great to hear that you are planning to propose this as a ledger labs project. So we're looking forward to hear more about it. And also the other demos you're working on, the assurance and verification. Yeah, yeah, sure, thank you. Yep, thanks again.