home / kskb / notes

notes: research/papers/cesr-proof-signatures

This data as json

path title type status classification words body
research/papers/cesr-proof-signatures CESR Proof Signatures: Partial Digital Signatures with KERI and ACDC summary v0.1 — 2026-10-14: drafted by Claude from the slides (Google Slides exported to PDF, 24 slides); unread by Mark; marked partner on Mark's word 2026-10-21, paraphrase only partner 500 # CESR Proof Signatures: Partial Digital Signatures with KERI and ACDC **Abstract.** A 24-slide Google Slides deck introducing CESR Proof Signatures, a specification for attaching digital signatures to nested portions of self-addressing data, with signatures that can be transposed across envelope boundaries. It recaps KERI, ACDC and CESR, then explains SAD path signature groups, transposition, the SAD Path Language and new code-table entries, and lists uses in KERI, ACDC and the vLEI. For implementers. ## Summary The deck sets out the background first. KERI (Key Event Receipt Infrastructure) is described as a framework for decentralized identifier systems whose key innovations are pre-rotation and threshold structures (multisignature, delegation, witnesses). ACDC (Authentic Chained Data Containers) is described as signed containers chained to dependent credentials, with compact schemas, provenance chaining and a rules section. CESR (Composable Event Streaming Representation) is described as a composable text and binary streaming encoding with table-based codes. CESR Proof Signatures are then defined as a specification for applying digital signatures to multiple nested portions of serialized name/value data. The slides list its properties: compatibility with KERI, ACDC and therefore the vLEI (verifiable Legal Entity Identifier); signing any self-addressing data (SAD) in JSON, CBOR, MessagePack or XML; multiple nested partial signatures; signatures transposable across envelope boundaries; and publication as an IETF draft in the ACDC specification family. The "How does it work" slides step through an ACDC example: start with self-addressing data, attach signatures, sign partial content by path, and nest signatures. A detour introduces KERI exchange messages. The transposition slides show how a signature attached to an inner payload is moved outward when that payload is embedded in an envelope, keeping it attributable. New attachment types are SAD path signature groups (several signatures on one path, either transferable indexed controller signatures or non-transferable witness receipt couples) and SAD path groups that collect them. The SAD Path Language is offered as an alternative to JSONPath or JSON Pointer, using '-' as its only reserved character and no wildcards. The last slides list additions to the CESR master code table and uses: nested partial signatures on ACDCs, embedding ACDCs in IPEX (Issuance and Presentation Exchange) messages, forwarding signed content through /fwd mailboxes, and a pilot signing GLEIF's xBRL annual report. ## Key terms CESR Proof Signatures, self-addressing data (SAD), SAD path, SAD Path Language, transposable signatures, nested partial signatures, signature group, IPEX, master code table ## Claims and their evidence - Signatures can be applied to nested portions of a serialized data structure and remain verifiable [informative] - Signatures can be transposed across envelope boundaries when content is embedded [informative] - The SAD Path Language avoids wildcards and uses one reserved character [informative] - The mechanism was used in a pilot signing GLEIF's xBRL annual report [presenter-reported] ## Related - ACDC specification repository - CESR specification - ACDC for Wizards (ACDC overview deck) ## Provenance Drafted by Claude on 2026-10-14 from the public Google Slides deck exported to PDF, all 24 slides read as text. Not yet read by Mark.

Links from other tables

  • 1 row from summary in resources
Powered by Datasette · Queries took 1.829ms