resources
1 row where summary = "research/papers/where-trust-bottoms-out" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked (date)
type 1
level 1
access 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-where-trust-bottoms-out | Papers and paper collections paper | Where Trust Bottoms Out: X.509, Certificate Transparency, and KERI's DPKI Architecture | https://dhh1128.github.io/papers/wtbo.html | Daniel Hardman | changed within the last six months, or a live service active | 2026-10-14 | practitioner | an author's paper, deck, tutorial or post explaining the suite informative | anyone with the link public | A paper by Daniel Hardman comparing Public Key Infrastructure (PKI) with Certificate Transparency (CT) and the Key Event Receipt Infrastructure (KERI) as a decentralized PKI. It sets out what CT and KERI share, where their roots of trust differ, KERI's own tradeoffs, and how each would handle the transition to post-quantum cryptography. For practitioners who know X.509 and want to place KERI against it. | Daniel Hardman | 1.9 (item CC-COM-260327) | keri.one KERI Resources page keri-one-resources | Where Trust Bottoms Out: X.509, Certificate Transparency, and KERI's DPKI Architecture research/papers/where-trust-bottoms-out | 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);