Misconceptions
Misconception: KERI Requires a Blockchain
KERI can use blockchains for discovery or anchoring, but its identifiers do not depend on shared-ledger consensus.
Misconception: "KERI is blockchain identity, so it must depend on a shared ledger."
KERI uses cryptographic event logs, receipts, witnesses, and watchers to make identifier state verifiable. A blockchain can be useful infrastructure around KERI, but the root of trust lives in the identifier and its Key Event Log (KEL), not in a validator network.
Summary
What the clips cover
- Samuel Smith - the ledger wars. Early SSI conversations often became arguments about which ledger should hold identity. KERI's insight is that portable identity should not be locked to one ledger.
- Samuel Smith - identity without blockchain. KERI was designed so decentralized identity can work without requiring blockchain consensus.
- Thomas Mayfield - blockchain hashchain comparison. KERI uses hash-chained data structures like blockchains do, but a KEL is per-identifier rather than one global shared ledger.
- Thomas Mayfield - off-chain identity. Blockchain integration can make sense for some use cases, but identity itself should remain off-chain.
Why it matters
Blockchains solve double spending for scarce digital assets. Most identity state changes need consistency and duplicity detection, not global ordering by a consensus network. That is why KERI can be decentralized, portable, and scalable without being tied to the blockchain trilemma.