This thread highlights some of the challenges developers, educators, and users have in this space when explaining and understanding how different types of Lightning wallets work.
In the quest to provide either better UX or more sovereignty, certain tradeoffs are necessarily made. You can favor ease-of-use on one end and hide all the complex stuff from the user, or you can offer full control on the other end, but have to explain how channels, liquidity, and synchronization work. You can also opt for creative third ways that try to accommodate both, but also require a lot of explanation.
It’s not easy, and if it were, the perfect solution for everyone would already exist.
nostr:note1cdel0aqf4ns94z0d7z5mg5fh508v8zynah5l4r785utf4nr8su4qeg5elp
That post is hilarious. “Self custodial lightning isn’t hard.” And then this thread ensues 🤣
nostr:nevent1qqs08w63dy4v7d4whd4vhjytgc0vemp9092e0emnx8gcwmt67eqfaespr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet50jv3za
Please Login to reply.
Damn lolol
Custodial Lightning - more expensive than on chain and more complicated too!