 Alright then, good morning everyone or good evening or good afternoon depending on the location you are at right now. I am Abhimanyu Sikhaavar. I am a blockchain developer at Argo right now. I have been mentee at Hyperledger and I have been among top get-go-and-feel answers working on different blockchain-based projects. So today I will be speaking on EasyDuser, a tool that we build during my mentorship time along with my mentor. It will simplify the management of endorsement policies of a Hyperledger Fabric Network. So we will be discussing on firstly what are endorsement policies of a Hyperledger Fabric Network. Then we will be discussing about EasyDuser and then finally we will be having a small demonstration of EasyDuser. Firstly, what are endorsement policies in Hyperledger Fabric Network? So for a transaction to be mined or to be included in the ledger, the transaction's data and its state has to be verified by different nodes. But since Hyperledger Fabric is a private blockchain network, the data cannot and should not be read by all the nodes. Like there has to be some kind of policies that governs like this data has to be read by only these nodes and this data can be read by only these nodes. So these policies are called endorsement policies. So endorsement policies governs like this kind of transaction or the transaction coming from this chain code has to be verified by these these these nodes and then only it can be merged in the ledger. Problem with endorsement policies is like at every stage there are multiple endorsement policies in play. Firstly, we have like channel level endorsement policy, then we have chain code level endorsement policy and then finally we have private data collections. So firstly it's not easy to like fetch all them and see what kind of policies there are. Then even fetching them and reading them is kind of hard like you'll have to write long commands with a lot of you'll have to navigate through quite verbose JSON file. So it's kind of a tedious task to handle the endorsement policy. So now what is easy-dozer? Well, easy-dozer simplifies management of these endorsement policies for you. It extracts away all the complexities involved with the endorsement policies and provides you a comparatively easy to use the user interface where you can like see all the endorsement policies involved and you can update all the endorsement policies involved and you can update these endorsement policies. Easy-dozer well allows you to firstly fetch them. It also fetches the endorsement policies of chain code, private data collection and channels and it gives you an easy to read structure. Like you can read them with comparative ease then reading the big JSON file. Then you can update these endorsement policies of the chain code. Then you can like match the certificates in a comparatively easier way. Like if you were doing it in a traditional way, you'll have to write long commands, put a lot of different paths in the commands so that the paths will be of different certificates and it will get quite tedious. So easy-dozer provides you an easier way to do that as well. Lastly it can run on multiple platforms. You can run it on Docker and without Docker and it can run on Linux machine or Mac machine or anything like that. I could go through the structure of easy-dozer now. Firstly there is a front-end which holds all the certificates and all the information. Then there is a server that parses the data and puts together the whole thing. Then there is this peer boundary from Fabric which takes all the data and all the calls and then it executes them on Fabric node. Similarly the data which is coming back from the Fabric node will go to peer boundary and then peer boundary will return some big data which will be then trimmed down by the rest server and it will return it back to the front-end. The data that is being returned to front-end is quite easier to read as compared to what we are originally getting. So now let's have a small demo of easy-dozer. Let me just switch the tab. So here firstly what we need to do is make sure you are having an instance of Appledger Fabric up and running. So when you do something like Docker PS it will give you something like this. Then what you have to do is download a release file. It is available on the GitHub and once you have downloaded that release file you'll have to accept that and once you accept the release file what you will have to do is modify the permissions of the start script. Once you have modified the permissions you can simply start running the start script and you will have an instance of easy-dozer up and running. Now on the second step what we have to do is enter all the details like the URL of our server, the peer address, the order address, MSPEID and all kinds of certificates. Well this is a one-time process so you'll have to just do it once and you won't have to do it again and again. Once you set all the certificates, check on that training on Docker thing. I think you will be good to go and once I have all the certificates let's move forward now. You will be able to see channels policy in this way. I know it's not exactly the best UI but it segregates all the different policies with different colors and easy to read manner. So it shows you a hierarchical way of reading policies. You can go a bit lower and you can see multiple organizations and then at the bottom most of all you'll see policies involved with those organizations like or writers there's only one sign required it can be of either admin or client. Or like for everything you will see policies like this. Now moving forward we can also check private data collections. Well this instance does not have a private data collection but we'll add one by the end of this demonstration. In the meantime we can check out the channels and those policies as well. But for this you'll have to have some user level certificates so again you'll have to add two more certificates but again this is only one time thing you won't have to do it again and again. Once I've picked the certificates you will be able to see like what kind of policy the chain code is having and who are the members. Now moving forward as a tool we can also update the policy of a chain code. So here we are moving forward. What you will have to do is put the endorsement policy like this one and then if you want to add some private data collection as well you can add a JSON file of private data collection and once you do that you'll have to add a version as well. Just make sure you're entering all the details same for all the different nodes or all the different organizations because this thing has to be done by all the organizations. You have to approve the new definition by all the organizations and once they are all approved you'll be able to commit them. So now we will check the commit readiness of this new change. So what we'll be doing is like enter all the details again and then it will be verified like which new update we are talking about and once we enter exactly same details if all the organizations have approved it will show you like all these organizations have approved for you and then you will have to put the, before committing you'll have to do it again though. You'll have to put address of all the organizations and you'll have to actually have their TLSC certificates before committing the definition. And once you do this, once you do this and you'll sign for that along once you do this, you will see like your definition has been committed. Now we have like a private data collection added here and you'll be able to read this new private data collections definition here. And I think this is it for easy to do sir. Just write down any questions you have in the questions box and I'll be happy to answer them. Okay, so we have a question. Does the tool provide an option to endorse from each organization to exchange the signed documents across them? You actually cannot exchange the signed documents across them. You will have to have the different instances running of easy-dozer at different organizations and you can approve the changes. But there have to be a collective system where you can like have certificates of both the organization or all the organizations to commit the change groups new definition. I hope I answered your question. If there are any other questions, just write them down in the chat questions box and I'll be happy to answer them. No questions? All right, then I think I'll be signing off. Thank you for joining my session and thank you for asking this question. Have a good day people. Enjoy the Hyperlegia Global Forum.