Lightning node economics
summary
Running a Lightning node earns routing and channel-sale fees but is capital intensive and full of tail risks: on‑chain opens/closes and force close can wipe months of revenue when mempool fees spike, inbound liquidity costs money because inbound is someone else’s outbound, and atomic swaps or LSPs buy you liquidity at a price. Database corruption, hot‑wallet exposure, uptime demands and operational risk are hard to price. Only operators with steady flow, tolerance for variance, or enough volume to avoid third‑party fees justify self‑hosting; small users usually don’t.
AI-written summary · about
chapters (15)
- 0:00Lightning node economics
- 1:08Why run a node
- 3:55Earning from routing
- 5:21Selling channels as LSP
- 7:25Sovereignty and control
- 9:12End of altruism
- 9:57Hidden costs
- 12:44On-chain fees and force closes
- 13:28Cost of inbound liquidity
- 16:58Operational risks
- 19:05Nodes as hot wallets
- 21:14Scaling risks
- 22:39Market competition
- 24:50When running a node is worth it
- 27:19Final warnings and Q&A
related talks
01h 00mScaling Bitcoin Off-Chain
48mLightning Network Economics: Cost-Minimal Channels and their Implications for Network Structure
29mBitcoin: When Lightning Strikes
50mSecurity Aspects of Lightning Network Routing
26mInstitutional Lightning
29mRunning The Block Lightning Node
15mThe Lightning Network: Scaling Financial Services on Bitcoin
28mThe Path Forward For Lightning