0:00 Ryan Hansen Pannel ｜ What KERI allows us to do that we couldn't before ｜ KERI Conference 2026
0:04 Just really quickly as we get our
0:06 conversation just started, I wanted to
0:08 give a couple of quick ground rules.
0:10 First of all, some of my questions
0:13 might be fairly open and broad and
0:16 lead to some pretty long-winded
0:18 potentially long-winded answers. So just
0:20 be conscious of the time and the
0:21 respectful of everybody and make sure
0:24 we give everybody a chance to chime
0:26 in. Also, all the questions, even if
0:28 I direct maybe at one person, they're
0:30 all open to all of you. So, if you feel
0:31 like you want to say something about it,
0:32 by all means, jump in anytime. So, with
0:36 that, our the theme for this
0:38 conversation, this chat tonight is
0:41 in effect, what does KERI make
0:43 possible that isn't possible without
0:45 KERI? So, in that frame,
0:49 the first question I have is a little
0:51 bit of an existential question, I
0:53 guess. Why are you here?
0:57 And what I mean by that is kind of
0:59 what's the story again being respectful
1:01 of the time and all that. What's the
1:02 story that leads you to sitting in this
1:04 chair at this time? What's your aha
1:06 moment with KERI? What brought you to
1:08 this point? I'm going to just kind of
1:10 open this one up as a bit of an
1:11 introductory question for everybody.
1:14 Alan, I want to start with you. Well, I
1:16 guess I should start by saying that I
1:18 I genuinely believe that we should all
1:21 be our own identity providers and I
1:24 don't see how you can do that without
1:26 either KERI or something very similar
1:30 and that's why I'm here to see that
1:32 happen.
1:33 Great. And did you have a particular aha
1:34 moment with KERI when you fi founded
1:37 and or was it more of a gradual thing
1:38 for you or
1:39 it's been a gradual thing and a
1:42 continuing education by Sam
1:45 it's a it's a continuing process I can
1:48 tell you
1:49 that's good Thomas
1:53 I would have to say for me the aha
1:57 moment coming from the blockchain
1:59 space was realizing that what Sam has
2:03 invented is all of the things that we
2:08 value about blockchain
2:10 without the negatives.
2:14 Okay, cool. Yeah. And when did you
2:17 actually first get introduced to Sam or
2:19 to KERI in general?
2:21 It's it's going to be about four
2:22 years now.
2:23 Yeah.
2:23 Okay. It's been a while. All right,
2:25 Nico.
2:26 Yeah. So, you know, this kind of brings
2:28 me back to Sovereign, right? I was
2:32 introduced by Timothy Ruff
2:34 randomly messaging me on Twitter as a
2:37 pseudonmous account whether or not I
2:40 wanted to invest and the opportunity and
2:43 failure of sovereign was the exact
2:45 catalyst for what led me to KERI.
2:48 Obviously like the opportunity of
2:50 decentralized identity was massive and
2:53 not realized there. And I knew there
2:55 was something beyond a blockchain when I
2:58 was posting, I remember on the Telegram
3:01 of Sovereign about something like a
3:04 microleddger and Timothy actually
3:07 messaged me in a sideh show like who
3:08 told you about microledders? It's like
3:10 it's like no, I just came to it on my
3:12 own idea and we started talking about
3:15 the implications of what could be beyond
3:16 how do you scale a chain beyond this
3:18 sort of one chain to rule them all. And
3:20 then subsequently, you know, when
3:22 things are looking their bleakest
3:25 Sam comes out with the white paper and
3:27 Immediately it strikes me like, "Oh
3:30 my god, this is it. This is the endgame
3:32 of how identity needs to be created at
3:36 scale in a decentralized way." And I was
3:40 pleading for the rest of the sovereign
3:42 people to recognize what this was. And
3:45 no one else saw it. So we created
3:48 key state Capital to solve that problem.
3:55 I started working in the telco space only a few years ago and not very deep
4:00 Into it and I'm a little bit of an
4:02 outsider in those circles. But the
4:06 thing that was shocking to me is that
4:08 large companies have invested billions
4:11 maybe tens of billions is a better
4:13 estimate in complying with regulations
4:16 like from the FCC related to
4:19 shaken in the United States.
4:22 And after 10 billion dollars of
4:24 investment they haven't solved the
4:26 problem even a little bit. It's like
4:28 almost as bad as it was to start with.
4:30 The only way to solve the problem is
4:32 with KERI.
4:37 I agree.
4:39 I want to ask a little bit about you all come from it seems pretty different
4:44 problem spaces. Maybe there's some
4:46 overlap in some cases but what
4:49 solutions have you evaluated or seen
4:51 attempted to some of the problems that
4:53 you're particularly interested in?
4:56 What solutions
4:58 have you seen attempted and how
5:00 have they failed?
5:01 Now let's not get into vendor
5:03 bashing and stuff like that you know
5:05 we'll try to be nice as much as we can
5:08 but you know what have you seen as
5:10 failures and we'll go from there and
5:14 this is open to all of you so whoever
5:16 would like to jump in first I
5:18 I think for me I in particular when I
5:21 was working primarily in the blockchain
5:22 space was focused on consensus systems
5:25 So thinking about again how do you
5:27 scale recognition of an event
5:31 globally right and we went across many
5:34 different various obscure consensus
5:38 systems some that like are more than
5:40 proof of stake you have DAGs you have
5:42 parallel crystal streams it's it's it's
5:45 some crazy structures out there but I
5:49 think the bottom line is that you
5:51 need a system that is expressive enough
5:55 to if someone wants to define the limits
5:58 of consensus they can do so in such a
6:00 way that it can compose with another
6:04 consensus system because it all it is
6:05 governance right I'm going to push back
6:09 what
6:09 I'm going to push back I think with
6:12 KERI coming from the blockchain space
6:14 and consensus I think with KERI you
6:17 don't actually need consensus all you
6:19 need is one honest watcher to tell you
6:24 someone's lying.
6:25 I Wait, so hold on.
6:27 Well, maybe I misinterpreted what you
6:28 said.
6:28 No, no, no. I was leading there.
6:29 Okay. Okay.
6:30 Right. In the sense that like you don't
6:32 need consensus.
6:34 What you need is convergence.
6:37 Convergence on the truth.
6:39 To your question.
6:43 For me the failures that I have
6:46 seen in the decentralized identity space
6:49 is when the logic of digital identity
6:51 was applied to decentralization of
6:54 finance where
6:56 Blockchain networks tried to do the
7:00 same thing they did with a token with
7:01 your identity. then you end up just
7:03 locking an identity into another network
7:05 with varying actual decentralization
7:09 And relying on purchasing of a token
7:13 for that identity to work and then not
7:15 really being able to use it outside of
7:17 that ecosystem. So for me the
7:20 failures are trying to apply what we've
7:23 applied to decentralized finance to
7:25 identity and that just does not work.
7:28 And why not like give us a little more
7:30 detail on Well, well, because
7:32 effectively your identity is once again
7:34 siloed into a network. It's relying on a
7:37 token. It's also non-existent once
7:41 that network fails or that chain
7:43 crashes. And it has no meaning or
7:46 authenticity outside of that network.
7:48 So I need multiple identities
7:51 across multiple chains of multiple
7:53 tokens that have multiple levels of
7:56 security. it just isn't the right way to
7:58 go about decentralized identity.
8:01 I'd like to comment that one of the
8:04 failure modes that I see and that I'm
8:06 deeply concerned about right now is the
8:08 idea of business wallets.
8:10 I think this is one of the most
8:12 dangerous and worthless efforts
8:15 that the world has ever come up with.
8:18 That's strong words, but I think the
8:20 whole EU business wallet initiative is
8:23 destined for failure.
8:25 And part of the reason why is because
8:27 it's not respecting the first
8:30 principle which is you have to
8:32 have transparency. If you wrap a border
8:35 around an organization and say we're
8:38 going to think of everything inside this
8:40 organization as being atomic. We
8:43 can't decompose it in any way and we're
8:45 just going to say the organization
8:47 projects its identity outward and
8:50 everything inside of it is irrelevant.
8:53 you end up no matter what your key
8:56 management strategy is, no matter what
8:58 your credential formats are, whatever,
9:00 you end up in failure mode. And so in
9:02 some ways, this is a shout out to
9:05 Carla. I think the fundamental
9:07 principles of VLES
9:10 are deeply true. Those principles are
9:13 that an organization doesn't just have
9:15 authority because it exists. And people
9:18 who belong to an organization don't have
9:20 authority just because they belong to
9:21 the organization. They actually have
9:23 authority because they got delegated
9:25 authority from somewhere. And if you
9:27 can't track that down, you end up with a
9:30 massive failure mode for the whole
9:31 world.
9:34 Alan,
9:35 yeah, I see something that is a
9:37 continuing failure in the world
9:39 generally, which is something I call
9:42 identity theater. And I call
9:45 someone up and they say, "Oh, what's
9:47 your email address? What's your mailing
9:49 address?" They ask me a bunch of
9:51 questions that somehow are supposed to
9:53 prove that I am me. And I'll say, "So,
9:55 did that really prove that I am me?"
9:57 And they just laugh at the other end,
9:59 but they continuously do it. I went
10:01 through an airport the other day,
10:04 and they checked our passports five
10:07 times on the way through to the gate.
10:09 And
10:11 why
10:11 it's it's why it's it's just it's just
10:14 Security theater, identity theater,
10:16 whatever you want to call it, but it's
10:18 The SAD thing is that's
10:20 the that's the best that the business
10:22 world has at the moment. And they
10:26 seem to think it's okay.
10:29 Better things are coming.
10:32 Good. Okay. Speaking of theater, I'm
10:34 glad you brought that up because one
10:35 of the questions I wanted to ask and I'm
10:37 going to direct this specifically at
10:38 Thomas and Allan to start with just
10:41 because we heard your presentations
10:42 earlier today and both of you talked
10:44 about in different ways. Allan, you
10:46 mentioned kind of taking a bit of a
10:48 step-wise approach to getting KERI out
10:49 into the world and Thomas, you mentioned
10:52 a version of KERI maybe that's not
10:54 fully implemented as KERI as it is
10:57 defined. What do you see as the risks of
10:59 what you might call KERI theater where
11:01 where it's not fully KERI but that's
11:05 out there in the world but some form of
11:07 it? What do you see as potentially risk
11:09 that we need to be aware of in that sort
11:10 of situation?
11:18 I'll go first. I think it should be Really as much of caring as is
11:22 necessary to make it fully secure and
11:24 privacy protecting. but there's
11:29 nothing wrong with that being built into
11:32 existing legacy applications to add this
11:36 layer of trustability onto existing
11:39 transactions that are at risk.
11:43 So but no it really if it if it's
11:46 not as much care as is needed to
11:49 make it secure and safe then that's
11:52 not going to be good enough.
11:54 Yeah.
11:56 I would agree. I think there are
11:58 scenarios perhaps whereby
12:02 You can take on the risk of not using
12:05 all of KERI. The KERI light method
12:08 that I mentioned that the Swiss
12:10 government are using from my perspective
12:12 is actually where you shouldn't be
12:14 taking those risks because you're
12:16 dealing about with digital identifier
12:18 people. I also think that the KERI
12:23 Light approach is just
12:25 The byproduct of someone on their
12:28 journey through KERI. I was about to
12:30 say that
12:31 it's it's almost part of that learning
12:33 roadmap to some extent
12:37 from my perspective but I would I
12:39 would emphasize that for digital
12:41 identifier for humans for people for
12:45 governmentsized
12:47 systems
12:49 Anything but real full KERI with all
12:52 of the five W's is a risk.
12:57 Fair enough. Nico, you looked like you
12:58 had something to
12:59 Oh, no. He took everything I wanted to
13:01 say. How rude. That's great. Daniel,
13:05 anything to add here?
13:06 I once proposed a KERI light
13:09 posture in our ecosystem and
13:14 there's certain conditions under
13:17 which you could operate with
13:19 less than what KERI provides, but I
13:22 don't think they apply at an ecosystem
13:23 level. I think that was a mistake.
13:27 Okay, good. My next question,
13:32 what well,
13:34 I'm going to open this up a little more.
13:36 I was going to say one thing, but I'm
13:38 not going to limit it to one thing and
13:39 put too much of a boundary on it. What
13:41 what have you taken what will you take
13:43 away I guess from this conference
13:46 that either enhanced your understanding
13:49 of KERI will change the way maybe
13:51 you approach or describe KERI or
13:55 what are you taking away with you from
13:57 being involved in this conference for a
13:59 couple of days the first inaugural KERI
14:02 conference
14:10 I would say first and foremost If it's not perfect,
14:13 still put it out there. I mean, I think
14:16 the KERI Conference is a little bit of
14:17 a microcosm of that, right? It's our
14:21 first step at making a carryon only
14:23 conference. I think we did a great job
14:25 considering, but there's definitely ways
14:27 we can improve on it. There's definitely
14:29 ways that it can be expanded beyond
14:32 this. And the same thing with all
14:35 of the open threads that Sam's designs
14:39 has allowed us to pursue now this blue
14:41 sky of opportunities
14:44 that exists now in the world
14:47 because of this architecture.
14:49 The level of coordination and
14:52 communication that's necessary to
14:54 optimize our attention about what really
14:58 matters is one of the most important
15:01 choke points I think of our ecosystem.
15:05 That and money. So we need more money
15:09 too. So
15:10 indeed
15:17 I'm I'm going to take away how delighted I am that the KERI community is as
15:22 not only as big as it is but growing so
15:24 fast and that's must be very
15:28 encouraging for everybody here but
15:29 especially Sam because it's his baby
15:33 and it's it's getting to a
15:37 difficult teens age I think but It's
15:40 maturing nicely.
15:42 Yeah. And I'll just personally add on
15:44 to that I'm I've been super
15:45 impressed how deep so many of you
15:48 guys already are in KERI and
15:50 understanding of I feel like I'm I'm
15:52 certainly a little bit of imposttor
15:56 syndrome even sitting in this chair in
15:58 the position that I'm in. Anyway
16:01 Thomas, you want to
16:03 One of my takeaways from some of the
16:06 conversations that I've been privy to
16:09 and observed is there's there's almost a
16:12 need to take all of the technical
16:13 contributors
16:15 Behind the various libraries and
16:18 lock them in a room so that they can
16:20 have effectively a technical standup
16:25 and have these conversations because
16:27 I've seen just actually through the
16:28 hallways from one session to another
16:32 devs talking to each other and
16:34 finding a path to solve a problem that
16:36 they've been dealing with and that's
16:38 just happened walking from one room to
16:40 another so I think not only is KERI
16:44 conference important to talk about
16:46 the specifications to talk about the
16:49 opportunities where revenue streams may
16:52 exist and what everyone is building
16:54 but also give the devs that are
16:56 typically only engaging in an online
16:58 environment that opportunity to lock
16:59 them in the room. Maybe not lock them,
17:01 but stick them in the room and allow
17:03 them to have that same dialogue that
17:05 I've seen happen just between rooms with
17:07 a with a focus kind of agenda. I think
17:09 that'd be extremely productive.
17:12 I like that. Yeah. Daniel,
17:14 I'll just say that I'm super
17:16 excited about the is it five
17:19 engineers, Sam, that you've you've got
17:21 working on your five Ws or maybe it's
17:23 five W's but three engineers or four.
17:26 Anyway those five W's are really
17:29 awesome and I'm looking forward to it.
17:31 That's maybe one of the things that I'm
17:33 most jazzed about. Wait, also I didn't
17:35 get a chance to see the mobile wallet
17:37 yet.
17:38 You didn't?
17:38 No.
17:40 Where's Keanu?
17:42 Or no, Jay.
17:44 So, so I want to see that. But also, and
17:46 you'll arrange that
17:46 regrettably as well. With Sam's
17:50 crippled voice right now. It was
17:53 that's why we recorded all the sessions
17:55 so you can see all of them,
17:56 right?
17:58 And additionally, I mean, I think
18:01 the transfer registry primitive
18:04 that's going to unlock a lot of new
18:07 opportunities. It's very interesting.
18:09 I'm curious to see how that fits with
18:12 the rest of the stack.
18:14 Cool. Yeah. So the theme that as we
18:18 introduced it is what's possible now.
18:20 That wasn't possible before. And
18:22 let's flip that for a minute and talk
18:24 about and some of you or maybe all
18:27 of you have had a chance to talk about
18:28 this to some degree. So, let's maybe
18:30 unpack it a little bit more. What isn't
18:33 possible right now with KERI and what
18:36 needs what do we need to change to make
18:39 KERI possible? Let's start with Daniel
18:42 and move work our way down or anybody
18:45 else want to chime in if you if you
18:46 don't.
18:47 Well I'd like to see the
18:52 the developer experience be one where a
18:55 developer says I heard that KERI was
18:57 interesting. I'm eating a sandwich on
19:00 my lunch break.
19:01 I wrote a you know a KERI online or
19:04 I asked chat GPT and three minutes
19:07 later I have something that you know
19:09 plugs up end to end or whatever. That
19:13 to me feels like a utopia. We're
19:17 working hard on that. But it will be
19:20 a while because there's just so much to
19:22 learn and there's so many things you
19:24 have to glue together. And I remember
19:28 Back in 2017, I saw the first demo of
19:31 a wallet that showed a proof
19:37 request and a response
19:40 You know in decentralized identity
19:42 circles. And it was such a from the
19:44 outside it was a really boring demo. It
19:47 was like somebody holds up a wallet
19:49 and they click a couple of buttons and
19:51 then they get a green light and they
19:53 showed it. And I freaked out when I saw
19:55 it because I knew there were like 2700
19:58 things that had to be right for that
20:00 demo to work and that's kind of how I
20:03 feel today.
20:04 Nice. And maybe applying this to your
20:06 specific space like what still
20:08 needs to happen yet for KERI to be
20:12 fully realized there? Well, in telco,
20:14 the demo that I showed everybody
20:17 when I kind of showed a canned video
20:20 included Google you know, a Google
20:23 handset verifying something for
20:26 KERI. Google built that. They signed
20:28 it. They showed it at this
20:31 worldwide conference, but it's not in
20:34 general distribution yet. I would really
20:36 love to see that happen. And Apple, who
20:38 started working on it, I'd like to see
20:40 them finish what they started.
20:43 Nico.
20:44 Yeah, I it's kind of a specific one
20:46 actually. But I
20:49 really am looking forward to when
20:52 someone builds an ambient watcher
20:55 network cache
20:57 where you can just propagate key state
21:00 to there and then just repeat that
21:03 when that comes online and it's
21:05 sufficiently decorrelated I think the
21:09 network effects of KERI and the
21:12 possibilities of multiple Roots of Trust
21:14 and their credential sets interacting in
21:16 the combinatorial explosion, right? The
21:19 Cambrian the KERI explosion, right?
21:23 Is that's when the value proposition of
21:26 KERI really comes alive for me at least
21:28 in a theoretical sense. I don't know
21:30 there's so much that is possible to be
21:33 built with these data structures. It you
21:36 could talk about this all day. Please
21:38 continue.
21:45 Thomas, go ahead. I'd have to second what Daniel said. I think one of
21:48 the biggest risks is there's a snowball
21:52 effect happening with KERI and
21:53 developers are hearing about it. They're
21:55 going to explore the ecosystem and maybe
21:57 they're going to shy away because it's
21:59 not the most ideal developer friendly
22:02 experience, especially when it comes to
22:05 troubleshooting and tracing out errors
22:07 within your code. And I mean, Fergal
22:10 actually ran a whole session on this. So
22:12 there's there's there's that element
22:14 of the experience to the developer. I
22:18 mean I think a lot of us see that as
22:19 just a pain we have to deal with for the
22:21 time being but we understand that the
22:22 journey is worth it. Outside of that
22:26 for me I would also like to envision the
22:29 ability to download the wallet and for
22:33 there to be a gossip protocol that
22:36 allows me to just choose which agent I
22:39 want to connect to. I'd love to see
22:42 that level of adoption and the
22:44 infrastructure roll out and I think SEDI
22:46 is actually one of those initiatives
22:48 that will drive that type of
22:50 infrastructure roll out as well.
22:53 Well, there's a scenario that
22:57 may be solvable and may have an answer
23:00 that but I don't know what it is yet.
23:01 So, I'm going to put this out as a
23:03 question to everybody. So the
23:05 scenario was that the u the governor of
23:07 the state of Utah has himself a SEDI
23:11 credential and a watcher network
23:16 detects duplicity.
23:18 What happens next?
23:21 Impeached.
23:29 It's a good question. I'm looking for answers. We can't have
23:31 any political leader who says two
23:33 different contradictory things,
23:34 right?
23:35 That doesn't happen in politics.
23:41 Yeah. If anybody wants to try to throw an answer out there,
23:43 I think you stumped him, Alan.
23:45 His people will do a rotation for
23:55 Should we revoke or revert? Oh, no. Revise. Is it revise?
23:58 Actually,
24:01 it's a it is a bit more of a general
24:03 purpose question though where you have a
24:05 a regular human out there and
24:10 u some watcher network somewhere detects
24:13 duplicity on their key and this is
24:15 just some person who's going to inform
24:17 them what to do and
24:18 well you need to your wallet you should
24:20 have a local watcher that is informing
24:22 your wallet of any changes to your
24:25 key state that you didn't source And so
24:28 it can compare the two and see that your
24:31 witnesses don't agree with what you did.
24:33 And so it'll tell you, hey, there's bad
24:36 stuff just happened. What would you like
24:38 me to do about it? I can do a rotation,
24:40 repair it. Do you want to call? You
24:42 know, all of those are things are part
24:44 of the user experience that needs to be
24:46 developed to make it. That's what the
24:48 wizard in the five W's is for is to
24:51 figure out so that you can suggest to
24:53 people the right thing to do. One of the
24:54 things in critical physical security
24:56 that we had to figure out is that when
24:59 bad stuff is happening, the
25:03 security people that are monitoring the
25:05 cameras get overwhelmed very quickly.
25:08 And so you can't give them a menu of
25:10 options. You have to give them like one
25:12 button, press here, and then good stuff
25:15 happens. And so you have to figure out
25:18 what that press here does so that when
25:21 there's an emergency, they don't go,
25:23 "Crap, there's duplicity. My life just
25:26 ended." They need to be able to say,
25:29 "Oh, everything's okay." Right? So you
25:32 have to figure out. So you have to have
25:33 enough intelligence to be able to say,
25:35 "Okay." Right? And rotations are safe.
25:38 You can rotate a lot. It doesn't hurt
25:40 you to rotate. It's just friction. And
25:42 so you can try to reduce that
25:44 friction but make it so that it and you
25:47 know it's like that what's the worst
25:49 thing that can happen right you know is
25:52 that you rotate when you didn't need to
25:55 right but as long as you know I mean rot
25:58 rotation too much becomes a security
26:00 problem in and of itself but you can
26:02 manage that
26:03 but of course the pre-rotated key then
26:06 has to be stored somewhere else and so
26:09 yes that's why I said there's friction
26:11 there so you have you have to the
26:12 regular human.
26:14 Yeah. So, but that's why that's
26:16 why there's various things that we have
26:18 to work on to figure out all the
26:21 different friction points and figure out
26:22 how to solve those and it's
26:25 not those aren't trivial problems. So,
26:27 yes, it's it's it's a hard problem yet
26:29 to be solved.
26:30 Maybe the answer eventually is we all
26:32 have a little chip and that's where we
26:34 keep our pre-rotated key.
26:37 I want to throw in one other thing.
26:41 Go ahead.
26:47 Movie with Keano Reeves in it. That's a really dystopian view of putting stuff
26:49 in your brain.
26:52 I want to throw in one other thing I'm
26:53 really looking forward to that we can't
26:54 do today.
26:56 And that is I'm looking forward to
26:59 the postquantum support in KERI.
27:04 I want Falcon to be in. Part of
27:07 why I want it to be in is because I can
27:09 see the train wreck happening everywhere
27:11 else.
27:12 And I know that we have a great story,
27:16 but it will be even greater when the
27:17 train wreck starts to have casualties
27:19 everywhere else and we say, "Come on
27:21 over." I we're ready. I mean, it
27:26 would not be that hard to add it in.
27:29 So that's just a little bug in
27:32 everybody's ear. Let's let's get that in
27:34 quickly. Something that just occurred to
27:37 me that I would love to see is a login
27:39 with KERI button
27:42 just everywhere.
27:43 Wouldn't we all? Yeah. Get rid of get
27:45 rid of the login with Google and GitHub
27:47 and all the other stuff and right
27:49 login with KERI.
27:52 All right. I actually don't have any
27:54 further questions. I wanted to open up
27:56 maybe to the group to ask questions
27:58 of our illustrious panel here. those who
28:02 haven't had a chance to maybe ask
28:04 questions or hear from some of our
28:06 guests.
28:11 I guess not. I guess we've covered it all. We are coming to the end of or I
28:14 guess we are at the end of our
28:16 conference. We've had a chance to hear
28:19 from pretty much all of you at one point
28:20 or another and it's really been an
28:23 amazing experience. For me
28:25 personally, as a kind of new to the
28:27 KERI ecosystem, the KERI world,
28:30 it's it's really encouraging to see how
28:31 many other people have been thinking
28:33 about this for a long time and have been
28:36 working on this for a long time.
28:38 I've got a lot of catching up to do and
28:40 we're excited as a as a KERI Foundation
28:42 team to get in to start addressing
28:45 some of these problems that you guys
28:46 have brought up. So, in the last just
28:49 maybe few minutes, I'll give you guys
28:51 each a chance to kind of give your
28:52 closing statements and your last
28:54 little messages to the KERI Conference
28:56 are our first ever KERI Conference. No
29:00 time limit.
29:03 Dangerous.
29:04 Well, I'll go first by just saying
29:06 that all of the thanks goes to Sam
29:10 Smith. I mean, none of us would be here
29:13 without Sam. and I'm
29:18 looking forward to next year.
29:21 Indeed.
29:28 I think one thing that's kind of come up in
29:30 some conversations I've been having with
29:32 fellow colleagues
29:33 From the W3C space that I just
29:38 wanted to share is
29:41 There's been a lot of work there in
29:43 standardization and for me there was
29:45 kind of a moment that shifted across the
29:47 last couple of months where what I
29:51 what I can acknowledge from the W3 three
29:53 spaces they have standardized the data
29:56 model and that's been that's been useful
29:59 for a lot of development work but I
30:02 believe that what we standardized here
30:04 with KERI is the trust model and
30:08 from my perspective that is something
30:12 that for me is what's keeping me here
30:16 keeping the team working hard
30:20 and I look forward to continuing the
30:22 journey.
30:25 Yeah, just in the same way building
30:27 off of Allan's sentiment I just
30:30 want to thank you, Sam, and also
30:33 everyone else here who's put their
30:35 blood, sweat, tears, and time into this
30:39 protocol and into the people. You
30:42 all make it an absolute pleasure to be
30:45 on this stage with and to share in
30:48 this sort of co-creation of a what
30:51 I view as a beautiful new future.
30:54 And
30:56 it's a joy. It's a joy to be in this
30:59 space and I couldn't be happier. The
31:03 duplicity game is a foot.
31:11 I'll just say that I think we all need to protect our own identities and
31:13 reputations urgently.
31:16 If I were malicious I would,
31:20 Point AIS at a bunch of different
31:23 communities and have them wreak havoc.
31:25 Yeah.
31:26 And we have the tools to protect
31:28 ourselves, but we're not using them yet.
31:30 It would be great if we toolled up
31:32 GitHub so that you couldn't make a
31:34 contribution unless you could prove who
31:36 you were. It would be great if you
31:40 know our remote interactions were
31:42 protected and I'm seeing I don't know
31:45 how many of you are on the various W3C
31:47 mailing lists but they like us are
31:52 vulnerable to the assumption that
31:55 well-intentioned humans are the ones
31:57 that are going to show up and they're
32:00 having AIS show up in the you know in
32:04 the comment streams and the email
32:05 threads and so forth.
32:07 and they've shut those down. But
32:09 this is just going to get worse. And so
32:12 I think it might this is kind of a an
32:15 invitation or a shout out to people that
32:17 maybe it's time for us to solve our
32:21 own community's
32:23 Reputation and trust problem
32:26 before any havoc occurs.
32:30 And to the extent that's true for
32:33 our community, it's true for every other
32:34 community out there, too. So, the world
32:36 really needs what we have. Let's go give
32:39 it to them.
32:41 Well said. And a big thanks to our panel
32:44 today, our guests, and a big round of
32:46 applause for all our guys here.