resources

1 row where summary = "research/papers/why-anchored-signatures" sorted by date descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: last_checked (date)

level 1

year 0

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
kerione-why-anchored-signatures Papers and paper collections paper Why Anchored Signatures? https://dhh1128.github.io/papers/was.html Daniel Hardman no change in six to eighteen months; still correct quiet 2026-10-14     practitioner an author's paper, deck, tutorial or post explaining the suite informative anyone with the link public A short paper by Daniel Hardman explaining why a bare digital signature is weak evidence once a key may be stolen or rotated, and how anchoring each signing event in a tamper-evident record of key state closes the window for backdated forgeries. It uses KERI key event logs and transaction event logs as the worked solution. For practitioners designing evidence that must survive key rotation. Daniel Hardman             1.1 (item CC-PRI-250201)             keri.one KERI Resources page keri-one-resources Why Anchored Signatures? research/papers/why-anchored-signatures   1 1        

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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);