 Hello everybody! First of all, thank you for joining us in the Happy AgroGlobal Forum and thank you for all the TND for our Interest Team. So listening and learning about how you're in Brazil, we are issuing virtual book auditions signed by X509 Certificates. My name is Fernando Marino. I'm a Blockchain Tech Lead at CEPICODE. If you have any question to do in this presentation, please feel free to write in your platform that I will read and answer you. Well, a little bit about me. I am Brazilian, I'm based in Campinas, a city of São Paulo State here in Brazil. I'm a person for innovation, software development and blockchain experts. I have worked with innovation for almost 10 years, including mobile-accessible applications, user experience and close base. In early 2016, I got in touch with the meta-technology and since then I have made development of several concepts here in Brazil and some other pieces as well. Almost all of this development was related to supply chain management solutions and self-sovereign identity. Furthermore, I have published papers and spoken several events in Brazil and abroad. I have an active participation under Hyperledger Community, Hyperledger Brazil, I am one of the Hyperledger chapter members and one of Hyperledger Meetup, São Paulo Coordinator. I have spoken in events of Hyperledger, like Hong Kong Boot Camp in Hyperledger Brazil Boot Camp. Well, talking about a little bit more regarding signing documents to be issued using the VFB credentials protocols. First of all, why does it matter? Why is it interesting to sign these VFB credentials using the X509 certificates? Well, almost places like Brazil and Europe already have digital identity based in the infrastructure of the certificates. So, by the force of the law, several proxies and documents must be signed using these certificates. So, the users have the guarantee of these documents and transactions have the security and the proposition of a real document in the real world. Furthermore, we have to build transitions between the classic systems of digital identity towards the self-sovereign identity. We have to create ways and proxies to allow people to use their identities and what they are currently working in the digital world to use that in the self-sovereign identity ecosystems. This case was developed for a specific case here in Brazil where we were developing a solution for digital prescriptions here in Brazil. And at that time, digital prescriptions must be signed using digital certificates because the Brazilian law said the digital prescription had to be signed by the certificates of a doctor to be issued in the digital manner. So, this project that we developed here in Brazil using the Hyperledger Aries College Agent Python and Hyperledger Indie was a project related to the to create an identity of the doctor and the identity of the patient and to connect them to the doctor. The doctor here has the role of an issuer and he is related to issue the credit to a prescription in the format of a verbal credential. But the patient used this credential, for example, in a in a in a commerce of a pharmacy. This credential must be signed for a digital certificate, a digital certificate that has its roots of ICPBR, the Brazilian Roots Certificate for Digital Identity here. So, we developed a methodology to sign this credential, this verbal credential, using an intermediator agent and just using the agent to agent protocol to send and receives the documents that must be signed. Now, let's explain a little bit more about this methodology in the process that we developed here. First of all, this phone here represents the wallet of the doctor. The doctor sends the documents to be signed to Aries College Agent Python issuer. Okay, that's the Aries of the doctor. Just to inform you, this solution was based is called as a cloud-based solution, which means that the Aries of the doctor is in the cloud. Okay, so the doctor using its application sends the document to be signed for its Aries College Agent Python. These Aries, the application of these Aries doesn't have a web application to select a certificate and sign in the document that will be issued as a credential. So, to sign this credential, these Aries have to send using the GDCOM this document for another Aries, an intermediator Aries. These intermediator Aries have the web application and backend application, which has the process to sign the document that will be issued. Okay, so the Aries College Agent Python off the issuer sends the document's body to be signed using the basic message. This message will be received by the Aries College Agent Python off the intermediator. The intermediator then will trigger an event for its web hook. So, we developed an app that is listening to the events of the Aries College Agent Python off the intermediator. The web hook intermediator forwards the document for the microservices that we developed here called the DSBX509, which means digital signature based off 509 cert files. So, then the web hook will send this message that must be signed for these microservices. And these microservices will storage this document, this body of this document that has to be signed. Okay, that is the schema that we adopted here in Solitia. Okay. Oh, that was the patient's motivation. Sorry, my bad. This was the first patient. After that, the doctor have to access the web application off the Asian intermediator and authenticate itself to obtain the list of the documents that they have to be signed for him. So, the doctor authenticated itself with this agent. This authentication occurs by a QR code that actually has a public invitation by the agent of the intermediator. Okay. If the doctor is already connected with the agent of the intermediator, it's interesting thing, technical thing to talk here. We are not using the outcome, the outbound, we are not using the outbound connection between among these agents. So, we are controlling here, the application of the doctor has internal database and it's known if he's already has an active connection with the public invitation by looking for the public DID of this invitation. Okay. So, the application of the doctor read this public invitation in QR code form. And if it has a connection, an active connection, it will lose this connection to authenticate itself and to identify the doctor, the agent of the doctor and then get the document for this doctor, not for another person. So, when he is looking for the microservices that is storage in the documents that have to be signed, please give him back the documents of this doctor. And then the microservices retrieves these documents of these specific doctors and we'll present this and then we'll present it in form of a list. Okay. Okay. Since the application gets back the list of digital documents to be signed, it will present these documents for the doctor and the doctor will select the document that he'd like to be signed in and then they will, we are using a plugin here from an organization here from Brazil. We are using a plugin to select the X509 certificate and then sign the body of the document. This document is a JSON. This document is the date, is the JSON of the content of a verbal credential. Okay. So, this document has a schema. This schema is the schema that was defined in Hyperledger engine to create this verbal credential. Okay. This document is signed using the 509 certificate and then the application will post this signed document one more time for the microservices and the microservices will then integrate itself with the Aries, send a post for Aries using again the basic message to give it back to the Aries from the issuer. The Aries from the issuer will receive this signed document and will send this event for the WebHook. The WebHook was here of the issuer, was developed to listen to this event and then send an offer for the patient that was received this prescription was created for. So, the WebHook will send an offer for the holder, the patient. The Aries from the patient will receive this credential, this offer, and will notify the holder using the push notification services. It's interesting to see here that these POC that's developed here was entirely developed using just the Aries Code Agent Python, okay? For intermediation, issuance, and the holder. We used one instance for each agent here. Now we can use the functionality of the multi-tenancy of Aries, but when we developed the solution, it was not ready. The version 0.6 of the Aries was not ready yet. Now it is ready. Okay, so since the patient received this notification, he can accept the issuance of this credential, and then the credential will be issued, and this credential will have one attribute more, one attribute related to the digital signature that was used for the verbal accreditation. Okay, how is the outcome that we got from this POC? Well, first of all, we have verbal accreditation that its content was signed by one certificate that is in compliance of our regulation. Another outcome that we have is a document that can be used and checked in only machine-to-machine approach, instead of a signed PDF that usually needs a human verification. That's interesting when we are talking about the digital prescription, because in the pandemic situation here in Brazil, we had remote consult with the doctors and patients, but the doctors are still having to issue prescriptions in a paper, or in a PDF that usually here is not used for integrated services, and to allow that e-commerce regarding pharmacists can use it and check it in an automatically way. When are you using this? Both technology, the self-submarination, I mean the verbal credentials and the digital certificates, we're allowing to the e-commerce of controlled drugs here in Brazil, because when we are talking about some medicines, controlled medicines, it's not easy to sell it in an online way, because you have a regulation that just allows you to use it to buy it. Furthermore, we develop a methodology that can be used to sign any kind of document, not just a prescription, but you can sign a prosecution and other documents that must be signed at this time with the certificates by the force of the law, because when the word is trying the self-submarinated concept, they will still, they still using the other GITAL identity solutions, so it's very important for us to create a self-submarinated solution to build these transitions solutions, to guarantee the users that they are still using the solution that they have, but we are decentralizing the identity, the storage, and managing the handling of the identity of people. So that was the case that I have to show you, the proxies as well, that was the proxies that we used to create a verbal credential signed by digital certificates here in Brazil, and I'm opening for questions. I will stop to share my screen right now and see the question and answers from you.