 Welcome to Hyperledger Kochi, Kochi Org Book Meetup. So Kochi Org Book is a community initiative that aims to bring in the concept of decentralized identity to reality. It is based on Hyperledger Indie which focuses on self-sovereign identity management. Today's agenda is a quick overview of Kochi Org Book project followed by demos on Popman and email verification service. This meeting will be recorded and uploaded to Hyperledger YouTube. So I now invite Kochi Org Book team to deliver the session. Thank you, Nikhil. Hello, good evening everyone. A warm welcome to our session. Let me introduce myself. My name is Eric Joy. I am part of the Wipro Cybersecurity and Risk Services team. I am a community member of the Kochi Org Book initiative as well. I have Arun Suresh and Sumod Rajan Josh with me today. Can you guys introduce yourself please? Yeah, thank you Eric. Hello everyone, good evening. My name is Arun. I'm a part of Wipro Cybersecurity and Risk Services team. And I'm also a community member of Kochi Org Book initiative. Good evening everyone. My name is Sumod Josh. I'm part of the Wipro Cybersecurity and Risk Services team. And I'm also a active contributor to the Kochi Org Book initiative. Thank you Sumod. Thank you Arun. The agenda for today's session is the overview on Kochi Org Book initiative, then the demo on KOB man utility, demo on email verification service, and later on Q&A sessions. The objective of this session is to introduce you all to the Kochi Org Book initiative. We are looking for community members who are interested to contribute. This is a pure community initiative and the first of its kind from Wipro. Let me start with an overview on Kochi Org Book initiative. All of us have digital identities and we use them to build new relationships, in case existing relationships. Today many sites permit us to log in using Gmail ID or Facebook ID, which is a convenient way for us as we do not need to remember passwords for all our relationships. Well, it has provided convenience for us to build new relationships and avail new service offering. I would like all of you to think through on these lines and let us know. Is it safe to use it? One second. Are we exposing too much information from our end to the likes of Google and Facebook? What all do they know about me? Is it limited to what I have just shared with them or anything more? Do we really own our digital identity? These digital identity management systems are centralized in nature. A single entity has full control on managing our identity information. They decide what information to share and how to share it. This takes the control from our hands to manage our identity details. As a solution to these issues, we are focusing on decentralized identity management leveraging Hyperledger Indie and Ares, which enable individuals to manage their identity information using constant management. We are not discussing about Hyperledger Indie and Ares in this session as it can be done in a separate session. The Orbook is a verifier organization network for the city of Cochin. This is a modeling from the government of British Columbia's The Orbook Initiative. This initiative is the production and the Canadian government is extending these two other provinces of Canada. The objective of this initiative was to enable business entities to avail permits or licenses from the government in a transparent and efficient manner. In Cochin, these are many associations and in the current form it may not be feasible from an ordinary citizen to confirm it. Confirm if the associations are valid or not. We often trust the documents they present. As you know, today's documents are being forged and it is quite easy to miscut anyone using the forged documents. With Cochin Orbook Initiative, each association will now be able to present digitally credentials which has been issued to them from a trusted entity and can be verified by any citizen of Cochin using their mobile water app. Cochin Orbook is a technology demonstrator to launch and de-centralize the identity based utility complaint with the TOIP standards to enable trusted digital verification service for various associations within the city of Cochin. We can schedule a separate session on TOIP foundation later on. Today to avail a service, we need to share a lot of documents to provide our identity for eligibility, etc. Often the whole process takes time and a lot of our effort to follow through till we secure the approval. This utility aims to cut down the red tape and improve the overall efficiency of the current process. Internet-scale digital trust with close to one million digital credentials on the network. Next, let us discuss on EU cases of Cochin Orbook. Medical practitioner getting an expert opinion is not an easy thing today. QoB would permit a citizen to identify a doctor with specific expertise and secure their consultation service without compromising on their privacy. Laws. Similar approach to be leveraged in this case as well. Driving license. Ability for an individual to prove his eligibility to attend a driver's license test. Issuing mark sheets. Enable universities to verify the credentials shared by the student to confirm the eligibility for admission to a course offered by the university. Next, we will discuss about the generic use cases for QoB, which will exist in all of the use cases which we just discussed. Search association organization. The initial actor can be credential requester. A credential requester enters search criteria and is written a list of association matches based on the criteria. Another use case is verify credentials. The initial actor can be claim requester. The claim requester selects the association and the type of the claim and request verification. QoB sends the request to the sovereign blockchain node which verifies the request and returns the verification information to QoB. QoB then presents the verified claims to the claim requester. The next use case can be revoke credentials. The initial actor can be associations here, in this case QoB registry. At any point the claim issuer may revoke a previously issued claim and sends a request to the update the ledger in order to revoke a specific claim. The next use case is issue credentials. Here also the actor can be association. At a predetermined time an association's QoB registry will forward new public data as a CSV extract to a drop location where it is picked by QoB bootstrap tool and convert it to JSON format. QoB agent retrieves the files and loads new association information into Kochi Orbooks searchable database and add verify credentials into the association's wallet. If you take a look at the picture here on the right you'll be able to see the generic use cases, the pictorial representation of generic use cases that I just explained earlier. The benefits are QoB is a decentralized in nature, process building trust among participants, cuts red tape and improve efficiency, display public data in verifiable and authentic manner, empowers individual or entity to manage its identity. If you take a look on the next slide, you'll be able to see the Kochi Orbook subprojects, Kochi Orbook, the Orbook for the city of Cochin. QoB connect wallet application for QoB users. QoB registry, the base code to set up a QoB registry. QoB deflow, QoB decentralized workflow for QoB. QoB man, QoB man CLI for managing the QoB projects. QoB worn, worn network for the city of Cochi on top of sovereign hyper leisure entity. The below is listed the links to each of this project. You'll be able to redirect to the specific projects via the link. Next is the community groups. We have actually divided the community side into four different categories. One for developers, the next one for DevOps engineers. The third one is for solution designing and domain. And fourth is the community. If you take a look on the slide, you'll be able to see the activities of each domain and the requirement, the skill set that is required for each of the domain. For instance, for developers, if they are working on QoB connect project, the skill set that is required here is Android app or Angular skill set. For QoB deflow and worn, Python, Django, all these kinds of skill set are required. Likewise, for DevOps solution designing for community, the skill set that has been required is listed there. If you take a look on the activities for the developers, code refactoring, enhancements, issue fixing, for DevOps engineers, code integration, CACD GitHub, for solution designing, identify potential business use cases and documenting them. For community contribution, all of these activities are involved. We are actually welcoming the contributors here. Current status of QoB project is we have created the repose for the QoB project in the GitHub. Features has been captured and put in as the product backlog, sir. Features tracks as issues under specific project repose. Identified few community members, teams being onboarded to work on each specific project for QoB initiative. Initiated work on some feature leveraging the community members. How to contribute to QoB? Participation in events hosted by Hyperledger QoC community for QoB. Participation in local hackathons. Pick up issues and start submitting pull requests against various QoB code repositories. Participate in use case modeling workshop for QoB. With this, we conclude our first part of the session. We will now proceed with the demo sessions. Then take up on the questions. I hope this is fine with everyone. Let me call upon Arun to walk through the demo on QoB man utility. Over to Arun. Hello, everyone. So we'll be doing a demo on the QoB man CLI, which is a command man utility for the virtue of the initiative. And then we have also built a verification service called QoB email verification service. We are planning to play the video recorded videos of these two. So some more will be the one who's playing it. So how the QoB man utility. Okay. So what QoB man utility does is that it's an easy way of installing all that any elements that we just show. Since these elements are having a certain number of steps that you should really follow to bring it up. And it can be a little bit tough for someone with no previous experience. So QoB man utility deals that with just a simple set of installation and installation. You can just type in a command and then install all those and manage for yourself. That's easy. So more hello, can you hear me? So this is a way of confirming that the QoB code installed. Now QoB man's features gives out the UTPs version 003. The next command is the QoB list command which lists out all the elements that the QoB man UTP can install. And they are also listed on all the versions available for those elements. Now we have listed down QoB man as well as Aries Dev. The QoB man is a dev environment for the QoB man CLI, which actually creates a dev environment for you and your namespace. So that a developer can work on issues or new features that it is. Aries Dev is a Cloud Azure Python project. Now the next command will be to install. Hello, am I horrible now? Yeah, I'm sorry about that. So please continue the video. Okay, so the next command is to install these environments. So to install, we just have to type in the install command which is QoB install. So what can you please play the video? Thank you. QoB install minus cnv. Then mention the environment that you want to install QoB man. Then the version that you want to install minus v and 003, which is the latest version available. Now, once we run that, we'll be prompted to give the user's namespace, which is your GitHub ID so that QoB man can create a fork of QoB from Hyperledger QoC into your name, under your namespace. And the dev environment will be created from your own forked version of QoB man. So once you export it and we run the command again. So right now, it isn't promptive for that. But it says installing hub, which is an extension of GitHub. Now, hub is used to fork the QoB man that was in tree into your own namespace. And that could take a while depending on your network speed. So please do pen us. If this video is audible for everyone. Please read. Are we having an issue with the... Yeah, let me just share it from my end. Okay, thank you. So now that we are done with the QoB man CLI, I hope you are able to see my screen. Okay, then. I don't know how much clear the audio was for you guys. Can you just please confirm like how much you are able to listen to? Was it clear enough or... Okay, so if there are any questions from your end. Can I ask one question, please? Yeah, yeah, sure. Can you please state your name, please? Hi, my name is Nidupam. Okay. Hi, Nidupam. Can you state your question? Yeah, what is QoB CLI? Okay, it's a bashell scripts based project that we created for the purpose of setting up the new projects for... It will be... If we created... If we set up a new project, we'll be able to identify all the steps, right? So once we identify these steps, we will be categorizing it to one of the environment and once we identify it as an environment, we can add it to the QoB project so that from next time onwards, if some developer is trying to set up the same environment, right? He will be able to do that just in a jiffy, like by using a command like a QoB minus ENB install that project's name. So it's for the developers mainly for setting up the project. Yeah, you're welcome. So, folks, we really apologize. We don't know why exactly the audio was not really clear. We will try to make it up for the next time. So any more questions? Yeah, it was a good session, Eric. So can you just explain what the email service actually does in a short one minute so that because the audio was not... We couldn't hear what you are doing in that video. Yeah, of course. Like the QoB email verification service, it's actually an Ares-based project. It has an Ares agent beneath it. So what we just did was like, by using the QR code, we established a connection. If you are aware of what an Ares agent does is, it's actually for making the DAD-based exchanges, the Ares agent is required. So in this project, the Ares agent, we established a connection with an Ares agent. With that connection, we are not really doing anything here. For using that established connection, using the credential, there was some other project that was using the same Ares agent. We might have been able to verify the credential that we created. In this project, we just simply created it. Okay, so I don't know how much the audience is available about the Ares part. Okay, and Nikhil, just to clarify, what we're trying to do here is we're trying to actually create decentralized services, which can be leveraged to actually issue credentials for certain credential proofs for certain credentials. Right now, if you look at it in any online registration form, you'll have to submit your phone number, you'll have to submit your email IDs, you'll have to submit your address details, etc. Now, what we're trying to do is we're trying to actually build, separate out each of these credentials, having a separate decentralized service, leveraging the Ares cloud agent capabilities to follow the system to actually verify your address details or your phone number details or an email, and issue a proof stating that you are the trusted owner of this particular phone number or the email number, or the address that you've shared is a valid address. Now, this could be a credential which you can actually later on leverage to do for establishing, let's say, for example, if you have an entity which is already on-border as part of any DID-based network, and they have their registration process being made as an online service available on the DID network, then definitely this would give you an opportunity for you to actually share these credentials proof and help you to establish your identity with or actually sharing your information in a plain text format. So as part of that initiative, that's cool, right? We have actually decided to break down some of the basic credential information into a set of series of independent decentralized services for offering credential proof. So one of them is actually the email verification service at which we just showed. Okay, I think that made the point clear about the email verification service. So are there any other queries regarding the demo or in general about Kochi or Book Projects? So if anyone have anything, any queries you can ask now? Just to reiterate, your book is more of a technology demonstrated to showcase the capability of how DID can actually enable associations to have their own rhythm and vote themselves as a verifiable organization. And the citizens in a jurisdiction or like a city like Kochi will be able to avail various services using their credential proofs that have been issued to them and avail services in a secure manner whereby there is no compromise to their privacy. Today what happens is any online digital service that you have to avail, you have to share them a lot of your personal information. And by default, many of them ask you a lot of information which may not be really required for you to really avail those services. But the problem there is you end up sharing a lot of your personal information in a plain text format and you have absolutely no idea how this data is going to be stored in the database of the service provider. What kind of security mechanism does a person employ to ensure that your data is not being passed on to someone else? And I'm sure all of you on this call are very much aware of the mess-up that Facebook had done with a lot of personal information being shared with third party vendors which had assaulted a lot of people losing their privacy to external entities. So the objective of the Q&A is going to help establish and showcase the beneficial benefits that you can actually avail by setting up a database network and enabling and empowering the citizens to actually manage identity which in today's digitization world it is of utmost importance. We have government bodies across the world formulating various policies and legal procedures to ensure that the privacy of citizens are maintained and it is not being compromised for availing any kind of digital services. Okay, so if any of the participants have any questions they can ask now. We already have our code available in GitHub. It is hyperlegiccucci.com So it's available because you can take a look at it. In fact, under the hyperlegiccucci name space in GitHub we have quite a number of projects that we have actually included which is part of the overall scope of K.O.B. You guys can take a look at it. Right now we are focusing on K.O.B. Man project and then the other part that we are focusing is on creation of these decentralized services. Okay, so if anyone want to join the hyperlegiccucci.com or K.O.B. project, it's a community initiative. So anyone can participate in the community initiative and be part of the K.O.B. project. I think we have covered almost everything regarding the demo. So, Sumod, if it's fine then can we conclude the session? Yeah, I mean if anyone has any questions that you would like to drop us a mail you can reach out to Nikali, he has got our email IDs. So feel free to drop us a mail if you have any questions. I'm sure you may not extremely apologize for the audio quality that we have today. Okay, so one question is if there is any process for joining the Orgboop project. Do send us a mail, it will help you get onboarded. So can you share your email? Yeah, I'll put it in the chat window. Yeah, sure. Okay, then that was a wonderful session on Kochi Orgboop project. So it's an exciting community initiative based on Hyperlegia Indi and we saw the demo on K.O.B. Man and email verification service. So I hope we can collaborate further on when you have some other, I mean exceeded or gone through another phase in your development phase then we can have another demo on some other initiative that you have done on Kochi Orgboop project. So we really want to have more sessions with you but I think unfortunately, I mean just a suggestion, can we plan something on the weekend? I mean I know it might be of inconvenience to people but at least I think we can definitely do away with these sort of network related issues which is impacting the quality. Yeah, we can all do that. Definitely we can include it in the weekends if it is okay for the presenters also. Yeah, I think that should help us because usually what we have seen is towards the evening, at times we encounter network issues and it disrupts the audio quality as well. So once again, let me extend our apology for that. Yeah, that's no issues for now. We have seen the demo and it was a nice demo and we had a wonderful session and we had the clarification also. So that's all for this session. So I will end it here and you can all, I think we will gather again in one another day and we will share the progress of Kochi Orgboop. And Nikhil, thanks once again for hosting this session for us so that we could get initiated at least on getting people to know what Kochi Orgboop is all about. Definitely we'll have other sessions as well and I'm sure that will help you guys to get up to speed on what we intend to do where we have progressed so far and how you will be able to contribute back to this community initiative. All right. Thank you everyone.