What’s the deal with nostr:npub1ajlrwgfj4yerhqf7ady03h7wmtk2qr3gs7h3sxcx83k05yld36sswpzx3q and why does anyone like it?
I’ve personally seen two people in the past month attempt to pay a Lightning invoice with it and it failed both times. The worst part was it said the payment had completed on the sender’s side but the recipient never got paid. After the invoice expires, the sender eventually gets notified and the sats are returned to their wallet, but it can take 24 hours. Meanwhile, the merchant either loses a sale or the customer has to pay using another method while waiting for their automatic refund.
This is a frustrating experience both for retail customers and merchants, and it’s things like this that are going to kill Lightning adoption.
It uses Boltz Liquid<->LN swaps. It's essentially Muun except there is no unpredictable fee issues and/or subsidizing for turbo channels by being Liquid-first.
I think most issues will be around tiny LN payments not suitable for a Boltz swap or Boltz being unable to find a route to the receiver and this only being apparent to the sender (Aqua) after a while..
On that matter; nostr:nprofile1qqswe03hyye2jv3msylwkj8cml8d4m9qpc5g0tccrvrrcm86z0kcaggpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtc9xqxg6 y'all should add more boltz swap providers like https://swap.diamondhands.technology/ and compare rates, go with cheapest, or randomly if the same fee for better censorship resistance and reliability :)
If a Lightning payment doesn’t reach the receiver in a few seconds but it takes more than a few seconds (not to mention an hour or a day) for the funds to be returned and become spendable again, the entire process is broken and by extension it makes Lightning appear unusable.
Fair enough. The minimum time for the payment is ~1/2mins since Liquid blocks are generated every minute and whatever Boltz takes to find a route.
I'm not sure what the timeout is but I can't imagine it being very long, so probably not getting into hours.
The downsides of swaps vs native LN... but comes with no inbound liquidity, FCs, and channel management nonsense + being fully insulated from onchain fee spikes 🤷♂️
Actually from a quick test it looks like they don't even wait for a confirmation(?). My Aqua LN swap took less than 10 seconds.
The problem is the unpredictability. In my real-world tests involving Aqua wallet users who tried to pay a Lightning invoice in a retail environment, I saw more than one instance of the payment failing to reach the destination, but on the sender’s side it showed as completed.
This causes a huge headache for both the sender and receiver. In an in-person setting such as a restaurant or store, this means a customer awkwardly waiting for up to an hour before the invoice fully times out with no indication of what went wrong during this entire time. As far as the customer is concerned, their payment was completed and their wallet balance is reduced. As far as the merchant is concerned, no payment was received and they then have to decide what to do next.
You can imagine how this will not scale for a commercial setting. A merchant can’t just say, “You can pay with Lightning, but not that particular way, because it’s unreliable.” This is a potential adoption nightmare.
I know a guy who uses Aqua Wallet to accept bitcoin at his brewery. We haven't seen these issues.
Have you tried Bull Bitcoin's wallet yet? It's similar to Aqua, but you can get your zpub and add it to BTCpayServer.
