IA-CCF: Individual Accountability for Permissioned Ledgers
Talkat 19th USENIX Symposium on Networked Systems Design and Implementation (NSDI '22) · 2022-04-04..04-06·
summary
A permissioned ledger implementation called IA-CCF signs and logs BFT protocol messages into the ledger and issues Merkle-tree receipts that clients can audit to expose replicas that sign contradictory statements; governance changes are tracked in a sub-ledger so receipt validators know valid signing keys. IA-CCF runs on Microsoft CCF with an LPBFT-style consensus, requires replicas to sign only one protocol message per batch, delivers receipts in two network round trips, and sustains about 47,000 tx/s in LAN tests (≈15k at 64 replicas).
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:59Individual Accountability
- 3:15IA-CCF and L-PBFT
- 3:49Sending a request
- 4:01Early execution: Primary replica
- 4:29Early execution: Backup replicas
- 4:56Agreement on execution
- 5:09Creating a receipt
- 5:28Committing the request
- 5:43Example: Misbehaving replicas
- 5:53Example: Banking transactions
- 6:34Auditing: Banking transaction
- 9:06Implementation
- 9:48Performance evaluation
- 10:11Throughput vs Latency (LAN)
- 11:12Scale-out (WAN)
- 12:04Performance of IA-CCF features
related talks
48mThe Accord Consensus Protocol, how to do ACID transactions at scale
34mThe Accord Consensus Protocol: ACID transactions globally at any scale
18mSmart Casual Verification of the Confidential Consortium Framework
01h 05mPBFT and Blockchains
19mCollective Authorities: Transparency & Decentralized Trust...
42mBeyond Blockchain: Convergent Consensus
01h 12mScaling distributed ledgers: Achieving arbitrary throughput and sub-second latency
35mAt the crossroad of Crypto and Security: A dev insider view