 Tim and Shaw, we're good to go. Awesome. Thanks, Sean. Appreciate it. So welcome to April 4th meeting of the Identity Special Interest Group here at Hyperledger. Today, we have an awesome presentation from Jorge and Jesus for you on the Aries Digital Trust ecosystem. But before that, we have a few announcements and a few working group updates that we'll go over. So for the announcements on the agenda, is the SIG call next week is canceled or next, not next week, but in two weeks is canceled for IAW. That'll be the 18th, I believe, would be our call. And then we have IAW coming up. So are there any other announcements to be aware of, Sean or Shaw? Yeah, so I'll just put in here for the IAW planning. On the ID SIG, we started a threaded discussion around IAW in April. It happens in less than two weeks, actually 11 days, 12 days in Mountain View, California. Internet Identity Workshop is very much a gathering of the clans of the identity community. A lot of folks who work in OAuth and OpenID and decentralized identity are going to be there across the spectrum. In the ID SIG channel in the Hyperledger Discord, feel free to post, even if you're not going, if you're going or not going, let us know if you're going, feel free to post the things that you would like to talk about or you would like to see or you'd like to learn. We're also going through a similar process in the Open Wallet Foundation, the OWF, which I'm going to start providing updates to the ID SIG in this document. The OWF has folks attending IAW this year, myself included, and we're having a similar conversation. What do you want to talk about? What are you bringing to IAW to talk about? What do you want to learn? And also, who's going? So by all means, on Discord, either the Hyperledger or the Open Wallet Foundation, please chime in, let us know. If you can't go, that's fine. You can still let us know what you would love to hear or talk about. And there will be a book of proceedings that comes out of IAW where the attendees take notes on the different sessions and they share them with everybody so nobody really misses out. The second thing here is we've got a workshop on April 24th, Zero Knowledge Approves and ZK Programming and Blockchain Application Development. This Zero Knowledge Proves play a large part in identity at Hyperledger. The two presenters of this work in the ZKP space, they're going to be using Beizu and Fabric for the root of their presentation and workshop, but everyone is welcome, as with all Hyperledger events. Please join us, the link to our registers right there. And thank you, Shar and Tim, for letting me do those announcements. Yeah, absolutely. All right, moving on to some working group updates. Hyperledger Indy contributors working group call happened on the 26th of March last month. Was anyone able to attend this session that would like to give us a quick summary? Yes, so we received updates on the Indy Beizu project. There's a draft PR open that adds Hyperledger Indy Beizu specific identifiers and entities to the original Indy did method. We also received updates on the Ubuntu 22.04 upgrade. The Indy plenum work on that is in progress and coming along. There is also a fourth Indy summit coming up next week, April 9th. The topic is ledger redaction. This was previously known as tombstone and it is marking transactions as non-resolvable. And I can send out that link to register if anyone's interested. Yeah, it was a good meeting. All right, very cool. Thank you, Shar. Appreciate it. Hyperledger Aries met just yesterday. Was anyone able to attend this session at the Aries working group? All right, looks like they were talking about VCX and some RFC updates. By Fold hasn't met in a while. So the Aries Cloud Azure Python group met just a couple of days ago. Was anyone able to attend this session? Yeah, we got a bunch of status updates on didpier and AFJ interop work. There's work progressing on connection reuse for didpier 2 and 4. On Akapai 012-0, adding a few more PRs that need to go into that release. On a non-creds RS, there are PRs for a non-creds. And credits concurrently that it looks like will be merged in after the 012-0 release is finalized. There's also discussion of logging for multi-tenant agents and defaults around multi-tenant agents. If the current non-multi-tenant agent should just be a multi-tenant agent with one tenant. Akif, I know you were there as well and talked about logging. I'm not sure if you want to give a more in-depth update. Yeah, I think you covered it all perfectly. We're talking about maybe Akapai moving to a default multi-tenanted, I guess, runtime. I don't know what you want to call that. And that there wouldn't be this sort of delineation between a single tenant and multi-tenant mode. So, yeah. Thanks for that. Yeah, thank you for jumping in. Awesome. No, thank you both for the update. That sounds really interesting. Looks like the Aries, CloudAsian, Python maintainers meeting happened last week. Was anyone able to attend this session that would have any updates for us? All right. Looks like they were talking about some out-of-bounds issues and backwards compatibility. Hyperledger and non-creds met last week as well. Was anyone able to attend this session? They were discussing a non-creds v1. And if anyone wants any more information on any of these sessions, the links are all right here. So please feel free to explore in your own. That happened a while back. I believe the trust over IP, all members meeting. Yeah, that happened for our last meeting. Older stuff. Looks like the TOP ecosystem boundary group met last week. Was anyone able to attend this session? All right. Looks like they're reviewing some papers and case studies. And the concepts and terminologies group met last week as well. Was anyone able to attend this session that would have a quick summary for us? All right. Looks like they were discussing the terminology governance guide. And again, you can learn more at these links if you're interested. The diff didcom spec working group met just recently on April 1st. Was anyone able to attend this session that would like to give us a quick summary? All right. Looks like they are prepping for IW and discussing all things post-quantum. Which sounds very interesting. The didcom users group has an upcoming meeting. And I believe that brings us to the end of the working group updates. Unless anyone else has anything they'd like to share. All right. Well, with that, we'll hand it off to you, Jesus and Jorge. Okay. Well, thank you, folks. Let me see if I can get my screen here. Can you all see the screen here? Yes. Okay. Great. So thank you, folks. Once again, Jesus Torres, co-founder and CEO of Entidad. And excited to be here to share a little bit about the work we've been doing over the last few years and provide a little bit of background and context here. For work that, frankly, folks would not have been possible without the hard work and dedication of this community. Together, we've been able to deliver 60 million in direct aid and growing to U.S. farm workers. So know that there's a growing number of them and nonprofit organizations around the country that are grateful for what you all have created here. And even though Entidad, we're so early in our journey with this community, we're off to a really good start because of you. And so briefly, who is Entidad? We're the social impact startup. And we help mission-driven organizations that work with underserved communities use technology to grow and deepen their impact. And we emerged out of a volunteer project with a group of nonprofit organizations where we were trying to understand how we could leverage growing digital literacy in their communities to address the plight of farm workers in this country. And after a few months of this volunteer work, folks, we were captivated. And we decided to establish fund, I mean, found Entidad to pursue this work full-time. Because we understood that, oops, farm workers are the backbone of our nation's food supply chains, folks. Put simply, no farm workers, no food. And yet they remain one of the most underserved segments of our population. Now, there's a lot of different reasons for these. But two areas where we thought Entidad could be impactful in helping address these challenges was one, access to basic civic infrastructure. So these organizations work in rural communities. And so whether it's farm workers not having a physical mailing address or access to transportation or identity documents, these challenges become an organization's challenges when they try to deliver their services and programs. Over the years, they've done their best to build their own infrastructure to be able to reach these communities. But access is inconsistent. It varies from office to office, county to county, state to state. And so this makes it really difficult and expensive for these organizations to operate and to scale their operations. Because they have to be able to answer problem number two here question, this question of who's on the other end of an interaction. And so most of the services and programs that these nonprofits provide come from funding sources that require them to collect and verify applicant information to determine eligibility, to prevent fraud, for reporting purposes. The thing is that traditionally these activities were completed using manual processes, which again are difficult to operate and expensive to scale. And so the thing is that what we notice is that at all of these events, everybody that would show up, all the farm workers that would show up, they all had smartphones in their pockets. And so and to that propose to the group of nonprofit organizations, hey, why don't we build a farm worker services ecosystem that uses verifiable credentials to make it safer, easier and more affordable to deliver these services. And they agreed. They love the idea. And so the preparation ecosystem was born here. And so there's four major components to the solution. There's a smartphone app, which farm workers use to access the ecosystem. There's a platform solution that organizations use to build and host the business services, which are the apps that farm workers connect to, to access the benefits that the organization provides. And the last component would be is a data analytics component that allows us to better understand the end user. And so in 2020, we began working with the UFW foundation on the progressive project here. And as we built out these business services, we were we were able to iterate through the components of the ecosystem. And just as these components were built out and kind of got integrated together, the USDA was announced the historic farm and food worker relief program. Now in 2022, farm workers were still feeling the effects of the pandemic and the USDA having already provided several rounds of funding to growers. They decided for the first time in their history to provide a disaster relief specifically for farm workers. And so the the program was funded through with 670 million through a congressional bill and the program selected 14 nonprofits and a tribal entity to partner with the USDA in implementing and operating the program. And so the UFW foundation, our customer received the second largest grant to distribute 97 million approximately. Part of that included leading eight other nonprofits through this program. They'd be responsible for processing over 125,000 applications from farm workers and distributing those funds nationally. And so with the pieces in place of the preparation ecosystem, we were able to use the preparation platform to build out the Aliveo business service, which as I mentioned earlier has been used to process over 16 million in direct aid to farm workers to date. And it's growing. We've been able to reach 49 out of the 50 states. We're still trying in Alaska, not too many farm workers there. And we've delivered to over 1800 zip codes as well. But more so than just helping us deliver this aid to farm workers. The, the Aliveo service has really been a vehicle for us to vehicle for us to drive adoption of the purpose of mobile component of the ecosystem. And so today, we've been able, we have 30,000 verified farm workers using the mobile application. When provided the option nine out of 10 farm workers have decided to download to follow along with their Aliveo case and just introducing the mobile app and the intake self guided intake for farm workers. You know, there's still a lot of more work that we can do downstream but just the intake portion providing that has already led to a 33 33% efficiency gain when compared to other forms of collecting this information. So again, still early, but really happy with where we're at with this project here. And I think with that, I'll hand it over to Jorge to dive into the details of what it is that we've built. So I'll stop sharing now and hold it. Thank you. Hello, everybody. I'm Jorge Flores, co-founder and CTO of Entidad and I'm excited to be here today to tell you a little bit more about the technology approach that we've undertaken in serving our mission and the mission of the organizations that we're working with. To begin, I wanted to kind of set some context for design considerations that have influenced the choices we've made in building the solutions, the apps that Jesus just described. If you're a nonprofit or a public service provider or any organization for that matter, and you're trying to bring your digital service to your communities. These are some of the questions that come to mind. If you're a farm worker or if we look at the farm worker perspective, which is something we do, you know, on a daily basis, how do you find a service? Who do you trust? Where do you go? Do you have a smartphone? We believe that most farm workers and most immigrants working here in the US probably have a smartphone. Is it an Android or an iPhone? Are there differences in the user experience between those? Do you rely on your phone SMS messaging or email address to exchange or to interact, exchange communications? We find email, for example, is a channel that is very hardly used. Practically nobody uses it, at least not in this community. Do you work or live in rural communities where connectivity is sparse? And so offline becomes a very serious need. Are you apprehensive about biometrics on your smartphone or on the apps that you're interacting with? What is that all about? And do you share devices? Do you live in a household where there's only one smartphone, perhaps a husband and wife or a daughter and grandfather sharing the same smartphone? We find that that's a quite common use case. And of course accessibility in the farm worker community, we find that there's a wide range of backgrounds. A lot of farm workers come from Mexico, Latin America and other parts of Central America. And there's a huge indigenous community, Zapoteco, Mixtecco, Purapecha. These are languages that are not very well written. And so if you're in this community, are you finding services that cater to your needs? And if you're a service provider, what are you thinking about? How can you extend your brand over digital medium? What does it take to positively identify somebody, an individual, who you're interacting with and trying to deliver a service to? What kind of communications tools do you use? Do you have a call center? Do you rely on email campaigns or SMS messaging campaigns? We know that there's a lot of challenges with that. And then of course, fraud prevention, which is on top of everybody's mind, especially these days with the onslaught of AI technologies that we're all hearing about today. Moving on. The question of email and SMS, relying on phone numbers and email, to all of us on this call and to practically anyone who has a smartphone, I think these communication channels are practically unusable today. But not only that, they're a constant attack vector. And these are just some examples that we've encountered ourselves that anybody can fall victim to. And then, of course, there's, you know, the constant threat of surveillance and data harvesting and privacy breaches. I mean, we hear about this stuff every day. So we're here to talk about how we've adopted hyperledger Aries and the great work that you all, this community has contributed. There's open source frameworks, there's protocols, decentralized protocols, there's specifications and open standards. And we found very early on in our journey that this community was something special. It had exactly the right tools that we needed to be able to address some of these problems. And so we have a minimum viable ecosystem that we're going to demo today that leverages the hyperledger Aries issue credential presentation, proof presentation, protocols and basic messaging for DITCOM chat. DITCOM I think is quite unique in that it offers a viable alternative for reliable persistent connections and communications between the organizations and the communities and gives the user control, right? If you no longer want to receive communications or if you want to disconnect, you simply delete your connection. So these are capabilities we've been working hard at embedding into our solutions. And we have the alluvial service, which is the first service that we've operationalized on the Preparation Mobile app. And if there are no questions at this time, I'd like to proceed with a demonstration. We also have a training instance of the app. I'll walk through two parts of the demonstration. One is the wallet registration or wallet onboarding. And the second would be the actual interaction, the transaction or service delivery of the alluvial service through this meeting. We explain to the user what this app is intended for, right? It's intended to make it easier for you to access services, connect with trusted organizations that have been onboarded onto this ecosystem and then store your personal information in your own wallet and you get to decide who you share it with. We know that password list is an interesting design challenge. Most farm workers and a lot of folks actually don't use password managers. And so we're trying to make this as simple as possible. Today, you have a choice of setting a six-digit PIN and maybe enabling biometric if you have that turned on in your phone or if you're comfortable with it. So this is it. We've completed the wallet onboarding. And now on the services launchpad, you'll see a series of services that have been onboarded. This is a training environment and so we've got a couple of experimental things going on here, but today we're focusing on the alluvial service. So start to go through that process. So we first explain what the program is about. If you have any questions, you can link out to additional information about it. Some things you need to know, right? There's no fee. You should not pay anybody or there's no reason for you to hand over any money to any service or in order to apply. Immigration status is not a factor in eligibility. And of course, you have to provide proof that you were a farmer for working during this period of the pandemic to be eligible. And that's it. Those are the basic requirements. Have you started an application with any other organizations listed here or any other organizations working through the program, participating in the program? I'll answer no. Have you received a relief payment already through another organization? No. Did you work in agriculture or livestock during the pandemic? Yes. And did you incur any expenses during the pandemic? Any medical expenses or others? Yes. Review my answers. I'll hit submit and I'm eligible. So we move on to the next step. Here's where we started a process of identity proofing. We try to make it really easy for the for the farmer to provide their information. So a lot for that option. And I have an identity document that I'm going to quickly scan. So very easily picked up the information from my identity document. I don't have to fill out any complex forms here. You know, we've been talking a lot. I've been talking a lot about phone numbers. This is a unique program that, you know, there's serious considerations for making sure that the right folks who are eligible are receiving the distribution. And today we request, we require a verification of a phone number. But that's really because it's one of the few types of binding to a person that we have. There are other options that we're exploring, including biometrics that we'll get to discuss after this demonstration. So receive a text message with a verification code or punch that in. We have eight organizations participating. But those organizations serve particular regions of the country. And so we've enabled a geolocation capability that depending on the device location, it will be presented with the organizations that are serving your particular region. So here, select UFW foundation. Brief description of the UFW foundation and their mission. And that's it. My application has been created. I haven't completed all the steps. I still need to be able to complete the review, the proof of identity. And this is just a matter of reviewing what was captured and submitting that, that that task was done. I provide mailing address and proof of employment. I could also engage in real-time chat if I have any questions. On the other end, if you're a service provider or staffer, you're going to want to address these applications and incorporate them into your review process. So here we see the application that I just submitted. All of the information that normally would have been captured over a phone call, over a form completion is now just easily readily available here for review. We can see the identity document that was captured. I can, if I'm a reviewer or an approver, I can take a closer look at these things to make sure that, you know, nothing suspect is happening here with the documentation that's been provided. I can request additional information, such as a case, if needed. And lastly, we have this concept of video chat that we can also share, engage in a more intimate conversation to address any additional needs that might exist. So this is, in a nutshell, the capability, as Hsu said, the efficiency that is gained from this is tremendous. But, you know, there are some challenges that we're still working through. The thing here is that, you know, the experience, if you, the experience you just witnessed, right? We've been largely influenced by the wallet designs that we've seen from other members of the areas community. Today, we're working on enabling the cradle framework, which is the wallet engine that is now embedded into this app. I'll jump to the technical architecture. I'd like to stop for a brief moment. Are there any questions with the demonstration? I was wondering how, so how have farm workers received information about the app? Is it through text messages or other mechanisms? Yes. Oh, sorry, go ahead. Go ahead. Yeah, I was just going to add as part of the program, you know, it's a national program. And so there's been a lot of marketing to the communities through traditional media, social media, so on and so forth. And also, you know, kind of their existing member usage, their existing membership and community. So the organizations themselves have taken on a lot of that work. Oh, nice. So the service we built, you know, this service has been operational since January of 2023. It's a two-year program. And so we've iterated, you know, quite a lot in the past year and a half. And most recently, we rolled out our cradle implementation. That's part of our farm worker wallet OS framework. So, you know, we're building on a low-code stack. We call it the farm worker wallet OS where all these capabilities that we just demonstrated, we're building on a low-code stack, which is, you know, something we're very proud of. The ability for us to wrap these, you know, complicated technologies, emerging technologies. And provides, you know, a good experience, a very decent experience for these organizations and for the end users. And cradle is a big part of that, of our roadmap. You know, we want the app to be interoperable with other Aries ecosystems if you're issuing an on creds or soon to be supported. W3C credentials or SDJOT, right? Like all of this stuff is going to be increasing the capabilities that we can offer and still provide, you know, seamless user experience. We've partnered with Paradigm, which is another Aries implementer to provide the mediation service. And that allows us to have connectivity or did come message exchange to a mobile device. The mobile device is not a server. And so we need a way for to basically relay messages to a device. And so the mediator agent that we're incorporating or integrating with is hosted by Paradigm. And then the Paradigm cloud agent is what we're going to plan to use in order to start to issue and verify credentials as part of the next path in our journey. Some challenges that we've run into, I think that are not worthy. And I wanted to maybe highlight for other implementers and for other organizations that are looking at, you know, doing something similar. Like why is hyperledger Aries and the protocols standards that it offers? Why is it a good choice? Well, traditionally, if you rely on, you know, message-based communications over SMS or browser-based communications that rely on, you know, X519 certificates to ensure that the pipe between your browser and the server is encrypted. There are challenges that we've encountered and, you know, these are challenges that anybody would have to address and you may not necessarily be thinking about these. But if you're buying certificates, you know, not all certificate issuers are alike. Some are really expensive. Some are more affordable. But the ones that are more affordable don't necessarily work well with mobile. Especially if your mobile device is older and not running, you know, the latest browser. We find that there's a small subset of users that still use older phones and, you know, those browsers get into life, they don't get supported. And so on those very phones, this app that I just demonstrated runs just fine and we kind of circumvented this issue. If you're using deliverability, SMS-based communications or email communications for that matter, SMS specifically, depending on the network that your phone is on. If you're on a low-cost phone or a low-cost carrier, we've encountered issues with the encoding of messages that affects delivery. So if you have special characters or hyperlinks in your message content, this could happen where either the message gets delivered in a way that it can't be interpreted by the end user. Or sometimes the SMS message gets flagged and spammed by the carrier simply because there's a misinterpretation of the message encoding. Again, this is another issue that doesn't happen with DITCOM. And then another problem statement is the problem of shared devices, which is really interesting, right? We have one holder, one wallet, and we think of a holder, at least in how it's defined. Typically it's defined as the owner of the smartphone. But in this world of credentials, verifiable credentials or wallet, the holder would be the user of the wallet. And then there's the subject of the credential. So we recognize the need to be able to support a wallet that can provide the same level of experience to different users sharing that device. And this is usually a household, but it could also be a friend. You know, farm workers are seasonal workers, many farm workers are seasonal, and they travel from far away places of origin, and sometimes they don't have smartphones. So they'll ask their co-worker, can I borrow your phone for 10 minutes so I can apply for the service? But then there's also a fraud vector that we've ran into recently, and this one was kind of caught us off guard. And that is that there's, you know, bad actors, what we consider them bad actors, because they're charging a nominal fee. They're charging farm workers to use their own phone to apply on the farm workers' behalf and charging a nominal fee for that. So we recognize the pattern that was suspect and want to bring that up because it does introduce or pose an interesting design challenge with respect to how we implement a wallet. And ensure privacy and confidentiality. And then lastly on a roadmap, interaction patterns are important. And, you know, I think today with the version of Crato and the paradigm agent that we have integrated with, we have full support for one and two here out of band and mobile apps. Mobile app to browser desktop application. But we do, we are very interested in being in support close proximity that's, you know, Bluetooth low energy or NFC, you know, contact list offline, especially I think this is going to be really important. And, you know, we have our eye on mobile driver's license and other very follow credential standards like open ID for VC that potentially will, you know, expand the use cases to app to app or app to browser within the same device. So I'm aware that the cradle framework and acupy framework, and some of the other frameworks that are available. If not in the hyper ledger areas community or the open wallet foundation, these are some of some of the things that are that are being looked at and so we're hopeful that, you know, over time will be able to have full support for all of these interaction pattern. Okay, I think we have a couple questions from Brett. Yeah, in the chat. And right. Oh, okay. Yeah, I was gonna have. Okay, so my first question is about the underlying structure of the digital credential. Are they functioning as a token solution. Is it, is it a token, a blockchain token. It's not the, so the credential support that we are incorporated into into the app are verifiable credentials. So, there, there, there are various credential formats that are that are being developed. The one that is really, you know, at the core of hyper ledger areas is non correct. So what we're hoping to do is to provide a capability input policy by modifying the onboarding experience to allow the customer to self attest their profile. Right. In the example of the alluvial service that I demonstrated. There is a there is profile information being captured either manually to a form which I, which I didn't show that's the alternate path, or scanning an identity document. And that's important. So what we plan on doing is two things, one, we give the option of the farm worker to basically self issue themselves, self attested credential in a non credits format. And, and then use that to kind of jumpstart the trust establishment dance, you know, where the organization provider so we don't have to start from scratch. If you, if you land on an app from the app store, for example, or you're directed through a QR code to a website. You should be able to, you know, start by, you know, presenting your name at the very least to start a conversation. But that self attested credential will only get you served so far, right. Right. If you're applying for a cash distribution service like like a leave you is, it's not going to work. You're going to need another, you know, more high assurance credential. And so that that's where mobile driver's license potentially will come in. Or potentially after a process like the one that we demonstrated where you do incur the cost of identity proofing an applicant. Right. We were uploading employment documents were uploading identity documents potentially additional information. We're also going to be incorporating light 3D lightness detection and face matching capability to ease the burden of the shared devices and ease the burden of remembering your past code. But that will also help in the binding to the credential. Right. And so together, I think that this this is where we think that the patterns for exchanging information confidentially and giving the user the control. That's ultimately what we're super excited about that it's not only making things easier for verify organizations, other organizations, the foundation is, you know, incentivizing this this program. But the idea is that this the investment they've made into this initiative is going to be leveraged by other organizations that that are smaller they don't have the staff, or they don't have the budgets. Right. But here's a low cost effective tool that that they can continue to build on. And so, and just as a suggestion for food of thought, you know, a three layer token. We're dealing with credentials here so like one of the layers would be like a notary public that could be stamped by the foundation or even the government. Just just as a just as food of thought food for thought. That's a, that's an excellent suggestion. Yeah, three three layered token. And then the next thing is do you have any metadata metadata management solutions in place or a metadata and what sense and just as well. Just just as far as like having like a macro component to it. And so, you know, as opposed to just having a micro component. I'm not sure that could be other foods of thought to, you know, as far as, you know, you know, dealing with the problem statements and possible solutions. So, like I said, like I said, if you're able to get the government or these, or these foundations, these NGOs to basically notarize a token, you know, a token, it would, you know, I think it would go a lot further. So, anyway, that's just an excellent presentation. Excellent presentation. Thank you so much. Thank you. I'll reach if you don't mind bro. I'll reach out to you to give more clarity on these two points. Okay, yeah, I'll drop my, I'll drop my email and chat. Are there any other questions? I was wondering. So you talked some about the shared devices and delegation. I was wondering, how is the wallet set up when devices shared between multiple people? Okay, so today we don't have we don't have implementation support for multiple people using the same wallet. Because it today, it's just bound to a single person, right? You, you, you set a six digit pin. But we do have plans on a roadmap, hopefully, before the end of the year, to incorporate the multi-tenancy aspect of the, of the hyperledger areas, the cradle framework. And now that, you know, we could, we could extend the onboarding and pair that with a biometric lightness detection capability that we're also in the process of the building. So that, you know, even if it's the same device, different people can be authenticated just by simply, you know, doing that. Right. It's kind of like a selfie experience. Right. And then your, your, your personal wallet would be loaded. It's all stored on the device. But, but with cradle, we believe we have the flexibility to be able to support that. Right. Right. Cool. Thank you. Just real fast. The token would go in the wallet. So that would be the functionality of the token. Yes. Okay. I guess we'll turn it back to who takes Tim. Yeah, absolutely. I appreciate the both of you for sharing. That was an awesome presentation. That brings us to the end of our working group call. So as previously mentioned, there will be no call in two weeks as usual for IW. We look forward to seeing you all in a month. Jorge and Jesus, I'm not sure if you'd like to share the slides, but if you'd like to, you can for sure send that to either Sharra or myself and we can post them on the, on the page for today. If people want to look over that. Yeah, well, we'll get those posted by the people who are watching the recording. So thank you so much. Yeah, absolutely. We'll compile the two sets of slides and we'll share that hopefully by the end of the day. Awesome. Thank you so much and thank you so much for a great presentation.