WEBVTT 00:00.000 --> 00:09.440 Thank you all for joining the very first 00:09.440 --> 00:11.280 Deverem of the day. 00:11.280 --> 00:15.280 9am is extremely early for everyone who's out late last night. 00:15.280 --> 00:17.840 Thank you especially for showing up. 00:17.840 --> 00:19.240 We're going to get started about three minutes. 00:19.240 --> 00:20.240 My name is Sean Bohan. 00:20.240 --> 00:23.240 I work for the Linux Foundation. 00:23.240 --> 00:25.560 This is not a Linux Foundation Deverem. 00:25.560 --> 00:29.040 This is the digital wallets and verifiable credentials Deverem at 00:29.040 --> 00:30.360 Boston. 00:30.360 --> 00:31.360 I'm incredibly honored. 00:31.360 --> 00:32.360 That's be careful. 00:32.360 --> 00:33.360 I like to tap. 00:33.360 --> 00:34.360 I can't do that with a mic on. 00:34.360 --> 00:36.800 I'm incredibly honored that I got to be the Deverem Manager for this. 00:36.800 --> 00:40.960 I got to work with the amazing presenters who are going to be here today. 00:40.960 --> 00:45.440 These are not Linux Foundation or open wallet Foundation projects, but they are part of 00:45.440 --> 00:49.800 the identity ecosystem which we're a part of and we're just absolutely psyched that these 00:49.800 --> 00:52.240 folks are going to be here and share their knowledge. 00:52.240 --> 00:53.560 Some of them are still on their way. 00:53.560 --> 00:54.880 I've gotten a couple of text messages. 00:54.880 --> 00:55.880 I'm in a cab. 00:55.880 --> 00:56.880 I'm in a cab. 00:57.120 --> 00:59.640 I've got the first 30 minutes. 00:59.640 --> 01:02.920 But it's happened to me too. 01:02.920 --> 01:08.280 But before we start, so today, I'm just going to do a welcome super high-level 01:08.280 --> 01:10.880 brought-over view of the Open Wallet Foundation. 01:10.880 --> 01:15.200 The next team from net company is going to talk about utilizing EUDI Wallet 01:15.200 --> 01:18.480 ecosystems in your legacy systems. 01:18.480 --> 01:22.240 At 10 o'clock, we need disposable digital identities for a more secure and resilient 01:22.320 --> 01:24.120 digital society. 01:24.120 --> 01:32.360 And that is Rob Lorna Friedger and Andrea from 4th bomb slash Dine. 01:32.360 --> 01:36.040 After that, we have Jesse, our current standards enough towards verifiable credentials 01:36.040 --> 01:38.800 with expressive zero knowledge query. 01:38.800 --> 01:40.600 After that, Amir is going to join us. 01:40.600 --> 01:44.280 He's going to talk about Dark Five, zero knowledge cryptography for anonymous unsensitive 01:44.280 --> 01:46.000 organizations. 01:46.000 --> 01:50.920 Then, at 1130, trust change, trustworthy, decentralized public key infrastructure with 01:50.960 --> 01:54.000 Tim Pamela and Sam. 01:54.000 --> 01:57.880 At 12, we have Sample implementation of Open ID for Verifiable Presentation over Bluetooth 01:57.880 --> 01:58.880 Low Energy. 01:58.880 --> 02:00.840 I would like to apologize to all. 02:00.840 --> 02:01.840 I'm a giant nerd. 02:01.840 --> 02:06.560 I'm very excited about that one just because we have a project that works at Blue BLE 02:06.560 --> 02:07.840 and it's cool. 02:07.840 --> 02:12.520 And lastly, we are going to have folks vangalists and Connor Conners from the European 02:12.520 --> 02:16.960 Commission talking about challenges for wallets and digital trust services, following the 02:16.960 --> 02:20.040 EUDI Wallet Architecture Reference Framework. 02:20.120 --> 02:24.800 You'll hear folks today, probably call the ARF, that's the architecture reference framework. 02:24.800 --> 02:30.360 We just cut three letter acronyms, ARF, everything in the world in this world. 02:30.360 --> 02:34.360 All right, how today is going to run? 02:34.360 --> 02:37.840 I'm going to try to keep my comments to 15, 20 minutes. 02:37.840 --> 02:41.800 This way the next team can come up and get set up and it's nice and even. 02:41.800 --> 02:47.040 We would love it if you could give a 15, 20 minute presentation and leave time for questions. 02:47.040 --> 02:50.640 I have found the presentations are going to be awesome, but the questions actually make 02:50.640 --> 02:51.640 them even better. 02:51.640 --> 02:57.200 So by all means, if we please set aside time at the end of your session to do some Q&A. 02:57.200 --> 03:01.280 Also, if you have a burning question in the session ends and you really want to talk to 03:01.280 --> 03:03.000 that person, take them out into the hallway. 03:03.000 --> 03:04.960 This is a really small room. 03:04.960 --> 03:09.160 The acoustics are pretty good for our classroom, but we're also miked, so we don't want 03:09.160 --> 03:10.160 some cross-talk. 03:10.160 --> 03:14.000 It's going to hurt folks on the stream or in the video recording from later. 03:14.000 --> 03:17.000 And lastly, remember back in the day. 03:17.000 --> 03:19.000 At conference, we take a picture of the whole crowd. 03:19.000 --> 03:22.600 I'm not doing that, and I'm not doing that because I don't want anyone to get facially 03:22.600 --> 03:24.920 recognized by some platform 10 years from now. 03:24.920 --> 03:25.920 Unacceptable. 03:25.920 --> 03:26.920 Not doing that. 03:26.920 --> 03:28.400 I would take a picture from the back, but I can't get back there. 03:28.400 --> 03:30.400 So my name is Sean Bohan. 03:30.400 --> 03:31.880 I work at the Linux Foundation. 03:31.880 --> 03:34.960 I'm the community architect at the Open Wallet Foundation. 03:34.960 --> 03:41.440 The Open Wallet Foundation, I believe we turn two in March or April of this year. 03:41.440 --> 03:44.440 This is not, as I mentioned before, an Open Wallet Foundation room. 03:44.440 --> 03:47.960 This is a Boston room for digital wallets and verifiable credentials. 03:47.960 --> 03:48.960 This is about the ecosystem. 03:48.960 --> 03:50.160 It's not about us. 03:50.160 --> 03:54.200 I am currently lucky and honored to be able to be the devroom manager for this. 03:54.200 --> 03:55.680 I hope to do it again next year. 03:55.680 --> 03:56.680 This is my first Boston. 03:56.680 --> 03:59.040 It's been pretty amazing. 03:59.040 --> 04:05.280 So wallets are essential for digitizing our society. 04:05.280 --> 04:06.480 And they're already in broad use. 04:06.480 --> 04:09.280 Anyone who is, yes, my screen is working. 04:09.280 --> 04:13.200 Anyone who's taken a flight has been offered by the airline. 04:13.200 --> 04:18.720 Hey, do you want your boarding pass sent to your Apple Wallet or your Google Wallet, et cetera? 04:18.720 --> 04:19.720 They're used for payments. 04:19.720 --> 04:21.600 They're used for higher value credentials. 04:21.600 --> 04:27.600 We're seeing a lot of work right now in certain countries around mobile drivers licenses. 04:27.600 --> 04:30.040 And that's really differential. 04:30.040 --> 04:33.360 Like, identities in ecosystem, but what's happening in Europe is very different than what's 04:33.360 --> 04:37.920 happening in Canada is very different than the US or Australia or India, for example. 04:37.920 --> 04:42.120 I get to see all these things, which is pretty cool, but also the differences are what 04:42.120 --> 04:43.720 also make it really cool. 04:43.720 --> 04:49.880 And then wallets are becoming a cornerstone of digital infrastructure in our societies. 04:49.880 --> 04:52.560 I can't say everybody has a phone in their pocket. 04:52.560 --> 04:54.560 We do have a digital divide still. 04:54.560 --> 04:57.120 I started working on the internet 30 years ago. 04:57.120 --> 04:58.120 It still exists. 04:58.120 --> 04:59.760 There are folks who are not connected. 04:59.760 --> 05:02.960 We need to look at ways to support them as well. 05:02.960 --> 05:05.720 And that's something that we consider we keep in the back of our mind. 05:05.720 --> 05:09.440 Not just for people, I have a cousin who will not own a phone. 05:09.440 --> 05:11.000 I will not own a mobile phone. 05:11.000 --> 05:12.000 He has a phone in his house. 05:12.000 --> 05:13.000 He's a great person. 05:13.000 --> 05:14.720 He's just no. 05:14.720 --> 05:19.800 We need to make sure he's able to access all this infrastructure as well as folks who are 05:19.800 --> 05:22.080 on their 6, 7, 3, 5 phone. 05:22.080 --> 05:26.160 There are also numerous use cases, whether it's a refugee use case, whether it's a disaster 05:26.160 --> 05:27.160 use case. 05:27.160 --> 05:32.120 We just had massifiers in California where people literally lost everything down to whatever 05:32.120 --> 05:34.240 paper was in their pocket that they ran out of the house with. 05:34.240 --> 05:35.520 It's all they have left. 05:35.520 --> 05:39.400 How do they restore their identity life? 05:39.720 --> 05:41.200 Digital or otherwise. 05:41.200 --> 05:44.280 So these are not topics that are sort of like, it's never stuff. 05:44.280 --> 05:46.720 This is affecting everybody. 05:46.720 --> 05:49.040 And then digital walls and verifiable credentials. 05:49.040 --> 05:54.680 So it's a pretty, it's a, I just realized I'm blocking the screen and I apologize. 05:54.680 --> 06:00.520 It's a somewhat simple model. 06:00.520 --> 06:04.120 We should not have to go back to the identity issue every time. 06:04.120 --> 06:05.680 We want to show that credential. 06:05.680 --> 06:10.960 But I should not have to have Wi-Fi at the airport to show us. 06:10.960 --> 06:15.920 I might not be in a region with cell service and I need to pull up my mobile driver's license. 06:15.920 --> 06:23.120 All these things are sort of at the core of this and really it's the issuer and the verifier, 06:23.120 --> 06:25.240 but the user is at the center of this equation. 06:25.240 --> 06:29.520 And the user's device or cloud or hybrid of the device and cloud that are making this 06:29.520 --> 06:32.920 transaction work. 06:32.920 --> 06:36.240 And then we're the benefits of verifiable credentials. 06:36.240 --> 06:39.920 How many people here have ever rented an apartment? 06:39.920 --> 06:46.000 OK, how many of you handed over a folder of paperwork that could steal your identity 15 06:46.000 --> 06:51.880 times over to a person who, you know, has the key to the apartment, but you really don't 06:51.880 --> 06:55.480 know if they're the owner of the apartment, but you're pretty sure they had the key. 06:55.480 --> 06:59.080 And I just give this to them and hope they approve my rental. 06:59.080 --> 07:03.440 That was my sort of rabbit hole, my gateway drug into this industry. 07:03.440 --> 07:07.440 As I went and got a new apartment in two months later, I joined an organization that contributed 07:07.440 --> 07:09.840 some software to Linux Foundation. 07:09.840 --> 07:10.840 But verifiable credentials. 07:10.840 --> 07:14.560 So the end user gets more control, more privacy, more portability. 07:14.560 --> 07:18.920 In some identity spaces, I've described this as giving the user, the user is taking, not giving. 07:18.920 --> 07:20.960 The user is taking new superpowers. 07:20.960 --> 07:24.480 With these verifiable credentials, they can create compound proofs, they can do lots of things 07:24.480 --> 07:26.040 with them. 07:26.040 --> 07:30.360 That will give them new abilities, new capabilities, give them more scale in the transactions 07:30.360 --> 07:32.360 and digital life that they have. 07:32.360 --> 07:38.080 It's cheaper, it's faster, it's more secure, after it's depending upon what we're doing. 07:38.080 --> 07:42.480 And while it's transforming physical credentials into digital ones using verifiable credentials 07:42.480 --> 07:45.680 and a universal approach. 07:45.680 --> 07:50.800 Within my team, there are a lot of futures for verifiable credentials and wallets. 07:50.800 --> 07:55.840 One of those futures is one wallets to rule them all, and in the darkness bind them. 07:55.840 --> 07:57.960 Hey, hey, four plump teams here. 07:57.960 --> 08:01.160 One wallets to rule them all, and in the darkness bind them, right? 08:01.160 --> 08:05.800 I don't love that world, I don't love the fact that I have issues porting from Apple 08:05.800 --> 08:09.840 to Android, and I like Android, I have an Android phone at home. 08:09.840 --> 08:13.920 The other way, the other alternative, is every single relationship you have has its own 08:13.920 --> 08:16.600 wallet, and all of them are on a different upgrade schedule. 08:16.600 --> 08:20.720 And every time you really need them, there's no Wi-Fi, and it hasn't updated and you 08:20.760 --> 08:23.480 can't show that credential, that is bad. 08:23.480 --> 08:26.520 Then there's also a middle ground, but some of my colleagues, and I really believe in, 08:26.520 --> 08:29.120 it's going to kind of be like browsers. 08:29.120 --> 08:32.320 You've got a wallet for work, you've got a wallet for home stuff, you've got a wallet for 08:32.320 --> 08:33.720 your healthcare. 08:33.720 --> 08:37.640 I have a browser for work, and I have a browser for home stuff, and I have a browser for 08:37.640 --> 08:39.480 finance, none of them touch. 08:39.480 --> 08:42.360 I have never opened up a work thing on my home browser. 08:42.360 --> 08:47.240 They may be on the same computer, but I don't let those worlds collide or even get in touch 08:47.240 --> 08:48.240 with each other. 08:48.240 --> 08:54.240 There are a lot of different ways to look at this technology and how they're going to work. 08:54.240 --> 08:58.160 And a couple of examples we put in here, the mobile driver's license is, again, as we 08:58.160 --> 09:00.480 said before, it's geographically spread. 09:00.480 --> 09:03.640 In the United States, there are a lot of states, really interested in mobile driver's license. 09:03.640 --> 09:08.320 It's really interested in either getting pulled over, or when you walk into an office building, 09:08.320 --> 09:10.960 bam, show your phone, and you've got an MDL there, it's ready to go. 09:10.960 --> 09:11.960 Welcome. 09:11.960 --> 09:12.960 Thank you. 09:12.960 --> 09:17.360 And also the EU Digital Identity Wallet, also called EUDI, we're going to refer to as EUDI during 09:17.360 --> 09:21.640 today, and also the ARF I mentioned before. 09:21.640 --> 09:26.280 And so who are we, the Open Wall Foundation, we're a neutral home for open source projects 09:26.280 --> 09:30.080 and the communities that build them in the development of interoperable digital wallets. 09:30.080 --> 09:33.680 Interoperable is the most important thing for us if we are building new silos we have 09:33.680 --> 09:34.680 failed. 09:34.680 --> 09:38.120 If these things do not work, crossboard or we have failed. 09:38.120 --> 09:41.800 But there will never be an open wallet wallet. 09:41.800 --> 09:46.280 These are projects that people are building and contributing to and maintaining, and 09:46.320 --> 09:52.360 someone else is taking that code and building a wallet from it for a company, for a government, 09:52.360 --> 09:58.800 for a dog boarding place. 09:58.800 --> 10:03.560 So you can have a QR code that I can give to my neighbor to go get my dog because my 10:03.560 --> 10:06.120 train is like getting back from the Boston. 10:06.120 --> 10:08.440 Those are all real use cases. 10:08.440 --> 10:13.960 Our goal in this is to help these communities build these projects. 10:13.960 --> 10:18.440 And I'll go in a little bit about governance in a second. 10:18.440 --> 10:20.720 And I am absolutely shocked that I'm only eight minutes into this. 10:20.720 --> 10:22.880 I am super impressed by myself. 10:22.880 --> 10:25.400 I'm going to give you a dramatic reading of this. 10:25.400 --> 10:29.960 It's a consortium of companies and nonprofit orgs, collaborating, drive global adoption. 10:29.960 --> 10:31.560 We do not do standards. 10:31.560 --> 10:32.560 Let me refer to that. 10:32.560 --> 10:33.560 We do not do standards. 10:33.560 --> 10:34.560 We do code. 10:34.560 --> 10:36.400 We work with STEOs and standards bodies. 10:36.400 --> 10:38.600 We work with folks working with standards. 10:38.600 --> 10:42.160 We are standards are part of our ecosystem, but we are actually working with the folks who are 10:42.160 --> 10:43.640 building the code. 10:44.200 --> 10:47.800 Secure and interoperable digital wall solutions, as well as providing access and expertise 10:47.800 --> 10:49.600 and advice through a government advisory council. 10:49.600 --> 10:50.960 This slide is already dated. 10:50.960 --> 10:52.040 I will explain why in a second. 10:53.040 --> 10:53.840 Get a hand rest. 10:53.840 --> 10:54.880 Oh, no, sorry. 10:54.880 --> 10:58.840 And we set, we aim to set best practices for digital wall technology through collaboration 10:58.840 --> 11:02.160 on standards based OSS components, open source software. 11:02.160 --> 11:05.760 That issuer's wall providers and relying parties can use to bootstrap implementations 11:05.760 --> 11:09.320 that preserve user choice security and privacy. 11:09.320 --> 11:13.520 I mentioned before, the renting and department idea, all of that could be handled 11:13.520 --> 11:14.520 with verifiable credentials. 11:14.520 --> 11:17.480 I get a credential from my bank saying that I am a customer of the bank. 11:17.480 --> 11:22.680 I get another credential from my bank saying, oh, he's got a balance of X or even better 11:22.680 --> 11:26.240 a zero-knowledge proof that says, here's a predicate. 11:26.240 --> 11:28.440 His balance is more than Y. 11:28.440 --> 11:29.440 That's the world I want. 11:29.440 --> 11:32.800 I don't want anyone to know what my balance is. 11:32.800 --> 11:36.520 But these are things that we can help build. 11:36.520 --> 11:41.400 And then our technical community is 100% open and it's led by diverse group of contributors. 11:41.400 --> 11:43.160 Everything we do is an open source. 11:43.160 --> 11:44.880 All of our code is either Apache 2. 11:44.880 --> 11:48.120 We do have one or two projects using MIT. 11:48.120 --> 11:51.080 For IP concerns, which I am not a lawyer, I don't play one on TV. 11:51.080 --> 11:55.160 I'm not going to discuss because I don't have credible opinions here. 11:55.160 --> 11:58.920 We really don't work with GPL at all for IP protection purposes. 11:58.920 --> 12:01.800 But we support the communities that are building this software. 12:01.800 --> 12:04.320 And I'm going to go through a bunch of our projects in a second. 12:04.320 --> 12:07.480 But most important for us is this diverse group of contributors. 12:07.480 --> 12:09.280 Why? 12:09.280 --> 12:12.960 We have seen multiple times in different parts of the Linux Foundation. 12:12.960 --> 12:16.400 Two people have an awesome project and they're building it in great. 12:16.400 --> 12:17.680 But they don't bring anybody else in. 12:17.680 --> 12:20.880 Or they have a hard time finding contributors and other maintainers. 12:20.880 --> 12:23.000 And all of a sudden somebody gets a root canal. 12:23.000 --> 12:28.040 And we have lost a maintainer for a project that other people are depending on. 12:28.040 --> 12:30.040 One of my good friends, Brian Belendor, who's here. 12:30.040 --> 12:31.040 I haven't seen him yet. 12:31.040 --> 12:32.040 I'll see him later. 12:32.040 --> 12:34.120 He's called this permissionless innovation. 12:34.120 --> 12:37.600 Permissionless innovation is awesome because anybody can take this code. 12:37.600 --> 12:40.200 But he can look at it, use it, modify it. 12:40.200 --> 12:41.320 They don't have to tell me. 12:41.320 --> 12:43.080 They never have to tell me. 12:43.080 --> 12:46.640 Which also stinks because I wish I knew when there are cool projects working with our 12:46.640 --> 12:49.040 code and I usually find out after something is long. 12:49.040 --> 12:50.040 That's OK. 12:50.040 --> 12:53.440 I then call those folks and say, hey, can we get you to come and do an AMA or a workshop or 12:53.440 --> 12:54.960 a webinar or something? 12:54.960 --> 12:59.520 But that being said, contributor diversity is critical to these projects. 12:59.520 --> 13:02.840 And we're going to talk about our lifecycle in a second and how we go from labs to growth 13:02.840 --> 13:04.240 to impact projects. 13:04.240 --> 13:07.520 And one of the biggest requirements for graduating those stages is 13:07.520 --> 13:08.520 developer diversity. 13:08.520 --> 13:10.400 Is contributor diversity a maintainer diversity? 13:10.400 --> 13:16.160 If everyone's from one company, cool, except when that company does a lay off. 13:16.160 --> 13:19.040 And the principal engineers and maintainers have to go. 13:19.040 --> 13:22.520 They split, they can't work on the same or the company pivots. 13:22.520 --> 13:24.880 That happens all the time. 13:24.880 --> 13:26.760 Terrible, somewhat funny story. 13:26.760 --> 13:30.720 We had a wonderful community developers from one company, all four of them wrote a quarterly 13:30.720 --> 13:31.720 update. 13:31.720 --> 13:33.360 The quarterly update was like, we got two more maintainers coming. 13:33.360 --> 13:34.360 This is going to be great. 13:34.360 --> 13:35.880 Oh, you guys, you're nailing it. 13:35.880 --> 13:37.480 Six weeks later, one of my colleagues says, you know, 13:37.920 --> 13:41.480 this guy's haven't done a commit in weeks. 13:41.480 --> 13:45.120 All right, send an email, reach out on discord. 13:45.120 --> 13:46.600 Send an issue, won't get hub. 13:46.600 --> 13:47.320 Finally, here back. 13:47.320 --> 13:50.600 Oh, yeah, you know, after we wrote the quarterly update, we were really 13:50.600 --> 13:52.440 psyched about the new maintainers. 13:52.440 --> 13:53.560 We all got re-ordered. 13:53.560 --> 13:54.920 So we're not working on it anymore. 13:54.920 --> 13:56.960 Now, we have people relying on this software. 13:56.960 --> 13:57.720 It's not. 13:57.720 --> 13:59.880 It's somewhat funny, somewhat sad. 13:59.880 --> 14:03.680 Folks are relying on the software and the team developing it is gone. 14:03.680 --> 14:06.040 And how do we avoid that? 14:06.040 --> 14:08.480 We avoid that by having contributed to maintain a diversity. 14:08.480 --> 14:11.400 Bring people from outside your organization, both individuals, 14:11.400 --> 14:12.480 but also companies. 14:12.480 --> 14:14.680 If you're relying on the software, you want to make sure it works. 14:14.680 --> 14:19.280 You want to make sure that it is going and growing in a way that you need. 14:19.280 --> 14:20.200 I call it relying. 14:20.200 --> 14:22.280 Some people say, depending, I love the word relying. 14:22.280 --> 14:24.680 I need this software to work for me in my use case. 14:24.680 --> 14:26.960 I want to be involved in that roadmap. 14:26.960 --> 14:28.760 I want to be involved in contributing that software. 14:28.760 --> 14:33.200 Making sure my voice is heard and that project isn't moved forward. 14:33.240 --> 14:36.760 So what do we do at the Open Wall Foundation, code outreach and ecosystem? 14:36.760 --> 14:38.600 These are the three most important things for me. 14:38.600 --> 14:40.880 Everything else is secondary, tertiary. 14:40.880 --> 14:43.200 I'll get into the code in a second, but outreach. 14:43.200 --> 14:47.040 How do we reach out to folks who are using our software? 14:47.040 --> 14:49.880 My least favorite thing in the world is when I walk into my boss, 14:49.880 --> 14:52.040 and she says, hey, by the way, did you hear the nation of Bhutan 14:52.040 --> 14:53.840 is using Occupy? 14:53.840 --> 14:56.320 And I'm like, no, I didn't have to go find people in Bhutan now, 14:56.320 --> 14:58.640 who are doing this, and, you know, it stinks for me, 14:58.640 --> 15:01.720 but it's awesome for the ecosystem. 15:01.720 --> 15:04.920 But we need, as the Linux Foundation, to be reaching out to folks all the time. 15:04.920 --> 15:08.080 And when someone comes to us and says, hey, we're interested in this project, 15:08.080 --> 15:09.400 how do we get involved? 15:09.400 --> 15:11.760 Half of my job is giving them the on-ramp for it, 15:11.760 --> 15:14.920 and making sure that on-ramp is low as possible, so that their teams, 15:14.920 --> 15:17.680 with that individual, has a great experience. 15:17.680 --> 15:18.560 I'll go into that in a second. 15:18.560 --> 15:21.240 And then most importantly, the ecosystem that's why we're here today, 15:21.240 --> 15:23.720 that is why none of the sessions that they are open 15:23.720 --> 15:26.360 while the foundation sessions of the online, obviously, 15:26.360 --> 15:29.480 because this ecosystem is where the work is going to happen. 15:29.480 --> 15:34.920 And we're absolutely for it, and we absolutely want to see that work. 15:34.920 --> 15:37.440 So our technical, the way our projects are run, 15:37.440 --> 15:39.440 we have a technical advisory council. 15:39.440 --> 15:40.560 This is the leadership team. 15:40.560 --> 15:44.720 These are senior maintainers that lots of very large and small organizations. 15:44.720 --> 15:47.600 We have seats on our tack from impact projects. 15:47.600 --> 15:49.640 I'll go through one of impact projects in a second. 15:49.640 --> 15:52.840 Seats on our tack come from our members, and we have two at-large seats 15:52.840 --> 15:55.440 on the technical advisory council. 15:55.440 --> 15:57.520 They do not tell people what to do. 15:57.600 --> 15:59.480 They do not tell people how to code. 15:59.480 --> 16:02.600 They do not tell people what they should be doing. 16:02.600 --> 16:03.920 We do. 16:03.920 --> 16:05.840 We are prescriptive around things like security. 16:05.840 --> 16:07.840 We are prescriptive around things like a code of conduct 16:07.840 --> 16:09.040 and being good. 16:09.040 --> 16:10.240 Hey, welcome. Come on in. 16:10.240 --> 16:11.040 Grab seat. 16:11.040 --> 16:13.120 Being great to new contributors. 16:13.120 --> 16:15.280 Low, you know, having security policies, 16:15.280 --> 16:18.720 having contribution policies, having good first ticket tags 16:18.720 --> 16:19.560 and get hugged. 16:19.560 --> 16:21.280 Those are all critical to us. 16:21.280 --> 16:24.120 But there's no, like I don't like the way you did that commit. 16:24.120 --> 16:25.880 Like, ah, ah, did you DCS sign off? 16:25.960 --> 16:27.280 We respect you as a maintainer. 16:27.280 --> 16:30.120 We want you to build this project in a way that you need to get a building. 16:30.120 --> 16:31.400 We have project maintainers. 16:31.400 --> 16:34.040 These are the senior contributors on any project. 16:34.040 --> 16:36.040 I mentioned maintainer diversity and contributor diversity 16:36.040 --> 16:36.840 before. 16:36.840 --> 16:41.560 These are the elders on any given project 16:41.560 --> 16:44.920 who are not telling folks what to do, but they are leading. 16:44.920 --> 16:47.080 They're helping new folks and new contributors 16:47.080 --> 16:48.600 get through their first couple of tickets. 16:48.600 --> 16:49.960 Get a couple of bugs fixed. 16:49.960 --> 16:51.320 Hey, you got an idea for a module. 16:51.320 --> 16:52.680 Let's work on that together. 16:52.680 --> 16:53.880 They're reviewing PRs. 16:53.880 --> 16:55.400 They're writing their own PRs. 16:55.480 --> 16:56.920 All of them have a vested interest. 16:56.920 --> 17:00.040 And they rely on the software that they're building for a dozen reasons. 17:00.040 --> 17:02.520 And when we talk about, there was a funding session yesterday, 17:02.520 --> 17:04.280 which I only caught a couple of, of devrims. 17:04.280 --> 17:07.160 And it, uh, a couple of sessions for it. 17:07.160 --> 17:11.720 Like, they may be folks who rely on it because they're consultants who use the software with their clients. 17:11.720 --> 17:16.120 They may rely on it because their company has basically hired them 17:16.120 --> 17:18.120 to build this open source product 17:18.120 --> 17:21.560 that their companies either using or relying on or selling to others. 17:21.560 --> 17:25.160 And then we have project stages, um, labs growth and impact. 17:25.160 --> 17:28.440 Labs, I made a joke before about two cool people. 17:28.440 --> 17:29.880 Decide they have some code. 17:29.880 --> 17:30.920 They want to make a project. 17:30.920 --> 17:33.080 They don't know if they have traction, but they have working code. 17:33.800 --> 17:34.920 Let's start a lab. 17:34.920 --> 17:37.640 Let's see if we can build a momentum around this project. 17:37.640 --> 17:40.040 Let's see if we can bring in contributors from outside. 17:40.040 --> 17:42.760 Part of my job is when someone says, hey, do you have something that does X1s? 17:42.760 --> 17:44.120 And look, well, you should talk to this lab. 17:44.680 --> 17:47.960 They're not production ready in production software. 17:47.960 --> 17:49.800 They're learning, they're growing, they're building a community. 17:49.800 --> 17:50.760 Welcome, join us. 17:50.760 --> 17:51.720 They're building a community. 17:52.680 --> 17:55.240 The next stage, but to get to the growth stage, 17:56.200 --> 17:59.960 more mature, more POCs and pilots, in production some places. 17:59.960 --> 18:02.120 They need maintainer and developer diversity. 18:02.120 --> 18:03.640 They have other requirements they have to fill. 18:03.640 --> 18:04.920 I'm not going to go into detail here. 18:04.920 --> 18:06.040 It's all on our websites. 18:06.600 --> 18:09.320 But that growth, that graduation is a process. 18:09.320 --> 18:11.560 The attack is involved in reviewing the application 18:11.560 --> 18:13.800 to graduate, making sure that they're meeting the standards 18:13.800 --> 18:16.440 that we've set as a community to become a growth project. 18:16.440 --> 18:18.200 And then lastly is, is impact. 18:18.360 --> 18:21.560 These are senior projects in the market, in production, 18:21.560 --> 18:22.520 being used right now. 18:23.240 --> 18:26.840 In some cases, velocity is slow to little bit. 18:26.840 --> 18:30.040 They've gone from build build build to maintain build, maintain build, 18:30.040 --> 18:33.640 maintain build, but they're still, hey, welcome. 18:33.640 --> 18:35.880 Open source projects that are getting it done. 18:36.440 --> 18:39.160 And also, we look at them as senior members of the community. 18:39.160 --> 18:41.000 So I'll go through occupying the second. 18:41.000 --> 18:42.040 It's one of our senior teams. 18:42.040 --> 18:42.920 Hey, welcome. 18:42.920 --> 18:44.040 One of our senior teams. 18:45.080 --> 18:47.480 They've got to see it on the attack because they're an impact project. 18:49.160 --> 18:52.760 I expect all of you to be able to read this slide. 18:52.760 --> 18:54.200 And that's what makes it fun. 18:54.200 --> 18:56.280 These slides are going to be on the Boston website. 18:56.280 --> 18:57.640 There is a QR code there. 18:57.640 --> 18:59.800 I checked it again this morning to make sure it doesn't go to Facebook 18:59.800 --> 19:00.440 or somewhere silly. 19:00.440 --> 19:02.920 This is going right to our tax site with all of our projects. 19:02.920 --> 19:05.320 But really quickly, at the top, we've got occupied. 19:06.680 --> 19:11.240 It's secure interoperable communication between the identities. 19:11.240 --> 19:14.040 This is one of our senior most walled projects currently being used 19:14.040 --> 19:16.760 by a number of different companies and governments around the world. 19:18.280 --> 19:19.640 There's an organization in India. 19:19.640 --> 19:23.000 We have occupied came from the Aries community at Hyperledger. 19:23.000 --> 19:29.320 Occupy, Cretto, Bifold, Asgard, Al, and Didcom mediator service all came from Aries. 19:29.880 --> 19:33.160 And as a series of communities inside of Hyperledger, 19:33.160 --> 19:35.880 they decided the better place for them is the open wall foundation. 19:35.880 --> 19:37.400 We welcome them with open arms. 19:37.400 --> 19:38.360 There was no weirdness. 19:38.360 --> 19:41.160 I had one maintainer say to me, you guys met us? 19:41.160 --> 19:42.120 Like, absolutely not. 19:42.120 --> 19:43.160 And we support you. 19:43.160 --> 19:46.280 We want you to go where you feel you're going to get the most value in use. 19:46.360 --> 19:47.880 And get more exposure. 19:50.040 --> 19:52.280 Cretto, which is being built by a team of newtract, 19:54.360 --> 20:01.160 currently is being worked on with both the Sprint Funky competition for digital wallets, 20:01.160 --> 20:07.160 as well as it's in progress right now with the Republic of Ireland's EUDI wallet initiative. 20:07.160 --> 20:09.880 So they're working with those two teams in a company called near-form in Ireland. 20:10.920 --> 20:15.640 Bifold is in full development and is being used by the government of British Columbia 20:15.640 --> 20:18.760 and in the Penn Canadian Trust Framework, which are two different projects, 20:18.760 --> 20:21.240 but they're talking to each other all the time. 20:22.040 --> 20:27.000 Asgard, Asgard is within the Aries wallet environment and ecosystem, 20:27.000 --> 20:28.760 Asgard is the storage layer. 20:28.760 --> 20:30.200 That's where the keys are being held. 20:31.240 --> 20:35.240 Then you got Didcom mediator service, and Al is called Al, 20:35.240 --> 20:36.440 because they like the name Al. 20:36.440 --> 20:38.440 They wanted to call it open wallet labs. 20:38.440 --> 20:40.280 And I'm like, open wallet of something else. 20:40.280 --> 20:41.720 Like you can't do that, so we'll just call it Al. 20:42.680 --> 20:46.360 That is a test harness for Aries wallets. 20:46.360 --> 20:49.960 We are expanding that, which we're pretty excited about, not to just be Aries wallets, 20:49.960 --> 20:52.280 but to work on other wallets outside of Aries community. 20:52.280 --> 20:53.800 We have a lot of projects I'll go through. 20:54.680 --> 20:59.800 And then we got SD.java script, which I believe is working on an EUDI wallet initiative. 20:59.800 --> 21:03.160 Identity credentials, identity credential, which is now being called multi-pause, 21:03.960 --> 21:05.160 was contributed by Google. 21:05.160 --> 21:08.120 It's part of the Sprint Funky competition as well. 21:08.120 --> 21:11.320 It's being used in the EUDI wallet testing initiative. 21:11.880 --> 21:16.440 To volley, which is a lab, and VCAPI, also a lab. 21:16.440 --> 21:19.000 To volley is actually, I believe, being used in Africa. 21:19.640 --> 21:23.320 VCAPI is an implementation of VCAPI draft standard. 21:24.200 --> 21:26.760 Actually, a fantastic maintainer who's trying to build. 21:28.040 --> 21:29.320 And then we got more lab projects. 21:29.320 --> 21:31.960 I'm not going through all these, but they cover everything from Python, 21:31.960 --> 21:35.720 Kotlin.net, Rust, React Native. 21:35.720 --> 21:37.560 We have TrustBanding Protocol. 21:37.560 --> 21:40.840 We've got, you'll take a look at our list of projects. 21:40.920 --> 21:42.200 You'll see most in the right entity. 21:42.200 --> 21:45.400 We have one, which is sort of looking in the cryptocurrency space. 21:46.040 --> 21:49.160 The reality is, all identity problems are key management problems. 21:49.960 --> 21:54.200 Not that there's no difference between a cryptocurrency key and an identity key. 21:54.200 --> 21:57.560 There's lots of them, but effectively, that's a really good way to think about it, 21:57.560 --> 21:58.600 as far as we're concerned. 21:59.480 --> 22:01.800 And also, we added three new labs at the bottom. 22:01.800 --> 22:08.040 DC Decal, DCQL, TypeScript, OpenID for VCAIs, TypeScript, and OpenID Federation TypeScript. 22:08.120 --> 22:09.400 These came out of the Credo community. 22:09.400 --> 22:13.960 So that community, Credo, building their own wallet, implementing it in lots of different places. 22:13.960 --> 22:15.080 They were building their own tools. 22:15.080 --> 22:16.920 They turned around and said, let's give this back to the community. 22:17.320 --> 22:19.880 One of my favorite things that happened at OpenWall Foundation, 22:21.240 --> 22:23.480 when those projects moved over from Hyperledger, 22:23.480 --> 22:25.880 which is now the Linux Foundation Essentialized Trust, 22:25.880 --> 22:27.320 was they had a working group. 22:27.320 --> 22:29.960 And every week, they met and talked about the stuff going on in areas. 22:30.280 --> 22:32.200 And they're like, can we bring our working group to OpenWallet? 22:32.200 --> 22:34.600 And our only request was opening it up to everybody. 22:34.600 --> 22:36.840 So right now, that interoperability working group, 22:36.920 --> 22:38.360 yep, it's very, very eccentric. 22:38.360 --> 22:41.480 I've got folks from IronWorks who are working with the nation of Bhutan. 22:41.480 --> 22:44.600 Coming to that meeting to talk about making things more interoperable, 22:44.600 --> 22:46.920 helping to contribute to more did-com modules. 22:47.560 --> 22:48.840 It's the kind of thing we want to see. 22:48.840 --> 22:50.440 We're working with the whole community, let folks know. 22:50.440 --> 22:53.960 Not just that this meeting exists, because everybody has a full schedule. 22:53.960 --> 22:55.800 Every single person has a full day, 22:55.800 --> 22:58.600 but getting the projects to at least send a representative to these calls, 22:58.600 --> 23:00.120 so that they can have their voice heard. 23:00.120 --> 23:01.560 We don't want anyone left out. 23:01.560 --> 23:04.360 And I don't want anyone left out because they were too busy, 23:04.360 --> 23:06.520 or a project had too much going on. 23:06.520 --> 23:08.920 Like, we want to make sure we're being as welcoming as possible. 23:10.600 --> 23:12.040 And then lastly, oh, not lastly. 23:12.040 --> 23:13.080 But the OpenWallet's forum. 23:13.080 --> 23:15.320 I've got 10 minutes left, and I'm going to fly through these two slides. 23:15.320 --> 23:17.160 I mentioned before, outreach and engagement. 23:18.760 --> 23:21.480 Some of the feedback we got from a project a couple of years ago 23:21.480 --> 23:23.720 was we need better, this is an open-source project. 23:23.720 --> 23:25.960 We need better product marketing, which is really hard, 23:27.000 --> 23:28.520 particularly for an open-source project. 23:28.520 --> 23:30.520 Because in some cases, I'm going to take your code, 23:30.520 --> 23:32.200 and I'm going to run with it, and I'm not telling anyone. 23:32.200 --> 23:33.720 I don't have to tell anyone. 23:33.720 --> 23:35.880 And I'm building it inside my very large organization, 23:35.880 --> 23:37.560 and we're not talking about it. 23:37.560 --> 23:38.440 That's not messed up. 23:38.440 --> 23:39.400 That's open-source. 23:39.400 --> 23:41.960 I can't help that, but we want to get the word out 23:41.960 --> 23:43.480 when there are great implementations 23:43.480 --> 23:45.320 and people testing and playing with this code, 23:45.320 --> 23:46.920 because that's going to inspire someone else. 23:47.880 --> 23:51.000 The second thing we heard was we need more government engagement. 23:51.000 --> 23:53.480 And one of the reasons why I love the OpenWallet Foundation is we 23:53.480 --> 23:55.000 started with the Government Advisory Council. 23:55.000 --> 23:56.440 We've now created the OpenWallet Forum, 23:57.400 --> 24:00.200 but it's an joint organization with the UN's 24:00.200 --> 24:01.880 International Telecommunications Union, 24:02.760 --> 24:06.040 engaging government folks and standards development 24:06.040 --> 24:07.880 organizations and technologists. 24:07.880 --> 24:10.120 One of the things we saw was Estios. 24:10.120 --> 24:13.480 We're not talking folks were either not listening to Estios, 24:13.480 --> 24:15.240 or Estios weren't in the conversation, 24:15.240 --> 24:16.760 or technologists and governments were talking, 24:16.760 --> 24:18.040 but the Estios were over there, 24:18.040 --> 24:20.920 and we just kind of get everybody together and work this stuff out. 24:21.800 --> 24:23.880 And so it's starting with working groups and public meetings 24:23.880 --> 24:25.720 to collaborate on digital trust and global interrupt. 24:26.520 --> 24:28.360 So, lastly, it's an ECO system. 24:28.360 --> 24:31.240 We're here. We're at Boston, because we believe in the ECO system. 24:31.240 --> 24:34.040 If we were only doing OpenWallet Foundation projects eight, 24:34.040 --> 24:35.640 no one else would care and be, 24:35.640 --> 24:38.440 we would miss out on all the cool stuff that's happening in this space. 24:39.560 --> 24:41.160 But a couple of things to pay attention to. 24:41.160 --> 24:42.840 We do OpenWallet Foundation meetings, 24:42.840 --> 24:44.600 AMAs and Meetups. 24:44.600 --> 24:46.840 We've done AMAs with OpenID Connect. 24:46.840 --> 24:49.720 We've done AMAs with the EUDI Wallet Initiative. 24:49.720 --> 24:51.160 Those are not open-wallet projects, 24:51.160 --> 24:53.080 but we believe it's important for our communities 24:53.080 --> 24:54.120 to see what these folks are doing. 24:55.240 --> 24:57.560 W3C is where I started out 24:58.440 --> 24:59.960 within the identity space. 24:59.960 --> 25:02.520 It was working on basically dids 25:02.520 --> 25:05.320 for a company called Evername, which contributed some products 25:05.320 --> 25:06.520 to the Linux Foundation. 25:07.400 --> 25:09.800 W3C, we're engaging constantly. 25:09.800 --> 25:11.000 We're going to go to some of their events. 25:11.000 --> 25:12.280 They're coming to some of ours. 25:12.280 --> 25:15.000 Feed days, which used to be Dutch blockchain coalition. 25:15.000 --> 25:16.280 We're doing some events with them. 25:17.240 --> 25:18.120 If you're in Europe, 25:18.840 --> 25:19.880 DICE digital identity, 25:19.880 --> 25:22.440 Unconference Europe, is happening the first week of March. 25:22.440 --> 25:23.320 It's a great event. 25:23.320 --> 25:24.360 It's put on by the same folks. 25:24.360 --> 25:25.880 They do Internet Identity Workshop, 25:25.880 --> 25:27.480 which I mentioned two bullets above. 25:28.280 --> 25:29.480 IW is awesome. 25:29.480 --> 25:30.600 I've been going for years. 25:31.240 --> 25:32.360 Great event to go to. 25:32.360 --> 25:33.560 And then we're here at Boston. 25:33.560 --> 25:34.760 We hope this is our first. 25:34.760 --> 25:35.720 Well, this is our first. 25:35.720 --> 25:36.840 We hope this is not our last. 25:36.840 --> 25:37.960 We're going to be coming back every year. 25:38.680 --> 25:40.040 We think this community is that important, 25:40.040 --> 25:44.200 but also we need the feedback from folks in this room 25:44.200 --> 25:46.280 and folks outside of this room to make our own work better. 25:47.880 --> 25:49.000 And then, get involved. 25:49.000 --> 25:50.200 Look at another QR code. 25:50.200 --> 25:51.000 Look at me. 25:51.000 --> 25:54.040 Basically, this goes to our participation page. 25:54.040 --> 25:56.440 I'll share the open-wall foundation you were on the second. 25:56.440 --> 25:57.560 We have a community calendar. 25:57.560 --> 25:58.840 It lists all of our meetings. 25:58.840 --> 26:00.200 We have a discord. 26:00.200 --> 26:02.280 I know I put the mailing list up there. 26:02.280 --> 26:03.880 I'm the only person who uses the mailing list. 26:05.080 --> 26:06.680 It's broken my heart over the years 26:06.680 --> 26:08.360 that no one uses mailing list anymore. 26:08.360 --> 26:11.560 When I worked at Mozilla, I got yelled at because I was like, 26:11.560 --> 26:12.760 everything goes on the list. 26:12.760 --> 26:13.720 Yeah, but I want to have a meeting. 26:13.720 --> 26:14.360 Put on the list. 26:14.360 --> 26:15.160 All right, I'll put on the list. 26:17.160 --> 26:17.960 I miss mailing list. 26:17.960 --> 26:18.600 That's fine. 26:18.600 --> 26:19.560 And both of our get-hubs. 26:19.560 --> 26:22.680 We have a separate get-hub for our growth and impact projects 26:22.680 --> 26:24.280 and another get-hub for labs. 26:24.280 --> 26:25.640 That's just how we organized it. 26:25.640 --> 26:28.680 We have get-hub enterprise, and that's how we did it. 26:28.680 --> 26:30.680 And now, with six minutes left, sorry, 26:30.680 --> 26:33.560 a broken and rule of having less ten minutes, any questions? 26:36.440 --> 26:37.160 How dare you? 26:37.160 --> 26:38.120 No, no clapping. 26:38.120 --> 26:38.920 Put that out. 26:38.920 --> 26:39.880 You clap for everybody else. 26:39.880 --> 26:40.760 You'll clap for me. 26:40.760 --> 26:42.600 Any questions? 26:42.600 --> 26:43.880 Wait, are you going to clap for no questions? 26:43.880 --> 26:45.160 Come on. 26:45.160 --> 26:46.280 Yes. 26:46.280 --> 26:47.320 Oh, yes. 26:47.320 --> 26:49.560 So, one of the things I wanted to say yesterday, 26:49.560 --> 26:52.680 you speak against some really great suggestions for books, 26:52.680 --> 26:55.480 resources, anything that you would recommend. 26:55.480 --> 26:58.840 From your experience, it's a good way to get up to speed rule, 26:58.840 --> 27:00.200 and stuff like this. 27:00.200 --> 27:03.080 Okay, this is going to be recorded, 27:03.080 --> 27:05.240 and I will write it down after the session. 27:05.240 --> 27:08.440 Germany and Phil Winley, he used to be the Chief Technology Officer, 27:08.440 --> 27:10.200 the State of Utah, he's a professor. 27:11.160 --> 27:12.520 One of my favorite people in the world, 27:12.520 --> 27:14.760 he's also one of the founders of Internet Identity Workshop. 27:14.760 --> 27:17.320 He's been working in this space for literal decades. 27:18.360 --> 27:20.760 Phil has written two books about digital identity. 27:20.760 --> 27:24.520 I believe with a Riley, and they're kind of like, 27:24.600 --> 27:27.320 I still open them up and check on something Phil said, 27:27.320 --> 27:29.560 years ago, in a previous version of one of his books. 27:29.560 --> 27:30.440 He's one of my favorites. 27:31.480 --> 27:35.080 There is a newsletter, and I'm going to probably mess this up, 27:35.080 --> 27:38.920 Identisphere, which is put on by a person named DataMiner, 27:38.920 --> 27:41.240 and by Khalia, who's known as Identity Woman. 27:42.280 --> 27:46.040 It is a male, it is an email newsletter, I open up every week. 27:46.920 --> 27:51.320 It is from all over the industry, it is critical of some things. 27:51.400 --> 27:53.400 It is celebrating other things. 27:53.400 --> 27:56.040 It's calling out, like, hey, there's an event happening over here. 27:56.040 --> 27:57.640 Somebody over here needs help with something. 27:58.200 --> 28:01.000 It is literally sort of the pulse of, 28:01.960 --> 28:04.280 I'm not going to say just the open source part of Identity, 28:04.280 --> 28:05.720 because they cover everything. 28:06.760 --> 28:09.480 But they are definitely on the front of, 28:10.440 --> 28:12.840 if something's happening, I usually find out about it there, 28:12.840 --> 28:14.520 unless my boss has called me and said, hey, 28:14.520 --> 28:15.320 do you hear about Pluton? 28:17.320 --> 28:19.560 Those are my two number one go-tos. 28:19.640 --> 28:21.800 I'll see if I can think of a couple of others. 28:21.800 --> 28:24.040 If you get a chance, go to dice, if you get a chance, 28:24.040 --> 28:28.200 go to, I mean, IWs in California, in April, and October every year. 28:28.200 --> 28:29.880 But if you ever get a chance, go to those, they're great. 28:30.520 --> 28:31.640 Anyone else? Yes. 28:32.600 --> 28:36.680 The projects that are in, like, growth, labs, growth, and impact. 28:36.680 --> 28:37.320 Yes. 28:37.320 --> 28:41.320 Is there a sort of stable, monochrophane of those? 28:41.320 --> 28:43.800 I mean, as in, we reach the stable, 28:44.760 --> 28:50.360 I would generally say, you can have stable code bases in growth, 28:51.000 --> 28:53.960 but they have not met all the criteria to move up to impact. 28:53.960 --> 28:55.560 So we have two, could go ahead. 28:55.560 --> 29:00.280 Yes, so impact is the most stable, most mature of them. 29:00.280 --> 29:01.800 It doesn't mean growth is immature. 29:01.800 --> 29:04.360 It means it's being used, but I'll give you an example. 29:04.360 --> 29:06.520 Credo, the team working with the Republic of Ireland, 29:06.520 --> 29:09.480 they said in their annual review, like, hey, we're getting ready to apply, 29:09.480 --> 29:13.560 in this year, 2025, we're getting ready to apply for impact. 29:13.800 --> 29:15.080 Now, there are things they have to do. 29:15.080 --> 29:17.720 And they're going through the checklist to make sure they've met all those criteria. 29:18.840 --> 29:20.040 Anyone else, any other questions? 29:23.160 --> 29:27.960 All right. Next up, we've got utilizing UDI walletico systems 29:27.960 --> 29:30.200 in your legacy systems with the net company team. 29:30.200 --> 29:34.360 If I could get you to come on up, and thank you, everyone, for joining us.