Security Aspects of Lightning Network Routing
summary
Lightning routing often leaves funds locked or payments stalled because intermediate hops time out or return useless failures; multi‑part payments and probing expose which channels fail but can themselves lock value. The work proposes embedding timestamps in onion messages, collecting per-hop outcomes into a reputation/penalty system, and using probabilistic path scoring to pick routes. A prototype stores observations, trains simple models from payment outcomes, and uses them to reduce wasted retries and improve routing efficiency compared with blind retries.
AI-written summary · about
chapters (9)
- 0:00Lightning Network routing security
- 3:29Payment failures and timeouts
- 7:23Malicious channel balancing
- 13:07Payment failure analysis
- 19:51Alternative routing strategies
- 24:53Timestamp debugging
- 30:14Reputation systems for nodes
- 37:00Probing network info
- 43:01Q&A
related talks
41mEverything I know about Routing Reliability and Liquidity on the Lightning Network
34mState of Lightning Privacy
21mHigh Throughput Cryptocurrency Routing in Payment Channel Networks
45mUnjamming Lightning
01h 03mLightning is Broken AF (But We Can Fix It)
29mLightning node economics
28mThe Path Forward For Lightning
09mLightning's (other) Toxic Waste Problem