Shortcomings of the Lightning Network
1825 sats \ 20 comments \ @nout 7 May 2022 bitcoin
Here's a quick list of some of the issues with the current Lightning Network:
  • Not widely used standard for static codes (BOLT12 or AMP are not yet deployed, LNURL needs server with registered domain)
  • Privacy of hosted channels is not great (chaumian e-cash not yet released)
  • LN wallets on iPhone have hard time receiving when app is not open (Watchtowers not yet)
  • Many advanced features are commandline only (not in phone wallets)
  • QR codes UX is still annoying (LN not yet widely using NFC)
  • Onchain LN transactions take too much space (Taproot not yet used, Eltoo not yet released)
  • Punishment transactions are too strict (Eltoo not yet)
  • No way to "stabilize" lightning BTC balance to fiat rate (people have to use Tether :/)
  • Maintaining LN node & channels still requires manual work (no "single button" solution)
  • The lnd nodes are memory&disk heavy with more transactions (Eltoo not yet)
  • Payments are sometimes slow - especially for large amounts (mincut and graph flow algos from Pickhard et al have not kicked in yet, Tor is slow)
  • No good solution for inheritence is implemented (Onchain is also not good)
  • Not possible to use without internet (onchain is possible in person / over phone in crazy situations)
  • There's no easy way to do your own "accounting" across wallets (no standard protocol)
  • Web Apps don't have a simple way to integrate non-custodial wallets (possible, but complex UX)
The baseline Lightning Network works really well and most basic issues have been "resolved 18 months ago" 😉
That said I believe it's important to talk about the current problems and opportunities, so here's a start. Anything missing?
write
preview
related posts
136 sats \ 2 replies \ @DarthCoin 7 May 2022
Very good recap.
I could add some aspects more:
  • not very good algorithm for path finding, in special for MPP. On LND MPP, is not on by default (still depends on each wallet app), on CLN it is by default, but is taking same route, just splitting the amount in smaller parts.
  • not yet a method in the algorithm that detect the right balance of a channel. I am strongly agree with this tweet from ZFR
  • force closing channels still are a mistery, why they happen, in which conditions and why didn't happen when user really want it.
  • gossip propagation is not yet efficient and still buggy, sometimes, over Tor is terrible.
reply
36 sats \ 1 reply \ @nout OP 7 May 2022
Very good points too! I don't have that deep of understanding of the current routing implementations, but it feels like there's definitely opportunity for improvement.
reply
0 sats \ 0 replies \ @DarthCoin 7 May 2022
yes, exactly, we need improvements and I hope some LN devs will see your post and take notes.
reply
31 sats \ 0 replies \ @BlokchainB 8 May 2022
I’ll add two .
  1. If you recovered a failed node and you don’t have the channel backup you have zombie channels you can never close.
  2. A recovered node can’t change channel fees. Solution is to start fresh which is costly and erases the reputation you built for the node.
reply
8 sats \ 5 replies \ @notgeld 7 May 2022
LN wallets on iPhone have hard time receiving when app is not open (Watchtowers not yet)
Power management on end devices is not related to LN.
Watchtowers address absolutely different problem.
reply
2 sats \ 2 replies \ @notgeld 7 May 2022
No way to "stabilize" lightning BTC balance to fiat rate (people have to use Tether :/)
Not related to LN. And btw
standardsats.github.io
reply
0 sats \ 1 reply \ @nout OP 7 May 2022
I'm not sure how do you mean "Not related to LN"?
  • I'm talking specifically about lightning BTC balance, which is very LN related.
  • Also standardsats.github.io says "Lightning-native synthetic assets".
