 Okay, so maybe I'll get at least a warming up. So I'm Wenjing Chu, senior director for technology strategy at FutureWay, but today I'm mostly going to talk to everyone about OpenWallet Foundation, and maybe the first part will be what it is. It's a very new project, it's officially started in February, and then three days ago now, we have the first code contribution or project proposal in our GitHub now. So really early days, and so what I will probably provide is some background information, and some of the ideas or visions that we think of what a wallet means, and how we can think about what are the applications and what role it can play. So that will be a little bit of a sort of imagination, it's not quite reality yet. But hopefully we can at least share and start to think about what are the right ways for this community to be properly formed, and how we run them, et cetera. So we very much like to hear your feedback and questions and any suggestions. Okay, so with that, I had a similar kind of presentation yesterday. A lot of information will look very, very the same. I would probably add a little bit of a slight differences if you happen to be in that session as well. I know at least one person is there, but anyway, so that's my talk here. So again, very beginning, we had the earliest idea about this. It's really coming from many, many of the existing communities, open source, as well as in standards, in a lot of government and other organizations that have been working on identity, for example, and then the financial and banking sector. And all the blockchains and cryptos, et cetera, all have some, you know, a lot of work done in the last, I don't know, at least a decade of time. So there are the really building, a lot of the building blocks of this. And the idea of an open source wallet started in OSSEU in Dublin. And Daniel Gochair, unfortunately, he couldn't be here, really, is the leading person to sort of gather us around under this one banner, right, open wallet and the open source wallet as the focus point. And so that's the beginning of this project. And in this morning's keynote, you will see OpenWallet also highlighted in the AWF Digital Trust Initiative. So here is a diagram of most of the communities involved. I personally worked with OpenWallet, but also trust of IP, know quite well some of the work in hot pleasure, and then confidential computing, and C2PA, which I also am a fan of. I'll probably mention some of their work in the talk as well. Okay, so what is a OpenWallet? And this is my understanding. I present this first time in the sort of open source in finance forum last December of understanding really two things. One is a wallet that we are familiar with. We have a lot of visualization of it. But how about, you know, general purpose, right? Put the things together that I, as a user, I can conveniently use it. So this usability and a personal touch to those are things very important. So that would be one aspect of it. The other one, I think, is proprietary versus open source and open standard. That's a common scene. And even if, you know, a lot of our government organizations or many different communities devote a lot of energy into many building blocks and components of our wallet, until they are really composed together in a convenient package, I think it's going to be a very, it's going to be a challenge for the long run. So we hope that OpenWallet community can be that long-term home to have a sustainability of the projects involved here. I'm trying to look for, like, the initial, like, where the wallet come from. Unfortunately, the examples that people come up with is, you know, these, from maybe Greek words and et cetera, and we have a sack and carrying valuable things with us. And I would like to say, like, in, you know, other than the wallet, we should also consider a purse that may be actually a better name because then you have, you're not constantly thinking about, like, a car or money, but really a sack that you can carry stuff. And so here are some of the examples that we can carry things, digital objects we can carry, carry in the sense of, like, you feel like this is under your control, right? And at the end of the day, it's really about control and how you can make use of them. And so, you know, this chart simply shows some of the type we've been talking about or the community have been talking about, and also different form factors that may show up eventually. So that's also, like, a very important keep in mind. The software program that, you know, the OpenWallet Foundation would like to help curate or integrate and produce, we're trying to explain that with an analogy of a browser. And probably, you know, the middle section is what the OpenWallet Foundation is trying to at least focus on. And so those are the software components that will implement a lot of standards. There are a lot of technical stuff, whether, you know, it's from, you know, from very powerful credentials, driver license, right? Isram tokens, credit card, et cetera. Or basically, all those words and protocols represent a type of system behind it. And they somehow, you know, influence our life, and they need to be visualized and make it easy for us. And so that's our tool to us. That's the role of the wallet. And then the software SDKs in the middle are simply a enabler, right? So imagine some app developer may want to have a presentation of some kind of a digital object. Today, to make that very secure and reliable and, you know, preserving privacy is a challenge. It's very difficult to do. So the software, hopefully, can allow them to have a much easier task for focusing on the application and build, you know, really trustworthy applications. And that can be literally like a digital wallet as an app, or some people call it a super app because it has lots of things in it. Or it can simply be my, you know, sort of messaging app, my games, whatever people are doing every day could embed a part of wallet functionality in it, too. So I want to just make sure that we are not constantly thinking about all these things somehow or unified in some way. But basically, this will be a new framework to sort of unlock, right? I use the key as a metaphor for my title of the talk, but also thinking of that way as a way to unlock a new type of applications. There is a set of rules that governments also want to sort of provide. We think that's also crucial. So two easy aspects of that regulation, one is in the valid or authoritative identity. So naturally, that is a very governmental function. The other one would be, for example, for regulation of a financial services. So all of those will represent some kind of rule. We would like to see those rules transparent and standardized so that we can make that easy for adoption, again, in the app as well as in consumer adoption space. So I think those captures very well of the goals the Foundation want to do. And this simply summarizes the mission statement. We're all working on this. This is our first version. And there's a lot of ifs. Sorry. Someone's listening. User choice, security, and privacy. So I think those three things are quite important in what the software foundation of the wallet need to be. You are all very familiar with this. So I'll probably skip most of it. But I do want to mention there's the one thing that's quite unique. We are trying to start a new government advisory council. So this council is we mirror the similar function in IETF. If you remember internet and also internet governance, the phrase we use was a multi-stakeholder organization. We don't have, we're distributed, decentralized. There's no one authority. But how do we get all the different stakeholders, not just technical people, but also regulation as well as communities and organization who are pushing, for example, the UN's development goals, for example. A lot of those do not have a easy, identifiable representation in our technical communities. So we want to have a space for that as well to ensure that the work we do have a long-term sustainability. Here are our current sponsorships and also the community. So we're really happy to see a lot of our associate sponsors. They are really not just an icon, but they represent many, many organizations who have been working on these questions from many different perspectives. So with them aboard, we hope that we can unify these contributions as well as knowledge we've accumulated in different areas. But eventually, how do we make them represent in code and running code, good quality, so that they can see deployment and use in actual products we build? So this is a growing list. Now let me turn on to see, say, about the role of wallet. So this is why we are saying it holds the key. Again, I find the easiest way would be go back to the web browser analogy. So in the web ecosystem, we've defined a whole bunch of ways to represent these digital objects, or we may call URLs. But objects today, all the valuable things sit in the server side. So the server has a whole set of things available to that. The client or the browser size are not very secure. Which means that when we, as individuals, operate things in the user interface, we are constantly involved in logins, authentications, authorizations. And then all that system have a lot of issues on security. But also the entire infrastructure is just not built with resilience in it. So a lot of work today represent the patchwork of trying to solve those problems. And so the key, again, to unlock this new opportunity, is really how do we fix that problem on the client? And so if we could have a representation of what that module is, I would say that module probably the best represented by a wallet. Because the wallet, to us, it holds things securely, and it's under our control. So that helps two things, it holds valuable things for us, but also it allows a convenient way to exercise control. And that is really the key for, if you want privacy, that's the key. How do you say no? How do you say, well, you don't need to know that. That way of expression, or basically be part of a protocol and negotiation able to say that, it's extremely important. And we need a way to a tool to do that. And that tool, I think, is the wallet. Consent, we get all type of consent all the time. But really the only way I can see the consent mostly is just say yes. It's really not a choice. Secondly, sometimes they give me a choice, but the choice I have to click and dig into it and go a lot of things. It cannot be automated for us. The other side, server is fully automated. But on client side, we can't. And so that is another way, it's very hard to really go into the consent page and choose exactly what I want. And that's very hard to do. So I would like to see a day that I can set the rules or the consent level I want. And my wallet will automate everything else for me. And so I would never need to see it pop up and stop what I'm doing conveniently. We were talking about open SSF and the initiative trying to get open source code, have a good provenance data. So we know where the code checking happened, who developed it, who tested it. And that sounds easy. We should be able to automate. But one of the key things is identify people who signed it. Basically, this is extremely challenging work to do. It's distributing billions of keys to all of us in a secure, reliable way. That's very, very hard to do. And I think I want to basically post that as one angle to look at why that wallet is very important. And once we do that, we should reuse that functionality over and over in a very convenient way. Because that's very costly to achieve. Once we do that, we shouldn't give it away. And again, it requires us to have something we can hold on to. And that's the wallet. So I hope I touched on most of the things. I'll probably see one more thing. It is also a personal interface, because that will be the app we actually touch, literally touch and do. If I want to disclose things, I want to do payment, all that need to be an interface. And that interface need to be intuitive and convenient and designed for us, not a representation of how the technical protocol works. So how do we conveniently do the right thing by default? I think that's also a major challenge. And I hope the wallet community can help solve that problem too. So in abstract terms, we will say that's a value aligned, privacy centric, and authentic with high level of trust. So hopefully those are the very abstract level we can achieve. So last time, I have no time to talk into this at all. So this is an architectural reference framework by European Union. One of the government that's really trying to do digital ID services to all citizens in sort of like a universal way is the European Commission and the European Union. And so this is a diagram showing their architecture. And in this diagram, the pink ones are regulators. So think of their government agencies regulating how things should be issued, et cetera. What are the rules you have to comply? The first column, the yellow boxes here with the impossible acronym, EAA. That is A, I think, is attestation. Okay, so they're basically like, if somebody give you a driver's license or somebody give you a diploma, where the parties that issue these authorized information. These information are extremely powerful because with those information, all of a sudden that you can basically start to have control of how to use them and exercise and use them for services, right? So the purple block then is the wallet. And so if you look at the rest of the right side, you have a user relying party that's like your merchant, for example, if you're buying things, right? And the wallet provider would be the developer, the product or the app you download, for example. And so all that involve around one thing. If you see all the arrows go, that's the wallet. And so hopefully this is like, even though it's all techno jungle here, but it shows that the wallet is really in the center of a lot of things. So hopefully that picture is actually meaningful. And as an example, I want to acknowledge John Jordan, the keynote this morning. And this is exactly the type of work that I was referring to. That's very successful in British Columbia. And I hope the same thing can happen in EU and many countries. And so that provides one type of really things that we will see in the wallet. And this is an enabling tool because, you know, imagine like I go to a random web page, maybe want to find a t-shirt I want to buy. Today has a lot of issues. We have to go open an account. You have to type in a bunch of your private information plus payment information, right? And so to the merchant, that is a burden for them. To us, it's all our private information out there. Each one is a hacking target. They will eventually will all lose it. It's just a matter of time they will lose it one day, right? So we are leaking tons and tons of information. And there's no reason that they need to hold that information in the back end. So we could have a really a good wallet which will allow these identities to be accepted universally. And that way, we don't ever need to create another account again. So the account will be even if they exist, there will be a relationship between you and the merchant rather than something that happened to be the place that they hold private information. So that database hopefully will go away. Yeah, so with that note, I want to basically lead to basically look at what are new applications we can do with that kind of system in place. Remember, again, now we look at the new architecture. We have all these servers or platforms out there. But we also have our own identity, not an account in somebody's system, but in my own phone. And I'm owning the information that is accepted and believed, right? And so that enable users to imagine all different behaviors and activities that we can do. It also helps the app developers to really imagine new services. So if we want to build an instant messaging or social media or web e-commerce, all of that, we can imagine new ways of doing this things. And they may even be very new business models. So all of these are, I think, within the reach. So I want to just hope I have better pictures of everything. But I hope we've talked about government services. And we were just chatting before this about medical. So Medicare in BC is a public. So every resident can get a car. But apparently, there are more cars than residents. So that is a problem. And that's because these authentication and processes are not very foolproof. And the same thing happened to all the systems we built. So trustworthy digital services allow all of these to run much more efficiently. And then we can see the rules of protecting privacy. A lot of that really into how we can control our private data through the wallet. The second, of course, is the financial services. I'll probably skip this now. We've talked quite a lot about this. But imagine all the different services that's happening. We are seeing more and more that's offered as a digital service nowadays. Yeah. So the third type will be tickets and travel. So these are the things that used to be a piece of paper. It's a holding of some service or holding of some asset. So that representation and all of that can be fully automated and allows the buying and using of that without going through a central system. Authentic content is really interesting. So I want to mention the work that's done in another Linux Foundation project, C2PA. That's a coalition for content provenance and authenticity. So basically, this allows a uniform or standardized the way of specifying metadata. So I know some of the camera manufacturers are starting to put that into their cameras. If you take a picture, the picture comes with a signature on which camera and what time these are taken. And then all the picture processing software allow you to basically authorize or you are the author of the photographer taking the picture, what happened to it, et cetera. So that provenance allow the content to be authentic. So we can help prevent fake media, fake news, that sort of thing, but also allow creators to assert authorship to it. Similarly for software, if we open source software one to keep the provenance, a similar kind of principle will work. And the important thing of making these kind of systems universally convenient to use is that you have a wallet that you can sign things. Without you even need to actually do this stuff, you will be very conveniently doing this. That's the key. OK, digital assets, I want to keep that as well. Health care services, we talked about that. One of the really important problem in the health care service is that what kind of information we need to keep around so that basically your medical record and information, who can access it and who can you share it to. And so with yourself in control, you can allow you to actually making those decisions and services much more easy. It also allows some of the hardest to problem easier to solve for remote medicine. So all of those I think is very crucial. And then literally keys. So keys are our oldest thing that we used to physically carry around. And if we want to make those things digital, we need to be very careful that these things are not proprietary, because anything proprietary I think eventually will become a choke point, will come back and become an issue. I think so that it's very important to see these keys are standardized and we have a portability. So if we want to, for example, use a different service or use a new key or to a new app or that you want to be able to carry your key around and go to a different place. So that's also very important. And control privacy. There are a lot of talking about AI today. Now AI involves many, many different issues related to privacy, also related to fake media. And authentication based on content, for example, is almost impossible now, especially with all the automation that's happening. So if you look at the back end system, how we do authentication. Most of them today, we do intuitive authentication based on, for example, if you receive a phone call, you're still identified person by the voice. And that's going to be very, very tricky very soon. Secondly, we use facial content like that. That's also very difficult. And so when we disclose information, the question is not like we don't know what information we like or not like to disclose. The problem is that decision is made extremely difficult. And we are really not meant to do that, right? Or whatever the scheme they provide today is extremely difficult to use. So in practice, we have no control of what happened. So that need to change. And the best way to change that is flip the size so that potentially in the future, in the wallet, you can specify precisely how I want this to be working. And let the wallet to be your agent working for you. It's like you have a private lawyer basically and tell them what information you're willing to share and negotiate that way, automate it in some fashion. So that's the way I think eventually, in order for us to really convenient to have a meaningful control of this, we will need to automate in that sense. That requires a trusted computing unit within our own control. Like for example, some kind of a token or a smartphone. We've talked a huge amount yesterday on Metaverse and the way that if we imagine all the privacy issues we have today, and Metaverse will make it dramatically hotter. And so I think it will be mandatory to have a strong sense of a private control entity that we directly involve and control with. And that's the wallet or you can say wallet kind of a function that's embedded in your headset or whatever you're working with that allow us to, without even typing and be able to basically through our easy day-to-day motions and expression to express those ideas. So we need to be able to smile and nod and be able to do consent or refusal and negotiation, et cetera. And so those are the things I think it's fundamental if there's any chance that the type of really immersive behavior environment are widely used as a Metaverse will be. And finally, we will talk about a whole bunch of things related to AI and trust. How do the type of, so we can think of it, trust is very, very complicated. It's probably a totally separate, we will have to go through talking about human trust. But human trust is so complex because it's unbounded problem where people will say, oh, there's a contest. But when they talk about a contest, they tie into a particular system design. Unfortunately, we don't design systems. Consumers and users don't design the systems. So the type of trust that is expressed to us are essentially trust that the system designer chose. And to change that dynamic, I think is required to see widespread AI adoption. And that requires us to really start to think about all the type of talk of trust is in the nuance, right? If you go to a job interview or a loan application or all the important things humans do, it's never clearly specified. Because it specifies exactly what happens there. It's what I call a unbounded complexity. Because all the nuances is extremely important. And each time, the nuances may be different. And so how do we use AI, which can actually become quite influential to the way we interact or access information, et cetera, the systems able to produce natural sounding language which will give you a lot of hint embedded in the language itself? So how do we be able to really, in that case, action and interact properly? Are we going to need help? And I think the root of that help need to be built into the wallet. Hopefully, that will become some kind of a core kernel of our agents or applications that then will have a whole new class of applications with this ability built into it. Hopefully, these are some examples you find useful. I have very little time, but basically, this is a summary of more like abstract terms we use to think about new opportunities for consumers. That's all of us. Creators, like people are creating new media and data objects and the 3D models. Music developers who are imagining and designing new applications, and then businesses who run and whether it's, you know, any of these examples we talk about, maybe move to a new paradigm, thinking about the ways that we can make this whole system better. And I would invite you to think about, if you go that direction, what are the core components we're going to need? And I believe that you will see that a lot of that will be represented in this kind of what I've been calling the wallet, right? So that's the important part. OK, so how do we get involved? Here are some of the links for the Bonway Foundation. There's a really nice report that just came out of LF research talking about why the world needs another open source project and open source wallet. And right now we need it really right away. There's a Discord and GitHub. I'll give you some of the, so here's another slide for the report. Please take a look on that. Some of the more of the engineering and technical discussions are happening today. So this is a Discord channel on Architecture Sick. And if you look at this, there's Consensus, Verified Credentials, Architecture, European Identity, the W3C standard for Verified Credentials, Heart Pleasure Errors, DECOM, Trust Spanning Protocol that I've been personally involved with quite a bit. OIX is the UK based consortium that's also working on these. Ramo, it's an open source project for that. Again, UDI notary, that's a key thing. What is a notary? That's how we used to make information trust worthy, right? How do you prove to somebody? Well, you go to a notary. So that's cool. Yeah, Farmworker use case is a cool one. I don't have one here, but we had also refugees. How do they create some credentials right on the site and be able to actually do something for them? So those are all very extremely important. And there's a lot of them. This is happening every week. So that will be a great place to get involved and get started. And I just mentioned some of the ways we're starting code contribution or project proposal as we start to in the GitHub make a proposal. So these are the two that just showed up three days ago, I would say. And hoping that a lot more are coming. We have a big pipeline in the works right now. We will hopefully see a lot of the contribution coming in. Yeah, that's I think I run out of time. But I don't know how much extra time we have, but I open for questions. Anyone have questions? If not, I think the key takeaway would be check out our community. Again, it's very, very new. So if you keep around, we will probably have more news coming around. It's a global community. So you see a lot of European and North American working on bringing a lot of Asia players in as well. We will hope to see this becomes a foundational piece that enables a lot of open source projects and a new application to be able to use the phrase conveniently do the right thing. We know what the right thing is. It's just very, very difficult right now. But we need to change that. Thank you so much.