 Hey folks, we'll get started in one minute. Okay. I will paste the link in and begin to screen. Okay. Hello everybody, welcome to the Aries did come be to working group for April 10, 2023. So we're going to be on our last meeting before the I I W week. And so we'll probably be off next week. I still Lincoln. Again, in case let's see. God Alex, never don't go. Helping me on some things to call him in here. Okay, there's our link for today. I want to remind everybody of the antitrust the hyper ledger antitrust policy and the hyper ledger code of conduct. And feel free to add yourself to the attendees list. Is there anyone new today that would like to introduce themselves. Okay, are there any announcements from our areas working group meetings or anything else from frameworks out there. If anything, before we jump into the I I W stuff. Okay. All right, well then let's jump in. We've seen a ton of of activity. Regarding I W preparing for the I W did comfy to connectathon. Again, that's Wednesday, April 19 from 130 to 230 after lunch during I W. Yeah, it would be great to just go through and get updates roots ID folks. Any updates you want to give from this past week. I saw a ton of activities. I did last I did I including the in the hack and the include the like interoperability matrix. So we can so we can then start. Is it able. Yeah, that one. So try to start putting whatever test we we pass. Yeah, I'm not there. So that's what I wanted to do on there. The last days. And there's a reference so it's just being a basic message. Okay. Go to the bottom. Yeah. Okay. Great. Someone can improve that. That was my first attempt to have something. Yeah, this is great. Thank you for doing that. Message pickup. Okay, forward. Excellent. And so if I'm reading this correctly then. Obviously roots well to root solid Android. We can do trust being basic message. Same for iOS. Same for our prism. We just have basic message right now. Block trust web agent. We have basic message. And for Nessus agent, we have trust ping. Great. Okay. And then so. Right, we can go down the list. Yeah, basic message across. Okay, it looks like block trust and Nessus then have done. Trust ping and basic message. Fantastic. Well, maybe this is, yeah, I think I don't always be on update that. Yeah. Okay, good, good. But I think Nessus doesn't answer. So use center message to them and it shows up in the list. Yeah, great. Yeah, I guess you can. You can see on the list on the web page. Yeah, you see that they received your basic message. On the connections where you see that. Oh, when you open Nessus and then you can open the connections. Okay. Okay, go good. Great. It might be down there. Yeah. Hey, then can you reshare the link real quick for the activity? Yes. Thank you. Back in the incoming now. I think this was where those interaction. Okay, it looks like the Nessus playgrounds down right now. And we call it's, I think it's working. Oh, maybe the link that I went to. Yes. That's for using that for. Okay. Yeah. All right. And then did peer and then you go to connections on the right side. Yes. Okay. Government connections. Okay. I see some root ID mediator stuff. Is there a way that I can identify block trust? Do we know maybe it's. I don't know how often this three sets. Okay. But if you click one of those, you know, the connection link. Yeah. Maybe. Yeah. Yeah. You have a message there. So click, click on show. On the basic message. And you're going to see your Nessus. This is a root CD. Okay. Fantastic. Okay. I love it. I love the chart. Thank you so much for. Yeah. In that one, you also see that it's a proposed credential and a West credential. So. Thank you. Yeah. Should get the VR from Thomas, I think. Right. Okay. You bomb did it first. Yeah. I did that like in the Jupiter notebook. I don't know if that counts though. Yeah. Yeah. On the table as well. Great. Yeah. Yeah. Just off the top of my head since we want to touch base at the did calm, did calm user group meeting today who will be there for that. I think I can only listen to it. I'll be in the car. But I would love them to. Okay. Great. Cause I would love them to see this because this is, you know, goes well with the effort that we're just trying to do there of showing more services, interacting. Great. Okay. Yeah. Yeah. So, you know, I think we have some thoughts on this table of progress that we might make this week. Or, or, you know, what else based on this table, you know, do we need to tackle. Yeah, I'll fill in the Varamo stuff. Okay. Yeah. Any updates on Varamo mediator or. Yeah. Roots wallet for Ramo. Yeah. Yeah. So, I was able to send like, do a trust ping to it. And yes, like basic message. Those. Okay. Great. No. I'm trying to make sure that the whole mediation. The request in the pickup protocol, all that kind of stuff works. Excellent. Okay. And then Bjorn, do you want to give any block trust updates? I mean, certainly we can see a bunch from, from here, but you know, we'd love to hear your. Happiness and struggles, whatever they may be. Yeah. I think we had a few breakthroughs. Last week to get everything working. But there's really nothing new pick to. Announce or to talk about at the moment. Okay. Very good. Also be before the table. We go up. I started in last week, like issues found during preparations as to. Maybe least what we found and keep there as a guide for future implementations. To say this topics that we know they are. Yeah. The, the cases that need to be fixed. Like the, yeah. Service endpoint is on the top of the leaf. I think how you call the, the idea on the service endpoint. And other stuff that we need to. That's mostly things that I. Work with Bjorn. But yeah, I need to spend with the others as well. Yeah. The service endpoint is really the big thing because that's not really documented how to do this. And. Yeah. We just aligned on the, on the person way of doing this. Okay. All right. Very good. Any other. Just looking at our list of folks. Any, anybody else have. Comments, questions. About the table. Then we can start talking about. Well, what will give us the most bang for the most bang for the most bang for the most bang for the most bang for the most bang for the most bang for the most bang for the buck at IW. Okay. All right, so. From our point of view, I think, you know, this hack MD is fantastic. Of course, also being able to show these things. Next week at IW will be also fantastic technically. Is there anything. That we feel like will help. Less technical folks. You know, enjoy this or, or, or, or feel the, the, the power or the, the progress of this. I guess what I'm asking is what do you. Want to show in, in, in our five minute times with each person or 10 minute times with each person. What is it that we want to show. We want to show certainly from our agents that, that we made a connection and there was a chat. Is there anything else that will kind of help hit this home for, for people. So I would find it nice if we have. One or multiple posters. Depending where we are at the room, we could have some posters at the wall. But I think that maybe every team has a poster just explaining very basically what they are doing. So because it's in. It's, it's quite complicated to really understand what's going on, but visually it's more easily. Every team has a poster which just lists the features. So just an easy idea to produce. Okay, is that. I would love to make that more digital. Well, if I was on the same thing since you're talking about less technical people, I'm here. So this is, I've been interested in overall security identity and all that. So I know what the areas is for. I know what did come is for now. So I'm going to talk about how they work together. However, how is this like put together? How do they work with relationship with the distributed identity foundation. And the hyper ledger foundation. And also, they're also like open ID. That's very popular in the open in a CNCF security. How all this integrate together, how they fit together in a bigger picture. And specifically. You already have a pretty nice table content will be great to have more simplified. Like a table of what the protocol are. And. Yeah, it just kind of for education purpose for non tactical people. And overall, I guess this is just a big picture. Right. And put together what kind of problem that they saw. Yeah, very good. I, my sense then is that I should create a video. I mean, we've been talking about the highlights video, but maybe that's the point of the video that someone could. Sit and watch it for five minutes or two and a half minutes or whatever. Kind of understand how this all plays together. And then when they, you know. Spend time with us another five minutes, let's say. Then, you know, they're seeing it actually working, but to have an idea of how it fits. Because, you know, I do think that what you're saying, if you weren't about the poster and posters are fine too, like a physical poster would be good, but I guess digitally, I want to give people a fairly fast way to come up to speed. Yeah. I like that. I love it how it fits within Aries diff. Open ID connect. One area I'm actively involved in it's the, because I'm a database guy, so I'm interested in the, like the species, species spire, like the continuous authentication protocol that's going on in the, in the, in the CNCF work. So I just wonder how does this, is this going to help in that area going forward in the future. Continuous authentication. I'm not super. I mean, I kind of can glean from what it's called. Does anybody have thoughts on. Continuous authentication. Or, or maybe a little more about that will help. The project name is called species spire, species, but SPI FFE. And then the SPI RE is actually implementation. So the idea is every, every, every connection you to the database is, is authenticated. So it's now like a, it's kind of part of the real trust. Because I'm a database guy. I saw how the, how the real trust every, every time you connect to the database is authenticated. So, um, yeah. So that's why I'm looking at all these different protocols. And I mean, having distributors, authentication seems to be interesting. And then, um, and then, yeah, how does to come help that? Yeah. Okay. Yeah, very good. Yeah. Good insights. That's victory. Yeah. Thanks, Victor. I like, uh, it's, it's nice to have that perspective because we're so stuck on just, uh, you know, trying to get these protocols to interoperate. It was a big one. Yeah. I think that's really cool. I tore everything. Oh, it's, uh, right. Good. Okay. Other thoughts that will help hit this home. I mean, I think. I think for sure these two are huge. I love the idea of a poster. Um, it just makes me nervous having a physical thing. Uh, you know, in the next week. And having maybe we can. Yeah. Uh, if we have a table near the board. Whiteboards. Maybe we can use those as the, yeah. We can write it down there, right? But I don't know which table. How does assigned tables. Maybe we can ask. Yeah. And certainly on our laptops, we could, you know, kind of have like a summary. Maybe of ours, our particular. Uh, Summary of our. Agent. People abilities. Yeah, something like that. Okay. Yeah, though, I think all of those are good options then. Basically to have a visual aid. Okay. Good. How much do people care about the video idea? Do people feel like that is, um, absolutely necessary. Uh, a nice to have. Or something that, you know, we should really strive to have. Because, you know, my point of view, it's like, uh, you know, just because I've made a bunch of videos, like, okay, this seems like, you know, a natural fit, but I want to make sure that I'm not just. Yeah, go ahead. Yeah. Again, I'm totally non-technical in this area. Um, so yeah. You'll be nice. And also what happened real helps really well is I'm also joined. I'm not used to this area where I have time right now. So the open SSF open spirit foundation, they have a, a product, what is the project does a diagram. And so what they do. So when I joined that, because I want to learn what's going on, right, so the diagram helps me like, uh, navigate what's going on in the community and what project and how they're related. So not video is definitely a great idea. It'll be great even, even have a diagram which helps them, you know, of course that diagram can also be updated to reflect changes in the relationships. Okay. Yeah. Very good. Regarding the video, I think that could also be something which we can do after IW. So then we have some photos and some report what happened there. And I think the video is more something we can share over social media or give people. I don't think that the impact of a video, um, while the conference happen, it's happening is so big because the, most people don't have the time to, or it, I think it's hard really to watch a five minute video while all the people are running around and they don't see it and the acoustics of it. So I think it's a great idea. I think that the impact of the video should be designed or should be for a larger audience. And therefore it's, I think it's fine if we do that afterwards. Okay. Yeah. And again, I'm not going to IW. That's why I agree for someone like me who is totally new to this area and after IW probably. Okay, great. Okay. Yep. And I see Alex saying he thinks the diagram might be more helpful. I thought that Bjorn had pretty much. Yeah. Good. All right. Very good. That's great. That puts certainly less pressure on me for over the next week. So great. Yes. Right. Yeah, let's, um, I mean, certainly I guess the video will essentially be the video of all these different parts and just explaining it. So, yeah. Good. Very good. Somehow showing, yeah, there are, there are many different Asians on the table. That's I think one of the key things is not only. But the amount to it's going to be like, yeah. Five, yeah, six, whatever. We have. Good. Yeah, I guess it is right. It won't be obvious when people approach the table that they're essentially approaching. That the connectathon is that they're approaching. A bunch of different, we'll call ourselves vendors. We're, yeah, a bunch of different teams. They're doing a connectathon so that that will be. Something we need to repeat over and over again. I think. Any other thoughts on that? I mean, that this is where the poster idea, I think, you know, is nice because. You know, it's good to see each team. Kind of highlighted and represented. So this diagram then. That we like. Is this diagram a diagram of each vendor. Interaction so essentially like a more visual. A version of the table. That Rodolfo created, or is it more of a diagram of how did calm fits in the SSI ecosystem, or both. I would think that Victor, for instance, would want to see how did come fits in the SSI ecosystem. But then yeah, we also want to highlight interoperability, I guess across vendors. Any thoughts on that? We'll try to make both happen, I guess. Certainly if I was going to create slides for a video, I'd try to highlight both so. Okay. All right. Well, okay, so given, you know, everything that we've listed. What do we, what is. What do we absolutely need to do this week. We would add the flurry of activity from last week was amazing. I think, you know, really great results. I mean, this is our table here is a huge leap forward. We got updates from. Roots ID folks and block trust. And regarding for Ramo. Yeah, what else. Yeah, I think, I think, well, yeah, go ahead. Sorry, Rodolfo, go first. No, it's okay. No, I'm saying that I think we tested between the two of us, maybe the Ramo and prison are the one that we should focus. And that's what I think is, we are ready. Yeah, I get it at the point that is, I think, comfortable to show that in a, even in the demo, not another video, we can put that web page and send messages. I'm going to see on that. Yeah. Dashboard, right? I think the prison and the, maybe the, the prison wallet that made Tony would have, I don't know which one he's going to use that one. I think it's the one that needs to be tested or find what what's going to be. Um, maybe I don't know Alex, the Ramo, right? Yeah. It goes out the best person to test with the prison agent type thing or like, who can we test against? Make sure that it works before the actual demo. Cause like, I was able to test like prison, like the prison agent would be on the like wallet, for example, right? But should I try to run like Gonzalo wallet or is that like what he's using? Cause like, I know like he was working on updating some of the code as well. And like, so yeah. Yeah. Yeah, I don't know. I'm going to ask. Yeah. I'm going to ask him. Right now. And ask what it's going to do. Yeah. And then like from the veramo side, I know like veramo to veramo works, the veramo to sick by libraries. We can decrypt messages. But they cannot encrypt them and send them back to the sick by libraries as far as I know right now. So one of the veramo devs is going to be back tomorrow and I'm going to try to meet up with him to, to finish the, the rest of it. So that's where I'm right there. Okay. And yeah, I mean, it's important that we just to remind everyone it's important that we collect all of these difficulties or, you know, challenges, all the work that we're doing. So that when future vendors want to. You know, join our ecosystem that we're helping to create that they can navigate these issues quickly. So some of that might be updating the spec, for instance, but it sounds like a lot of it is just engineering. For example, like the veramo guys, the reason why they couldn't decrypt is because they were missing some as algorithm that didn't support for the library. So they had to implement that. So where, where are we capturing those aspects? I can write it in, in the, in here, like the, the pull request that was made to, to fix that issue. I can put it in the HackMD, for example. Okay. So that'll go under like issues found. Yeah. Yeah. Similar to like the Rosvalet block trust. Okay. Like a Rosvalet to veramo. Same. Yeah. Yeah, just to remind everyone the hope is that the result of all of this produces, well, in, in the, the ideal case, it produces a, a test harness. It did come V2 test harness that basically a new vendor can approach and, you know, as long as they can work with that test harness, they work with all of us, you know, hopefully. But in the minimum case, I feel like this documents will stand as a guide to help people to not only connect with us to know who to try to reach out to, to, you know, work with, but also to, you know, follow something that says, Oh, you know, I'm having that same issue and this is how we get past it. So. Okay. An integration guide, I guess, basically what I'm saying. Oh, any chance you can give me any access to the HackMD for the email. Yes. Thank you. We've got Bjorn and Rodolfo so far. Happy to invite others. Alex, what's your. Andre at roots ID. Yeah. Sweet. Thank you. I do here invite. Right. And if the way that I'm doing this is not as good as some other way, let me know because HackMD, I'm not as good at, I haven't used it as much so far. I've loved it, by the way, but. Okay. Well, I think this is fantastic. I feel like we're not scrambling, which is a good feeling. So thank you all for everything that you did over the last week because I was, I was much more concerned a week ago. I'm much less now, I think that we've probably shown enough that. Yeah, we won't. We're definitely way beyond embarrassing ourselves at our own event. This is excellent. Now I just want to make sure I really appreciate Victor's point of view and feedback because I want to make sure that all of this work hits home when people are at IAW with us. Yeah, to make it even easier for really newbie like me, if there's any, I don't know on this website, you already have a lot of description. It would be great to have like a more links to individual protocol and what the uniqueness of each one description or what they do. That'd be even better. Right. So from didcom.org, you can browse protocols and the protocols have the versions. And yeah, this gives kind of a description of all those protocols, but we definitely should do we highlight the version of each protocol that we use. I mean, essentially, the spec spells out some of that, but do we think we should list that here? We certainly said that we were going to have a table of protocols. So I think that making sure that people know what version is good. Let's see what we did here. Okay, our links look pretty good with the versions. Any thoughts on that? I do think it can be confusing just sending someone here, right? Okay, here's the problem. I mean, this is nice when I'm trying to look like, oh, you know, I know I'm looking up trust ping, for instance. Yeah, if you look at the CSCF landscape, which is pretty nice. I can drill down. So first of all, it's a table. And it'll be, of course, it'll be even nicer if it's a diagram, but the table is okay. So when you drill down, they go into the each individual project and give a lot of descriptions. And yeah, it'll be great to have a, ideally, yeah, like a diagram which groups on what, you know, what each area, you know, what the different protocols, different project do. And yeah. Okay. Yeah, that's helpful. Can you link me to the diagram that you're talking about for CNCF? Yeah. Thank you. This maybe hopefully that will inspire us. Is it the cloud native foundation or something like that? The sports Kubernetes. When I typed in CNCF, yeah, I came to the cloud native computing foundation, but I. Yeah. Okay. So. I think that's another hyper ledger project, right? There's more. It's Kubernetes basically. It's not just Kubernetes, but it's, yeah, I just posted that, that landscape. So if you, if you, if you drew down that. Yeah, it will give a, yeah, if you pick anyone on. I just pick anything. If you drew down, yeah, have a, what it does is actually automatically collect a lot of the information from like GitHub and fear. So, so you can tell what's going on with the project, how active it is. Yeah. A lot of good information. This is, this is cool. Definitely someone spent some time on it. So it will take time for us to catch up to this level. But I love it. Yeah. Yeah. And you know, Thomas this look from Nessus was talking about. Essentially. Yeah. A certification path for. For essentially the work that we're doing. So. Yeah, this is, this is hopefully our future. This is hopefully how awesome did come. You know, we'll become in whatever version it will be. Although this is, wow, this is such a big ecosystem. Yeah, maybe SSI actually needs this. Market cap on the start. Yeah. What's our market cap right now. Okay. Very good. I love it. I'm going to put this in the document as a. Even this one is still being worked on their efforts to do like diagrams. So focus on what area and then just kind of give workflow this way. Kind of have more intuitive. Like understanding of what's going on in the ecosystem and how the project is related. That was kind of good stuff. Yeah, very good. I mean, that diagram. So, yeah, I could imagine someone could spend their entire life working on that and it will never be finished. Yeah, the amount of drill down that you could do. It's pretty endless, I think. So that's great. Excellent. Thank you, Victor. Okay. Other thoughts. Let's see. We have 20 minutes. So. I guess I'll, yeah, I'll open it up to whatever someone wants to talk about or things that we need to discuss. We've got 10 days still demo or nine days still demo. Who's coming in on Monday for IWS or will everybody be there Tuesday morning, I should say, for the start of the. Yeah, I'm arriving Monday late night. So, okay. Okay. Same here. Yeah, I'll be there Monday night. Yeah, same with me. Okay. Yeah, I will have traveled the entire coast of California. So I'm getting into LA on Friday and then I'll travel up the coast and so I'll see you guys Tuesday morning. Going on highway one. Yeah, I think parts of it have washed away. So I'll have to do a little bit of a reroute at one point. But yeah, I'll get to. It's a pretty. Go around some mountains. I don't know what mountain range that is the Big Sur mountain range, but. I'll kind of go up and around Monterey and a little bit back down to see the Big Sur area. I've never done any of that. So I don't know what I'm in for. How long is it? We're moving like three hours every day. Friday, Saturday, Sunday. Yeah. Kids. No, no kids. We're going to have fun. No kids. So when our market cap is 2.1 trillion, then I, you know, I can afford to bring the kids along. Good. Okay. Anything else that people are looking forward to then for IW, let's kind of talk then about. Are you aware of any sessions related to did come? V2 that we think about like last. Last IW, there was the did come V2. OIDC for VC. Session, which I was new to the concepts of OIDC. So that was like a lot for me to take in, but essentially in that session, similar to what I saw Redolfo posts recently. I can't remember where you posted that Redolfo. Maybe it was in, actually, I think it was a GitHub commit. Yeah. Yeah. Yeah. Do you want to talk about that just a little bit? Well, it was from Sam. So I was just adding, yeah. Okay. Links to the, yeah, to the podcast and to the current presentation. So it can improve that. It's part, it's going to be part of the. Good book. I can find some between did come and, and why DC. So some started that and I had some additional links. Good. But that we, yeah. Yeah, very good. In terms of, I was just thinking when we're actually doing the demo time. Let's see, just going down our list here. Yeah. So the roots ID will have three of us there. But perhaps we should kind of call out now what we're going to focus on. I mean, it's my intention to be. Moving between all of the groups and essentially videoing it. So that we can, you know, have our highlight reel. Redolfo, what will your focus be during the demo time? Will it be like the, the roots lab? Yeah, yeah, probably that one. Yeah. Okay. I'll be showing that with whatever other. Yeah, I think that, yeah, that will depend on some of the people who's approaching. Question they asked, right? I don't know. Yeah. Okay. Yeah, I will have the roots ID lab with the iOS and Android and trying to, yeah, directly. Whatever it's on the table. Okay. And then Alex, what do you see for your. I'll have the, I'll have the Brahmo and the Prism one, I guess, depending on like who wants to demo with like is Tony like going to like sit there with us. That thing. Like, I guess I can use. Yeah, you can assume Tony's going to be using like on Salos chat. You know, Prism chat. Okay. Yeah. So yeah, maybe we can sit like like in pairs, maybe with the army and Tony and Alex, for example, and do that. Showing that there are two different actors or vendors playing. Maybe that may work. Do you think. Because so we think Nick will be there as well. Right. Yeah, I can chat with Nick. I can see if we can like do something else like together as well. And if that's the case, then. Yeah, like maybe you can do the one with Tony. Or yeah, we'll see. Yeah, I'll try with Nick today about like what he like how he wants to do it. Yeah. Okay. Like figure out the logistics and like the demo and like the demo flow and who's sending who to what and yeah. I didn't get the Brian, which is going to be there or not. Let's see. So I. I chatted him. He said that he couldn't make our meetings today. But it's okay. It sounds like he's going to try to touch base with us at IAW in person. Okay. Yeah. So, so, so we had mentioned pairs. Do we think that let's take somebody like Tony, for instance, do we think that Tony will be only showing his interaction with one other person. During our time, like as a pair, or do we think that he'll be showing interactions with multiple people? I mean, obviously that's going to get more complex. Right. Thoughts. What's that say again. I guess who else would be showing it with. I guess what I mean is let's say that the, let's say that the chat that Tony has or can work with against the block trust and it can also work with the roots, maybe multiple of our vendor instances. Who do we expect that Tony will be working with multiple connections or just repeatedly showing the same connection, but then talking to the fact that, oh, we also work with them and we work with them. Any thoughts on that? Certainly to keep it easy, I would think he would repeat the same demonstration over and over again. I, you know, we may have this, the, the Nessus dashboard. So that's another agent that you can run. Yeah. You can show with Alex and the Nessus, for example. Yeah, I don't know. Nessus is not the one I work with recently, but anyway, for the others. So, okay, so I'll ask the same question from the Nessus point of view, do you expect that multiple people will be showing their connections to Nessus or do you think that we'll have one person who, you know, one vendor that's doing connections with Nessus. I mean, let's obviously in the worst case scenario, let's say that we only had pairs of connections working. It seems from our chart here that we were much better than that. But if we only had pairs, obviously we would only do pairs. But because we're kind of beyond that, I'm just wondering from the actual demo standpoint, will it be like, hey, let me show you that I did a basic message with BlockTrust. And then, hey, let me show you, you know, from my same app, now I'm doing basic message with, you know, pick something else. Nessus, also. Oh, I see, yeah. I don't know how it's going to be the dynamics on the table, but probably, yeah, I would say, for example, we are, we can try to explain with someone who approached that, that we can communicate. And then, okay, but also we can connect with Nessus. And we're showing that with the laptop that we both connect Nessus and explain maybe other people showing, and we can explain the same or keep the dialogue showing that, okay, we can connect with Tony as well. I don't know. That's where I think it's changed based on. Will you have also the Python notebook on a laptop? Yeah, right. Yeah, also Python notebook. And I think that, yeah, once we start talking and explaining to people based on the, you know, in the background, you explain different stuff and you say, well, what is, what we're doing that? What is the hard stuff on doing that? Why we need to do that, right? Why it's not, if you read the spec, but it's not working as expected every time. And I think that changed based on the, on who's on there. I think that they, they said it's going to be five minutes, but we know that that changed. Some people show to only two minutes and others for half an hour. Yeah. Okay, can I throw out there that for the Tuesday lunchtime that we do a pre connectathon, connectathon. I would love to see the dynamics kind of play out before it happens. So that we know, you know, because for one, one thing, you know, which things are we showing as emulators and simulators and which things are we showing on physical devices? All of that. Do we think that it's worthwhile on Tuesday? On Tuesday? Yeah. Yeah. Yeah. Yeah. Yeah. How about you? How about you? Bjorn, do you think it's worth? Yeah. That's, that's great. Also, can I load your Android wallet on my phone? We need to be there. Yeah. Yeah. Okay. But this just opens more possibilities. Yeah. Right. Yeah. So also you can have the block trust wallet open. In a window. Next to Nessos. On one of your laptops. Right, right. Yeah. Okay. All right then. We all know what we're doing then for lunchtime on Tuesday. That'll be great and maybe. Since the demo time is after lunch on Wednesday. And tell me if we're over practicing here, but would you all want to, you know, group together at lunchtime prior to the demo and to kind of prepare and make sure everything's working. Yeah. With the food on the table. Yeah. Yeah. Okay. Last minute, the wrap ups, right? So something is inevitably going to go wrong. I think. Yes. Yeah, we'll find out what does work. Absolutely. Yeah. We can show that. Okay. Yeah. We're going to prep time. Okay. So essentially our lunches for the first two days are. Reserved. Very good. Okay. Can I. Hold this. That work. No. That did not work. I'm kind of double stars going on there. Whatever design that language. Well, anyways. Okay. Maybe I can underline it. Yeah. Okay. I think we're going to have a couple of minutes left. Just trying to think any more logistics through. We're able to practice. Then we'll have our demo time. By then we'll know who, you know, what each vendor is going to show in terms of one or more. Connections. I guess some. So then because we're going to show Nessus. During the demo. Because part of one of the things that I triggered the video idea was because we knew Thomas wasn't going to be there to show his Nessus stuff. But because we're showing it during the demo, do you think then. That recording our interactions with Nessus prior to IW is not necessarily. Yeah. Now, because we have this dashboard, I think it's better to show that. Like. Yeah. Showing under the workplace. Okay. And then. Yeah. Post IW will post a video that. Shows those interactions. Okay. Yeah. Very good. Make sure I didn't put anything about the video. I and W highlight video. Okay. So we had listed that as option or. What am I going to do with this? Let's see. We'll just say post. Okay. Any other thoughts? Okay. I think a great momentum. Here. And I'm looking forward to it. This is exciting. So. Great to see everybody. Thank you. And hopefully. If, if for those who can make it to the user group, the Diff did come. User group this afternoon. Because I think. Fabio and some others will be there and, you know, we can bring them up to speed on. Yeah. So next Monday, we won't have the call, right? Right. I won't be. Right. I wonder. Okay. I'll try to. Yes. I know who to contact and I'll have them remove it from the. From the calendar. Yeah. Good call. Okay. Great. Thank you, everybody. Great to see you. Thank you. Thank you.