 So, hello everyone. My name is Dimitri Barinov and I am from a security organization. What I will talk about, I will talk about our project called TaskBlock and how it is related to the hyperledger foundation and on our plans on developing basically interoperable identity and data exchange solutions. So, a little bit about security. This is just to show that we have been new in the industry, we have been doing identity solutions for a while. We are running a number of the, we are running an identity network based on the decentralized solution, decentralized ledger and hyperledger fabrics in 2019. In Canada, we have millions of users on the network right now, so it's quite successful and this year we have deployed a new solution called TaskBlock and I want to talk a little bit about that. So, basically it is very clear to us and it is very clear to the identity community and the data exchange community that interoperability is the key and the main drivers for interoperability standards come from W3C, from the Diff Foundation and from IFF and that the new solutions in the data exchange and identity world would require vendor independence and would require ledger independence as well. So, that customers of these solutions are not tied to any particular vendor for any particular piece of technology and they can migrate from vendor to vendor and obviously can make their own operational decisions and trust decisions as well. So, for us, it was very clear working with our partners that we must enable standards in the systems and their main standards are verifiable credentials and decentralized identifiers and obviously it was also very clear for us that commercial solutions would require a number of other community-related community-based standards being implemented. Such as, we definitely need to take a close look at the implementation of the HTTP issue and verifier APIs because this is actually a very normal way of how enterprise organizations communicate on the internet. We need to be very careful about using standard credential definitions, presentation request line, which is very, very important in many flows of the solution and then, of course, the core security associated with cloud identity management services, encrypt data vaults, key management services are very important and another very important, of course, is the ability to rely on the W3C standard for the universal wallet and for standard integration methods such as OEDC. So, what we have done, we have introduced the TrustBlock project and the TrustBlock project basically has several very ambitious goals. It has a goal of providing digital governance and interoperability for trusted identities, but also to provide interoperable framework that allows issuance and verification of credentials, user management of identity, and moderation of the flows. It was very important for us. So, basically, we started building the project with an open source project. It is described, it is only GitHub. It has registered, the two registered actually did methods. One is called TrustBlock and another one is called Orb. And what became very evident to us in the middle of the project that we wanted to have an orb method to extend the site tree protocol on which we rely on to ensure that we can offer ledger agnostic deployments. Obviously, we had to support the adapters to ease the integrations and we also wanted to provide options for user chosen data roles that can also offer different services and where the users can securely store their data. And of course, these options should include the option of storing the data on device or in the cloud or at the trusted product. Another important trustable characteristic is that we are ensuring a classic verifiable credential data interaction method and where the data is issued to the device. And we also support a method which is very important for many use cases where we support just-in-time exchanges. So, obviously, we have been involved with Hyperledger Foundation for a number of years. Our first engagement was where we started using the fabric code and contributing to the fabric code. But for the interoperability, we contributed significantly to the areas framework goal and we based our trust law for the equivalent credential services and bullets on areas framework goal. Another important point is that we're using basically ledger as a root of trust for the DITs. But we also wanted to ensure in trust book that organizations have a choice and this is actually a game by we introduce this ORB method and ORB functionality where implementations can be ledger independent. Another important point is that trust book is using DITcom implementation to allow data exchanges with governance and mediation and DITcom, of course, is based on areas RFP and deep work. And right now we're working on basically allowing communication between W3C compliant systems and Indian-based systems, ensuring that we can add privacy mediation, working on integration between areas framework goal and Hyperledger areas. CloudAsianPython or AKpy, as it's known, right? We're obviously very much interested in extending the support to the privacy based on the DBS plus and so on and so forth. So the demo that I wanted to show before we get into the questions period and the demo is actually very important. I wanted to talk a little bit about the demo. So all our demo practical demos, they're based on the artifacts that are developed through the Department of Homeland Security SVAP project, where we are working in partnership with a number of companies including Danube, Tag, Digital Bazaar, Matter, Mainnet, Spherity, Transmute Industries, and where we demonstrate that interoperability based on W3C test suite. So the example that we're going to show, we're going to show this interoperability based on that includes an example where we selected disclosure of some attributes on the network that leverages DBS plus. And we're also obviously developing, we're also using the technology which is based on the development draft standards. So we do include decentralized identifiers, universal resolver, credential handler APIs, and verifiable presentation request specifications and DCH TCP APIs. So maybe now we can show the demo now and see if there are any questions or follow-ups to this. So the demo is the video hopefully you can see it well. My name is Mike Rob Towns, Security. Our goal as Security is to ensure that people can efficiently prove their identity to access the services they need. Our digital identity network allows people to verify their identity by leveraging existing credentials to access the services they want. With this, we are putting people in control of their data. Verifiable credentials play a critical role in our digital identities as documents such as passwords, driver's licenses, and core certificates are regularly used to verify identities. As part of this, we are thrilled to be working with the United States Department of Homeland Security and their SBIP program. This demonstration will show multi-credential presentation with selective disclosure featuring a permanent resident card and a vaccination certificate credential using a trust blind client. So we're all set. It's time to fly. Then he decides to go on a vacation, just gone through and completed this reservation. And this particular small airline is taking advantage of the fact that there are digital wallets out there and issuing a digital booking reference so that they don't have to manage their own. So then he has wallet and collecting his booking. That's it. He's all set to go. Time passes and it's time to check in. There are two options for tailored charter flights. You can do a digital check-in, in which case we'll need a compatible wallet. You're booking a credential, a real TSA UID vaccination group. There is a manual option, but because it has to check some backend databases that can charge you $25 for that, you better to go to the digital web. He's going to check his wallet to make sure he has all of his credentials in order. All right. I'm going to check in. This is a final information check. Do you have your booking reference? Do you have a TSA real ID? There was the U.S. term that goes for qualifies. And do you have a vaccination group from a qualification? Do they don't need their whole vaccination group? They only need to know that you have had that situation. There are two options. You can proceed in the browser or you have a mobile wallet. You can scan a QR code to use your mobile line. You know you have a browser wallet, so you won't proceed with this. Here's the wallet review screen, booking reference will be passed over from our president, Carmen, passed over, and the code will be actually passed over. But only these fields. You're issuing country and that's the limited disclosure capability of the U.S. plus credential. All of these have been now verified. Now go on to your views. What's next for TrustBlock? We'll be working on a cleaner UI. We'll be working on in-person and offline use cases. And we'll be working on a native wallet experience. To learn more, go check out our account pages. Thank you very much. Okay, so that was the demo. In the demo, we were showing basically the web wallet implementation on the TrustBlock system. Once again, the system is completely interoperable and based on the WCC credentials and has been tested against other vendor implementations for the technology. So it's not the same use case. Obviously, there is a TrustBlock channel. You can see more videos if you're interested of this interoperability testing. And there are more videos on the capabilities on the system as well. And if you have any questions or would like to follow up, I would be more than happy to be in the please contact me directly, dmitriyabaryanathatsecureq.com. With that, the session is over. If there are any questions, I would be more than happy to answer them. If not, please feel free to follow me. I don't see any questions in the Q&A. I'd like to thank everybody for coming over. Thank you very much. Bye-bye. Bye-bye.