I agree that there are solutions in works (standardsats, Taro, RGB, Synonym, Liquid swaps), but it doesn't look like there's any usable version yet - or is there?
reply
0 sats \ 0 replies \ @notgeld 8 May 2022
At least because there very few ways to "stabilize" BTC balance onchain and none of them absolutely trustless due to oracle problem.
https://standardsats.github.io/ has "download APK" on its page. This is custodial tech, do not use it for savings. Currently only EUR asset available.
reply
0 sats \ 1 reply \ @nout OP 7 May 2022
I did not specify that one well. Indeed watchtowers are targeted for a different problem.
The fact that mobile wallet has to actively communicate with another node when receiving transaction is very much related to LN architecture and there could be either solutions on LN/application side or on the iOS power mgmt side...
reply
0 sats \ 0 replies \ @notgeld 8 May 2022
Also wrong.
There is IMMORTAN library written for SBW wallet around which makes everything possible for LN light client to work efficiently on mobile including augmented graph with Public Hosted Channels and trampoline routing.
The first BLW wallet actually had even Bitcoin SPV.
reply
31 sats \ 2 replies \ @arrowdrive 7 May 2022
All very good points but I wouldn’t say not having a way to “stabilize” a BTC balance is a shortcoming. Bitcoin is stable, it’s fiat that’s unstable. People need to stop thinking in fiat terms.
reply
122 sats \ 0 replies \ @nout OP 7 May 2022
Yeah, this is nuanced and for example people in US don't really have reasons to want it/need it. Also when everyone is on Bitcoin, then this won't be needed at all.
The main two cases I have in mind:
  • Someone operating business on low margins with a lot of money on the line. Volatility is the biggest enemy in this case, since the business can go bankrupt easily if the BTC value would swing down by e.g. 10% (and their counter parties denominate in fiat).
  • People in countries where local currency is rapidly inflating. Being able to switch to stable fiat is already massive improvement of experience and potentially human rights. It would be better if they switch to Bitcoin, but the stablecoin first step would imo provide a lot of value already.
reply
47 sats \ 0 replies \ @higuyslol 8 May 2022
I don’t think it’s worthwhile to pretend that BTC has a stable value.
The way I think about it is - fiat currencies like the dollar have optimized fulfilling as much of the total accessible market, as possible, making sacrifices on the soundness and hardness of the money.
Bitcoin on the other hand does the opposite (and it’s obviously much newer), where it maintains its hardness/soundness at the cost of a slower adoption (relative to fiat).
The instability of bitcoin come from the fact is that it’s significantly lower on the adoption curve, but it maintains excellent fundamentals. Fiat again, the opposite.
I guess the point I’m making is that it’s impossible to measure “stability” given both variables have different unstable properties. Let’s just be honest about it.
reply
21 sats \ 0 replies \ @faithandcredit 7 May 2022
For me i the delay between making a transaction and waiting for it to pop up in the wallet is always scary
reply
0 sats \ 0 replies \ @uco 12 May 2022
Great summary!
reply
0 sats \ 0 replies \ @EnormousPony 9 May 2022
Most of the issues seem to be related to the UI/UX land and I agree LN is still far from usable for the average user. We can make a comparison with 80s PC which where mostly for professionals and hobbyist. That being said if you want to help you have to choice 1) contribute to projects if you can 2) help them financially which is what I prefer to do for time/skill constraints. Sponsor projects on Github with some spare sats
reply
0 sats \ 2 replies \ @thrown 7 May 2022
Privacy of hosted channels is not great (chaumian e-cash not yet released)
The sad truth is that regarding privacy in a Chaumian mint, L1 is more private than Lightning…
By the way, you should group these into buckets: Solution(s) Known, Solution unknown
reply
0 sats \ 1 reply \ @nout OP 7 May 2022
Do you say that because the federation of the mint can see all the transactions? My understanding was that you can join the mint anonymously, no? In that case the mint federation is strictly smaller group than "everyone who has access to blockchain", so from the perspective of how many people can see what you do, this would be improvement.
That said I agree that it's not a clear cut and it really depends on what is your risk profile and who are you trying to be private or anonymous against.
reply
0 sats \ 0 replies \ @thrown 8 May 2022
I say that because when you’re using the chaumian mint to handle L1 transactions for you, it is using it’s own very private mechanism. When you are using it to handle Lightning for you, it is beholden to Lightning’s systems and quirks.
I suggest asking more to the developers behind Minimint. I can’t explain it super well, sorry.
reply
0 sats \ 0 replies \ @btcschellingpt 9 May 2022 freebie
Solid summary of where work and focus can build material results and progress
Also:
Payment routing still needs improved reliability (MPP coming) Recovery from node failure (LND) poorly defined and error prone (explore other impls)
Lightning today feels like what I suspect Bitcoin felt like in 2013-14 It's core function works just fine but it's not easy and has rough edges