pull down to refresh

21 sats \ 2 replies \ @nerd2ninja 24 Feb \ on: What challenges does the Lightning Network face in the future? AskSN
@supertestnet
nostr:nevent1qqswpfk3uxdu8qfzkhyl88rz4z6s465nepfpfwlpfa55vvza9d6k0pczyqsc8628tpyp6rcjf77e83tve2j9ulj5tnht34fgfrucy5l5j7uh2qcyqqqqqqgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgn5u2zv
UX problems with base layer payments include:
  • Mining fees are sometimes high
  • Confirmations usually take several minutes
  • Using it privately requires running a coinjoin server
UX problems with lightning payments include:
  • Setup fees are sometimes high
  • Payments frequently fail
  • Payments aren't asynchronous (the recipient has to stand there with their device open waiting to do a revoke_and_ack on their old state -- unless they use a custodian)
  • Payments that do succeed occasionally take more than 30 seconds (due to stuck payments, automatic retries, and no ability to say "stop retrying" in any existing wallets that I'm aware of)
  • Using it privately requires manual channel management
write
preview
21 sats \ 1 reply \ @nerd2ninja 24 Feb
This is honestly pretty surface level, but he goes on to talk about an issue the coinpool solves (soft forks allow for other solutions that do the same) like 10 users being able to pay for a $50 on-chain fee by paying just $5 each.
reply
0 sats \ 0 replies \ @Aardvark OP 24 Feb
Yea, I'm trying to steel man LN, but I keep running into solutions. 🤣
reply