notes: research/papers/papers-keri-for-muggles

This data as json

path title type status classification words body
research/papers/papers-keri-for-muggles KERI for Muggles summary v0.1 — 2026-10-15: drafted by Claude from the PDF slide deck (all 52 slides); unread by Mark; marked partner on Mark's word 2026-10-21, paraphrase only partner 453 # KERI for Muggles **Abstract.** A 52-slide introductory deck for IIW (Internet Identity Workshop) #31, Day 1, Session #2, 20 October 2020, explaining KERI (Key Event Receipt Infrastructure) in seven plain-language steps. The deck names no author; its host says they volunteered to run the session, with Samuel M. Smith answering questions and Timothy Ruff giving background. For newcomers. ## Summary The deck presents KERI as a new approach to decentralized identifiers and decentralized key management for SSI (self-sovereign identity) and ToIP (Trust over IP) infrastructure, then being developed in the Identifiers and Discovery Working Group of DIF (the Decentralized Identity Foundation). The unnamed host says they learned it while helping Smith write a book chapter, and lays out the session format: background from Smith and Ruff (introduced as partners in Digital Trust Ventures), then seven concepts, each with a short explanation and questions for Smith. The seven concepts, each paired with a stated benefit: 1. Self-certifying identifiers: an identifier provably tied to a public key by cryptography alone, so control can be proven without relying on anyone else, including a blockchain. 2. Self-certifying key event logs: each key rotation is written as a signed message to a log, so control of new keys can be proven. 3. Witnesses: others may keep and sign copies of the log, adding evidence that the controller is not cheating. 4. Pre-rotation: the next key pair is committed to in advance and locked away, so it cannot be stolen from the current device; the deck calls this post-quantum proof. 5. System-independent validation: logs can be kept by any ledger, database, file system or device, so identifiers are not "ledger-locked". 6. Delegated identifiers: one identifier can create another that proves its relationship to the parent, allowing enterprise key hierarchies. 7. Compatibility with the GDPR (EU General Data Protection Regulation) "right to be forgotten": because KERI needs no immutable ledger, event logs can be deleted. It closes by pointing to the DIF working group and keri.one. ## Key terms self-certifying identifier, key event log, rotation, witness, pre-rotation, system-independent validation, delegation, ledger-locked ## Claims and their evidence - A KERI identifier's control can be proven without relying on any outside party, including a blockchain. [informative] - Pre-rotation protects against compromise of current keys and is post-quantum proof. [informative] - KERI infrastructure can be GDPR-compliant because it does not require immutable ledgers. [informative] - KERI was then being standardized at DIF's Identifiers and Discovery Working Group. [presenter-reported] ## Related Key Event Receipt Infrastructure (KERI) white paper; KERI specification; keri.one resources page. ## Provenance Drafted by Claude on 2026-10-15 from the PDF in Smith's Papers repository (exported from Google Slides), all 52 slides read as extracted text. Not yet read by Mark.

Links from other tables