resources
1 row where summary = "research/papers/hardman-analysis-of-did-cel-heartbeat-relevance-to-keri" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date), date (date)
| id | type | name | url | maintainer | status | last_checked | date ▲ | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hardman-analysis-of-did-cel-heartbeat-relevance-to-keri | Papers and paper collections paper | Analysis of did:cel Heartbeat: Relevance to KERI | https://dhh1128.github.io/papers/heartbeat-and-witnesses.html | Daniel Hardman | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-12-20 | 2025 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A short 2025 analysis by Daniel Hardman of the heartbeat mechanism in the did:cel DID method, a periodic controller signature against retrograde (history-rewriting) attacks, and of whether KERI needs one. It concludes that KERI's pre-rotation and witness-based duplicity detection already cover the threat while allowing cold, offline keys. It is for readers comparing DID methods with KERI. | Daniel Hardman | 1.1 | Codecraft Papers (Daniel Hardman's paper archive) hardman-papers | Analysis of did:cel Heartbeat: Relevance to KERI research/papers/hardman-analysis-of-did-cel-heartbeat-relevance-to-keri | 1 | 1 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);