notes: research/papers/kerione-keri-white-paper

This data as json

path title type status classification words body
research/papers/kerione-keri-white-paper Key Event Receipt Infrastructure (KERI) Design summary v0.1 — 2026-10-14: drafted by Claude from the PDF (v2.63); unread by Mark; marked partner on Mark's word 2026-10-21, paraphrase only partner 547 # Key Event Receipt Infrastructure (KERI) Design **Abstract.** The founding white paper for KERI (Key Event Receipt Infrastructure), now at version 2.63, presenting self-certifying autonomic identifiers, key pre-rotation, key event logs and witnessed receipts as a decentralized key management infrastructure and candidate trust spanning layer for the internet. It covers the theory, event semantics, operational modes, witness agreement, derivation codes and serialization in 142 pages, for readers who want the full design rationale. ## Summary The paper (KERI here stands for Key Event Receipt Infrastructure) starts from the observation that the Internet Protocol (IP) has no security layer, so authenticity must be added as an identity (identifier) system security overlay that binds controllers, identifiers and key pairs. It argues that administrative trust bases, such as the Domain Name System (DNS) and certificate authorities, make that binding only as strong as the administrator, and proposes instead a cryptographic root of trust in self-certifying identifiers. Sections 2 to 5 develop autonomic identifiers (AIDs), autonomic namespaces and the autonomic identity system, compare trust bases, and present KERI as a candidate trust spanning layer. Section 6 treats key management, naming rotation as the primary operation. Section 7 defines the components: qualified cryptographic material, events (inception, rotation, interaction, delegated forms), seals, key event logs (KELs), receipts and key event receipt logs (KERLs), and the roles of controller, witness, watcher, juror, judge and resolver. Section 9 explains pre-rotation: each establishment event commits to the digest of the next key set, so a compromise of exposed keys cannot undo the forward commitment; hashing the next keys is also presented as the basis of post-quantum protection (section 9.2). Sections 10 and 11 describe the direct (one-to-one) and indirect (one-to-any) replay modes and the witness agreement algorithm, named KAWA (KERI's Algorithm for Witness Agreement), with escrow, consensus and recovery. Later sections give event syntax, a state verification engine, derivation code tables, weighted threshold multi-signature and serialization, including JSON. The conclusion restates KERI as a decentralized key management infrastructure (DKMI) built on minimally sufficient means, event streaming in design, usable with but not requiring a distributed ledger, with reconfigurable thresholds, reconfigurable witness pools and delegation. ## Key terms autonomic identifier (AID), self-certifying identifier, key event log (KEL), key event receipt log (KERL), pre-rotation, witness, KAWA, direct and indirect mode, decentralized key management infrastructure (DKMI), ambient verifiability ## Claims and their evidence - Pre-rotation's forward commitment to unexposed keys cannot be undone by exploiting exposed keys (conclusion). [informative] - Hiding next keys behind a cryptographic digest gives pre-rotated keys protection from a quantum attack on public keys (section 9.2). [informative] - KAWA may be more performant and scalable than approaches that depend on a total ordering distributed consensus ledger (abstract). [informative] - KERI may employ a ledger but does not require one (conclusion). [informative] - The author states KERI is the only event-streaming capable system known to him with this combination of features (conclusion). [unverified] ## Related KERI White Paper Slide Deck; The Duplicity Game; Universal Identifier Theory with KERI; KERI's Strategy for Post Quantum Security; the KERI specification at the Trust Over IP (ToIP) Foundation. ## Provenance Drafted by Claude on 2026-10-14 from the PDF (v2.63, 2025-09-14), read through the abstract, introduction, full heading list, sections 9.1 and 9.2, and the conclusion. Not yet read by Mark.

Links from other tables