notes: events/talks/kericonf26-d2-15-panel-what-keri-allows

This data as json

path title type status classification words body
events/talks/kericonf26-d2-15-panel-what-keri-allows Ryan Hansen (moderator): What KERI Allows Us to Do That We Couldn't Before (panel) (KERIConf 2026) summary v0.1 — 2026-10-15: drafted by Claude from the curated transcript; unread by Mark; marked partner on Mark's word 2026-10-21, paraphrase only, no quotation partner 838 # Ryan Hansen (moderator): What KERI Allows Us to Do That We Couldn't Before (panel) (KERIConf 2026) **Abstract.** The closing panel of KERIConf 2026, moderated by Ryan Hansen of the KERI Foundation, asked what KERI (Key Event Receipt Infrastructure) makes possible that was not possible before. The transcript names the panelists by first name: Alan (also spelled Allan), Thomas, Nico and Daniel. They discussed how each came to KERI, failed earlier approaches, partial implementations, takeaways from the conference and what still needs to be built. The session is for anyone wanting a broad view of where the community sees KERI heading. ## Summary **How the panelists arrived.** Hansen asked each panelist for their path to KERI. Alan said he believes everyone should be their own identity provider and sees no way to do that without KERI or something like it. Thomas, coming from blockchain, said his realization was that KERI offers what people value in blockchains without the drawbacks. Nico traced his path through the failure of Sovrin and the idea of microledgers, recalled recognizing Samuel Smith's white paper as the way to create identity at scale in a decentralized way, and said Key State Capital was founded for that reason. Daniel said that large telecommunications investments in complying with the STIR/SHAKEN caller authentication rules have barely improved the problem, and that he sees KERI as the way to solve it. **What has failed.** Nico described his earlier work on blockchain consensus systems; Thomas countered that KERI needs not consensus but convergence on the truth, since one honest watcher is enough to expose a liar. Thomas said attempts to treat identity like a token, locked into one chain, leave identity siloed and dependent on that network. Daniel criticized the European Union business wallet initiative for treating an organization as an opaque unit, and argued, in line with the vLEI (verifiable Legal Entity Identifier) model, that authority inside an organization must be traceable through delegation. Alan described identity theater: knowledge questions and repeated document checks that prove little. **Partial implementations.** Asked about the risks of KERI theater, Alan said an implementation should include as much of KERI as is needed to be secure and privacy-protecting, though adding it to legacy systems is fine. Thomas said a KERI light approach is too risky for identifiers of people or for government-scale systems, and saw it as a stage on a learning path. Daniel said he once proposed a KERI light posture in his own ecosystem and now regards that as a mistake at ecosystem level. **Takeaways and gaps.** Takeaways included shipping imperfect work, the need for better coordination and funding, the community's rapid growth, and the value of putting library maintainers in one room. Looking ahead, Daniel and Thomas named developer experience and troubleshooting as the biggest gap. Daniel hoped to see KERI verification on Google and Apple handsets in general release; Nico hoped for an ambient watcher network cache; Thomas hoped for wallet-to-agent discovery driven partly by SEDI (State-Endorsed Digital Identity). A participant asked what should happen when a watcher detects duplicity on a public official's key; the answer offered was a local watcher in the wallet and a wizard that proposes one safe action, such as rotation. Daniel also asked for post-quantum support with the Falcon signature scheme, and a participant wished for a login-with-KERI button. **Closing statements.** The panelists thanked Samuel Smith. Thomas contrasted the W3C's standardized data model with the trust model he sees KERI standardizing. Daniel warned that AI agents are already disrupting community mailing lists and urged the community to solve its own reputation and trust problem first. ## Key terms convergence, duplicity, watcher, KERI light, KERI theater, identity theater, delegated authority, five Ws, wizard, trust model ## Claims and their evidence - KERI does not need global consensus; one honest watcher is enough to reveal a controller presenting conflicting key states. [informative] - Daniel described a demonstration in which a Google handset verified KERI-based evidence, built and shown by Google but not yet in general distribution. [presenter-reported] - Daniel said he once proposed a KERI light posture for his ecosystem and now considers it a mistake at ecosystem level. [presenter-reported] - A wallet should run a local watcher that detects key state changes the controller did not make and offer recovery such as rotation. [informative] - Daniel reported that W3C mailing lists have had to shut down threads after AI agents began posting. [presenter-reported] ## Related The five Ws (wallet, witness, watcher, web, wizard), Veridian (Cardano Foundation), Key State Capital, Sovrin, the vLEI ecosystem, the EU business wallet initiative, STIR/SHAKEN, SEDI, the Falcon post-quantum signature scheme, the transfer registry primitive, Fergal's KERIConf 2026 session on troubleshooting, earlier KERIConf 2026 talks by Thomas and Alan. ## Provenance Drafted by Claude on 2026-10-15 from the curated transcript (d2-15-ryan-hansen-panel-what-keri-allows-us-to-do-that-we-couldnt-before.md), all minutes read (the transcript ends at about 33 minutes of the listed 37:30). Turns are not labeled by speaker in the transcript, so attribution follows the moderator's hand-offs. No quotations; paraphrase only. Not yet read by Mark.

Links from other tables