Bitcoin Without Controversy
summary
Panel debates concrete failures and tradeoffs: a proposal for covenants stalled for years, CTV emulation already accounts for roughly one third of value in Taproot addresses, and last‑minute Taproot edits (33 vs 32 bytes) create real wallet complexity. Built things include checklocktimeverify and CLTV/CSV soft forks that work, while MuSig2 implementations trip on 32‑byte key edge cases and BLS would trade cryptographic assumptions for simpler wallets. Notes: anonymous criticism was published, activation clients were attempted, and cluster mempool aims to fix Lightning’s one parent one child edge cases.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:03Defining Bitcoin controversy
- 4:35Is controversy desirable
- 7:47Controversy for better outcomes
- 11:56Soft forks and controversy
- 17:55Consensus in Bitcoin changes
- 24:32Measuring proposal controversy
- 35:53Open source costs
- 42:13Easy vs hard improvements
- 48:32Controversial Bitcoin Core opinions
- 55:55Leadership in Bitcoin Core
- 1:01:15Constructive Bitcoin talks
- 1:06:33Q&A
related talks
28mWe're Not Breaking Bitcoin: The Case for CTV + CSFS
32mBitcoin in a Taproot World
56mEconomic and Social Risks Panel
23mRequiem for a Decentralized Bitcoin
38mWhat Features Does Bitcoin Need For Global Adoption?
22mThis One Math Trick Powers the Future of Lightning - PTLCs 101
25mCovenants make Bitcoin Better Money
50mScaling Bitcoin On-Chain