Proofless Consensus & Client-side Validation
summary
Claim: validation moves entirely to clients while consensus only detects double spends by checking ephemeral pubkeys, reducing on-chain data to a tachygram tuple (old pubkey, new commitment) inscribed via a BitVM3 bridge using Argo garbling. Implementation uses recursive zero-knowledge proofs / proof-carrying data so each client verifies inclusion or non‑inclusion in constant time with constant-size proofs, suitable for light devices; prototype architecture exists but Sybil resistance and practical UX/backups remain open.
AI-written summary · about
chapters (8)
- 0:00Proof-less consensus & client-side validation
- 1:06Bitcoin needs private transactions
- 2:50Zcash recap: zero-knowledge proofs
- 6:22Moving proofs off-chain for client-side validation
- 8:33Recursive zero-knowledge proofs for history validation
- 13:57End-to-end architecture of shielded CSV on Bitcoin
- 17:07User flow: Alice to Bob in shielded CSV
- 24:38Summary and opening the floor for questions
related talks
42mBeyond Blockchain: Convergent Consensus
23mPerishable Proof of Transactions - New Consensus for Day to Day dApps
22mOptimizing network topologies...
30mStrengthening Reliable Decentralized Systems at Interchain
56mConsensus Through Herding
01h 11mDemystifying Bitcoin
31mSecure Distributed Storage
01h 04mConsensus with Asymmetric Trust
