The Anoma Protocol and its Design Process
summary
Anoma claims a minimalist, canonical protocol syntax that separates identity and resource formats from trust semantics so different communities pick consensus and crypto out of band. It implements content-addressed resources with predicates, labels, nonces and controllers, and composable identities (AND/OR/threshold) so users, chains and validator sets use the same protocol-level primitives. Local views hold histories, conflicts resolve via controllers or chosen consensus, and prototypes plus a spec are under active development.
AI-written summary · about
chapters (16)
- 0:00Anoma Protocol intro
- 0:28Scale invariance in systems
- 1:30Scale invariance for apps
- 2:11Heterogeneous trust assumptions
- 3:17Maximizing locality in trust
- 4:19Global identity and state spaces
- 5:45Composing identities for trust
- 7:52Cryptographic identities generalized
- 9:16State resources as units
- 12:51Local state views and histories
- 13:56Conflicts in composed identities
- 15:21Canonical syntax for models
- 16:23Global interaction with scale freedom
- 17:49Minimal syntax for flexibility
- 18:32Q&A: Who runs globally
- 20:20Q&A: Signature collisions
related talks
20mAnoma: The 3rd Gen of Protocols
30mBringing Privacy to Public Blockchain
02h 44mBlockchain consensus mechanisms
48mThe Accord Consensus Protocol, how to do ACID transactions at scale
22mOptimizing network topologies...
30mDHT, BFT, OMG: Know Your Building Blocks for Decentralized Applications
17mBuild Omnichain Programs
42mBeyond Blockchain: Convergent Consensus