Lightning is Broken AF (But We Can Fix It)
summary
Lightning currently breaks on real-world constraints: devices must be online to receive and to avoid locking HTLC liquidity, single-use invoices block offline receive, and watchtowers can’t enforce HTLCs without leaking channel info. Practical fixes under development include onion messages for offline notifications, trampoline routing to let intermediaries retry payments, and PTLCs via adapter signatures (Taproot) for multi-use QR invoices. Chain issues need Bitcoin Core changes (package replacement RPC and tx version 3) and mempool/CPFP work; some pieces land now, others need years.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:27Always online requirement
- 8:07Async payments solutions
- 15:35Transaction pinning issues
- 27:11Routing complexity
- 34:52Privacy risks
- 49:19Channel jamming mitigation
- 51:21Q&A
related talks
50mSecurity Aspects of Lightning Network Routing
28mThe Path Forward For Lightning
34mState of Lightning Privacy
01h 00mScaling Bitcoin Off-Chain
29mBitcoin: When Lightning Strikes
22mThis One Math Trick Powers the Future of Lightning - PTLCs 101
23mRequiem for a Decentralized Bitcoin
45mUnjamming Lightning
