KERI
Also called Key Event Receipt Infrastructure, autonomic identifiers, AID
KERI is an approach to decentralized identifiers that deliberately does not use a blockchain. Key state lives in a hash-chained log of key events, and trust comes from witnesses who receipt those events.
The argument it makes
Anchoring an identifier to a ledger means the identifier inherits the ledger: its governance, its availability, its economics, its longevity. KERI's position is that identity does not need consensus about ordering, only agreement about key state, and that a witnessed log delivers that more cheaply and with fewer dependencies.
The counter-argument
Witnesses are infrastructure too. Someone runs them, someone chooses them, and a verifier still has to decide which receipts to accept. The question is not whether a dependency exists but which dependency you would rather have and who controls it.
Where Solidus sits
On the other side of that argument, by design. did:solidus is chain-anchored, which buys a single ordered history anyone can check and costs exactly what KERI says it costs. Stating the trade honestly is more useful than claiming there is none.
Where it comes from
Someone else specified this. Solidus assembles it.
Originated by Samuel Smith, developed in the ToIP Foundation and KERI community, with IETF drafts that have not become RFCs. Its defining claim is a ledgerless identifier: key state is established by a hash-chained log of key events, witnessed and receipted, rather than anchored to a blockchain.
How to check this
Solidus has not built this. The entry explains the concept.
The specifications and reference implementations are public. Solidus implements did:solidus, which is chain-anchored by design, so the absence here follows from an architectural choice rather than from an unfinished feature.