 Thank you, Brian, for the introduction. I was thinking for a while how to best explain the topic. And then it turned out that perhaps what I would like to do today is take you through a story that actually goes well before COVID and well before health credentials, because this is where the discussions about blockchain hyperledger actually started as an opportunity to use the technology. So if we look back in 2019 in Ayata, we operate an activity which is called Air Industry Retailing think tank, a couple of more think tanks as well. And we look at how we could use technology to solve very specific business problems. And I'm sure that many of you would have traveled before at least the COVID took place. And your experience was not the most seamless one. Generally speaking, we would travel, we would get tickets from one company, we would get train tickets from someone else. We would have all maybe pieces of paper, some of it was on the mobile phone, but definitely not holding together. And if something happened, maybe a bad weather, big flight delays, it has been really, really difficult to put back the experience together. And thinking about it, we have been working with airlines on how we could make the experience much more seamless for the passenger. And how could we actually make sure that the communication between the providers of different services is holding easily together. Now, with that idea, we were thinking, well, wouldn't it be nice if I, as a traveler, had in my mobile device, literally something like cards that represent individual segments of the journey, I receive them from my providers. Equally, I could have cards that I share with my providers that show, for example, my preferences, or even search for the travel where I would like to go. And I will be the one who will literally control who can share which information with whom. For example, if my flight is delayed, perhaps the airline could help me with the accommodation based on the preferences in which type of hotel I would like to stay in. So all this we imagined as one seamless experience that relies on the possibility of using a mobile device and a wallet and a mobile device. And since it has been in 2019, and in 2019, there was lots of discussions about distributed ledger technology sovereign. What we imagined is, and if you look on the left-hand side, called truly my concept, we would literally factor in those activities that are taking place at that time. How could my as a traveler carry my identity in the wallet? That was the one ID project and go seamlessly and smoothly through the entire journey, couple of airports, for example. How could I equally carry my tickets or orders in the same wallet? And we have added the preferences of the traveler as well as other types of travel experiences might have been hotel training. And under this, if this is all on my device, I might carry it on the mobile phone. I might perhaps also have a version of it stored and at a part of cloud that I control. I want to be able to communicate directly with those services providers that might be providing me some service. And equally, I want to permission that perhaps even in some cases, the services providers can talk with each other about me on topics that specifically I have allowed that they can happen. And what we needed under as a fabric to underline this, we needed some sort of way of identifying each other, authenticating each other. And we imagined that the distributed ledger might be able to do this for us. Now, this all happened in 2019. And early 2020, we started having discussions about perhaps we could build parts of it. Maybe there were also already some trials how we could pilot at least the identity in the wallet. Everyone was motivated to go and try to use the technology. But as you all know, it was early 2020, what happened then? If I fast forward to January 2021, we had a massive, massive drop in the passenger demand because for good reasons, obviously the individual governments protected their own countries by limiting the travel. And that had a huge impact on the industry. It was a really huge test of resilience and robustness of the industry. But what happened with that is obviously the governments introduced new requirements passengers were asked to show the contact tracing data, for example, to see with whom they have been in contact. Equally, they may be required today to bring test results, vaccination results, perhaps results or certificates of recovery. And all this in today's travel, where we are at 30% of pre-COVID, because the staff at the airports is required to check all those documents. It increases the waiting time for the passengers. It increases the queue. And fundamentally, it increases the risks when it comes to hygiene because more people need to group at one place so the documents can be checked. And that in itself has created a huge driver going back to using the same concepts that we were thinking before the crisis because without any process improvements, if people start traveling in the summer, for example, in Europe, if we imagine getting to something like 75% of pre-COVID, it might be more than five hours per trip, in some cases even up to eight hours per trip in delays of processes just because of checking documentation. So the question is, how could we, all of us, the governments, the airlines, with the passengers move to digital processes so that we can actually test, we can literally test all the certificates digitally and avoid big queues and potentially chaos at the airports. So from an idea that was very just customer centric driven how to improve a journey, we come to an immediate challenge and that is how to make sure we don't have to papers at the airports. If you look at it from the perspective of the individual parties involved, obviously, what do we need as passengers? We need to know, where can I get tested? What kind of vaccine I might need? And I need to know what are the rules in the individual countries that I might be traveling to so that I know I can easily travel. Now, while one could easily say to your passenger, you should know it yourself, obviously the airlines and transport services providers, they need to be able to share this information with the passengers because passengers, if they plan for a travel, they expect, yeah, they will also give me that advice, how do I travel? So they need to be able to make sure that passengers know what can be done and how can be done. The governments, on the other hand, if you come a present a certificate, they need to be able to know that it is authentic and that it matches to the person who has been actually, the person who has been tested is the person who travels. And then one of the questions we were trying to resolve is the laboratories themselves, they need to be able to be recognized as someone who actually issued the certificate. So with that, airlines requested Ayata to focus on free things. It has been, how can we advocate for the global sort of approach? And I will get to details a little bit later, work on the standards and also try to demonstrate possible solutions that would meet a principles that the airlines has set because if you look at the problem from the airline perspective, it is not just about reducing the cues or finding a magical solution, it is about solving a problem in a very structured way. If we need to share data about passengers that is deeply personal, it might be health data, there are a couple of very fundamental principles that we have set ourselves. First, and that's a very obvious one, any solution needs to be interoperable, consistent and scalable and affordable to implement because we are in a major crisis. And this is where using technology standards that exist using open source comes in as very important factors. The second one is, as I said, it is medical data. That means that we have to make sure that the data stay with the passenger or are exchanged between the passenger and the party who can receive them. And surely as a transport services provider, I'm not necessarily the one who would need to know exactly what vaccine you had, where were you vaccinated, where were you tested. So the airlines themselves, they should not be involved in collecting the data, but the automation and standardization is absolutely fundamental to avoid the mess. And the last point is, and it's extremely important, remember I started talking about queues at the airports, anything that we can do that declarations about health or any travel type declarations can be done before the actual journey before I arrive at the airport that helps to smooth the process and helps to avoid the queues. So with these fundamental principles, as I said, a line said, please do help us advocate, that is the traditional role of IATA, work on standards based on the general technology standards. This is where verifiable credentials, decentralized identifiers come in and build an example of how such solution could work, especially for those situations that perhaps not in every country, the governments may not be ready to put the solutions in place or it might help to give a good example. So with that, IATA said to build a travel pass and what I would like to do in just a couple of minutes, give you a very specific example of how it works. If we put ourselves into the shoes of the traveler, what I can do is I can take my passport, scan it, or perhaps with character recognition, import it into my wallet and with that passport we can create a verifiable credential that carries the passport as a payload because the passport itself might be digitally signed but it is a package on its own on the passport. We also might need for the journey to actually have the itinerary where we are going to travel because then it depends on the rules where do I need for documents. So I am set, I have my wallet, I have my identity in the wallet. Comes COVID situation, what do I need? I might need to actually be able to get tests from different lumps and those lumps themselves, they need to be recognized and exist in the ecosystem. So eventually on the receiving side, we can authenticate that the information indeed came from the lumps. So one of the options is I might, for example, using the centralized identifier, spear exchange, identify myself to the lab, receive the lab results. You might know that there are over the time number of standards developed how individual states can issue vaccination certificates. So another option is to simply import the vaccination certificate into my wallet. Now we are at a situation today that we do not have as yet fully working technologies that would allow us to support zero knowledge proof. And as if you remember, I said, it's extremely important that the airlines themselves do not have to store the data. So how we address that specific problem, there are services like IAATO thematic that typically consolidate the travel rules and what this application does is it takes those data elements from the test certificate that are required to check against the rules anonymized and runs the check against thematic. If I was going on this date using this itinerary to this destination, would this information be enough? The response comes back into the wallet and in itself is created as a verifiable credential. I am okay to travel. And then once I travel, my wallet because it is travel ready is capable of sharing specific sets of data with those parties that actually need them. There is no storage outside. It is everything is on my wallet. Perhaps I might be sharing my okay to travel with the airline because remember I said the airline doesn't necessarily need to know the certificate itself. It might be that the border control does need to see the original certificate. I might be able to share it with them. And I mean, we started with actually the passport and also the possibility to take a selfie and match it. Perhaps I can also use it to notify the airport in advance. I will be coming so that when I am there, the gate knows this phase is coming for this flight therefore we can open all based on passenger actually permissioning what information can be shared with whom. So that would be an example of a very specific solution that has been built to a global concept. Now that concept itself is part of not just one ecosystem but if we kind of elevate ourselves, whenever we travel we have number of interactions with number of different parties. We might get tickets. They are in fact credentials that are provided by the transport providers. We might get passports. They might be credentials coming from the States. We might get the certificates. They are in fact credentials coming from the health facilities. We will all hold them in our wallet and then we might be able to show them to verifiers who need to know do we have this type of, can we provide this type of information to be allowed in. That is the business layer. But for this to be able to work, there is a fundamental technology layer set of services that need to be provided to individual services providers. And in those services today because those original credentials they might be digitally signed. They might be verifiable in fact but usually they would not allow selective disclosure. They would not allow zero knowledge proof. The first step that is needed is to take those original credentials interest them into wallet and preferably convert them into a format that actually allows later checking against the rules. Zero knowledge proof provides traceability back to as much as possible to the origin. So there is a need for services to make that conversion. I sometimes call them sort of notary services. Then obviously there is an open playing field for those who actually provide specific wallets. They might be commercial providers. And as we saw in Europe the states themselves might be providing wallets especially for identity itself. And then the third type of technology services is how to actually help the verifiers to ask the right questions and ask them innovate at the verifier only has received the right information but not necessarily the data that they may not need to process. And then for scalability obviously every verifier publishes their own rules. This is where you can travel and these are the rules. Often they are just typed or written in slots not necessarily machine readable. There is an opportunity for multiple services to consolidate this information, provide the rules, distribute them, make it scalable. And the last but not least of those technology services and I think this is really the one that's important to our discussion. If I travel with my wallet and the wallet is saying, oh, would you like to share this information with this airport or maybe I'm a verifier and I need to someone is presenting me with a test certificate and I need to know, oh, do I trust this lab actually that issued the certificate? There is a need for having a trusted set of services where we can authenticate the documents issued by the issuers and we can actually authenticate who is asking me the question who wants to have this information and that is trusted service on two levels. One is obviously who are the business parties allowed to ask the questions and the second one because we talk about cryptography where do I find the public keys of those issuers or verifiers so that I could actually authenticate that the questions come really from them. And the very last layer is the governance itself. As I said in the heading, I would never ever see this as a single ecosystem with a single and certainly not hierarchical governance. There might be individual use cases and probably will be where they have a very structured governance and structured hierarchy. But as a traveler, what I do is I travel from one ecosystem to another. I might take a bus, I might take a train, I might take a flight. I need to be able to travel seamlessly through everything and therefore what we effectively work on as a problem is how to have a trusted set of frameworks or ecosystems that all work together. And there might be different types of standards. There might be some sort of business level governance who can do what in which ecosystem. For example, the work of International Civil Aviation Association about deciding how to authenticate individual passports that would fit in there. But it is also important to rely on general technology standards. And in our case, we have selected decentralized identifiers verifiable credentials because individual travelers will definitely travel through different ecosystems. And as I said earlier, even before the COVID, we worked on a concept which was called one IDEAM. How to actually make sure that passengers can go smoothly through multiple destinations, ideally without ever having to pull the passport itself. So from airline's perspective, this ecosystem needs to be a seamless part of one IDEAM itself. The one thing that I would like to highlight is that as we were working on this, there were a number of questions that came up. And I would perhaps like to put it to you as a technology community, some of the lessons learned or questions that we would like to see answered. We do have standards emerging how to issue digital version of, I've tested, I was vaccinated, perhaps even the RECA very certificate. But as you know, those standards currently, they are signed as an entire payload. Therefore, they do not allow selective disclosure. And one of the questions that I think we have to look at technically is, how could we make sure that we can trust on the original signature rather than introducing some sort of interim signatures? But at the same time, support selective disclosure because the data is really personal and only part of the information should be disclosed. The second question, and that relates perhaps to the first, some of the original setups of the certificates, they do rely on a hierarchical public key infrastructure. And the question is, would we have some possibilities using the hyper-leggerous alternative technologies to safely decouple the information about where is my public key from the information which entity is authorized to issue what? Because surely my own pair of public private key, I would prefer to generate myself, publish it myself, and I can use it for multiple purposes, perhaps even multiple types of authorizations. And the third one that I wanted to highlight is we are well aware as an industry that decentralized identifiers, verifiable credentials, distributed ledger, they do offer a great potential, but the technologies are new and there are a number of protocols that have been already deployed for authentication and some of them already also allow the holder of the identity to be sort of autonomous. So one of the question is, how can we make sure that we can leverage the technologies that do exist today to speed up the deployment? Now, this was all about health credentials. I'm just getting to my very last slide because one of the question that is often being asked is, but all these health credentials for travel, they might go away. In September, October, next year, if the whole planet is vaccinated, we don't need them anymore. And frankly, if we don't need them, that is a success and no more work is needed, isn't. And with that, I would like to return you back to the original slide I was showing. For the airlines, it is not about just health credentials. It is about discovering the potential of the volets that the passengers can use to interact with the airlines throughout the journey. They can control the data. They can have the entire contactless travel experience. And if something happens during the journey, they can be in touch with the airline. This is why we are doing it. This is why we investing into research. The fact that health credentials came up was just an opportunity to speed up and use the concept. So with that, I would like to stop because I have been talking perhaps even longer than I should have. And I would like to hand over to Dramont because Dramont surely has many questions for me and I have at least one for him. Well, to begin with, thank you very much, Maureen. That was a wonderful explanation of the whole trajectory of the development of Viada Travel Pass. And you already actually answered one of my first questions which was gonna be, is it just about dealing with COVID? You've made it very clear that it is, it is only a step in the direction of verifiable credentials for travel and everything they can do. So maybe to give you a little bit of a break, if you have a question for me, you actually post several of them there in your last couple of slides, go ahead and shoot that first and I'll give you a little bit of a break and try and give you an answer. Thank you, Dramont. And I am really itching to ask that because I have on a couple of slides kind of scattered through the use of the hyperlatchers. And the reason I have been a little bit brief is at the end of the day, I am a business user and I wanted to make sure I really leave the opportunity, Dramont, you have been working with Ayata on setting up the Ayata travel pass. And I think it would be a really great opportunity if you could explain to the audience what components, what parts of the hyperlatcher were used where and how. Absolutely, and it's a pretty straightforward answer at a high level. And then we can spend the whole rest of our time diving deep, we won't do that. But you've consistently mentioned the two open standards that all of this is based on from the W3C and one of them is the Verifiable Credential Standard which is gonna be two years old in two months. So it's quite mature out there. The newer one is decentralized identifiers. I'm a co-editor of that spec and it is just about to go into the final stage and should be finalized in September. And both of those take special advantage of blockchain and distributed ledger technology. And there are two specific projects at Hyperledger that you're building on with travel pass and your overall system. At the base layer, you're using the Hyperledger Indie distributed ledger technology. And that is to register the decentralized identifiers that are used by the issuers of those credentials. And you actually use it, and I think of it in two stages. They're the health credentials or certificates that you're ingesting, whether it's from the EU, digital COVID certificate program or from the different labs that are issuing tasks. Those are all issuers Verifiable Credentials and each of those issuers has a DID on Hyperledger Indie based ledger. The default ledger you're using out of the gate is the sovereign ledger. The governance is provided by the sovereign foundation which turns five in September. So it's actually one of the most mature technologies out there. And then at the next layer up where we're talking about the actual exchange of the Verifiable Credentials, that's using the Hyperledger Aries project for the digital wallets and the exchange protocol for the credentials themselves for issuing and holding and then verifying those credentials. And you are actually using today, the format of those credentials is does in fact use a zero knowledge proof cryptography for the storage of the individual attributes in the credentials and it's currently called the Kminish-Lysenskija ZKP and we're moving here and we'll talk about that a minute to BBS Plus as the new ZKP algorithm. But Hyperledger Aries has focused on the incorporation of zero knowledge proof cryptography for all the reasons that you mentioned. So those are the two primary projects involved and the two areas of the stack. You're actually with, I had a travel pass and the overall ecosystem you're creating, moving up to what a trust of our P we call layer four which is interoperable digital trust ecosystems. And there you're gonna be using governance and the ability to reference the different governance frameworks and trust models involved with the credentials and DIDs. So you're really using the whole stack and in a very powerful way. Thank you, Drummond, that you couldn't have said it better. I really appreciate the explanation even myself. I was wondering if either of you should perhaps between the two of us focus on the kind of tricky question we have individual states issuing certificates for test vaccine and they are assigned in the entirety. Basically, I produce a payload. I get my X5 phone ID certificate as a government. I sign it, produce it as a data set goes on a QR code. This is what the passenger might be able to scan into their designs. But at the same time, many countries for really good reason the legislation does not allow technology providers even transport services providers to process and read this information. So how can we work or where are we on the way to work on the standards that we actually do have zero knowledge proof? That would be perhaps the question one from me. And the second one is, how can we retrofit it back so that we trust the source of the original entire certificate? That is spectacular. And I had sort of framed that as a question to discuss with you in the fireside chat portion because I think it's one of the most important things we can do that is this meeting of the technology capability with policy requirements, right? And one thing that you've emphasized that I hope the audience really understands which is the need of the airlines and I had as an industry to say we want selective disclosure and to make it clear for anyone that's not clear in the audience what we're saying is when I take a credential out of my wallet today and I hold it up to get on a plane or to get through a border, 100% of the information on that credential is exposed and in many cases that's not required, right? They only need to know certain data and one of the challenges when we share that credential digitally they actually have a copy of that data. So it's even more dangerous if you're always sharing all the information. So selective disclosure is the ability to cryptographically select only the data the verifier needs and it actually protects both the privacy of the individual but it also protects the liability of the verifier because they don't want data that, you know they have a liability if they're collecting data or seeing data that they're not supposed to and Meri, you referred to that. I would perhaps add one more thing to it that often it is not just the selective disclosure of the data, but it's really all the verifier needs is answered to their question. Because for example, why would I as a transport service provide the need to know whether a huge amount were vaccinated, tested or whether you had COVID? That for me is irrelevant information. All I need to know is whether the documents that you hold meet the rules of the state that set them and therefore you are ready to go. And I have two options. What Ayata Travel Pass does is runs the documents in an anonymized way against the rules and then gives the answer because we are not yet at zero knowledge proof. And the other option is, and that is happening today I can also rely on governments that take the responsibility to themselves. Therefore I facilitate the disclosure of the original certificates to the governments. And then the government gives me a signal, ideally again, verifiable credential and all that signal says Drummond can come to us, he's welcome. And then you can board the plane. Which is ideal because the airlines only get what they need. And the information has only been exposed in that case to the government that presumably is a safe place to share that information so they can provide that. What you're doing with Ayata Travel Pass and your thematic rules engine today is basically saying show that information, shows what is necessary against the rules for your itinerary such that we can determine this is what you need. These are like the health credentials you need. And if you have them, then you issue the travel pass as a credential back into the wallet and Ayata assigns it. And the airlines will trust Ayata's signature. Do I have that right? Yeah, that is the case. But that Ayata signature fills in the void of the change of trust. And I think that we have to really close that change of trust because that's much more important than putting new parties in it, be it Ayata or any other service provider that suddenly tries to play a part of the business where the trust should simply be end to end and this should be a technology service. I know that we are at the end. So I am absolutely closing. I just, all I wanted to say, Brian, is the very last note. The most important work is the work on the standards between everyone involved on the business side, on the technology side. That's where lots of the work of the Linux Foundation comes in. Yeah, there's a ton of work going on. This is a conversation I want to just keep having play out because there's so many important issues embedded in us that it's really important for so many people to know. But thank you, Marie. Thank you, Drummond. This has been a great illustration of how deep these issues go and the role that these technologies that we're working on here can go to address this. So now let's pivot to a very short break.