pull down to refresh
0 sats \ 4 replies \ @lnproxy 17 Dec 2022 \ parent \ on: Lightning @-address but for on-chain? bitcoin
haha, yeah but it's a pretty easy hoop if it already has to implement the logic to send the lnurl request. Plus, every onchain wallet should be able to do this.
Yes, every lightning wallet could easily add this support too.
For on chain-only wallets during the next 10 years, many are probably already doing HTTP requests and parsing returned JSON to fetch fiat exchange rates. So adding this on chain address payment support without having to parse LNURL-stuff at all should be easy.
Been using a long recommended lightning wallet for connecting to my own node over Tor sometimes and I would not wish that experience on beginners. For payments with low time preference, I still prefer on chain.
reply
parsing a bolt11 invoice is not hard, there's no reason an onchain wallet should not be able to do it.
reply
Okay, I looked at the Bolt 11 fallback option. Bech32 encoding with weird tag format should be okayish to parse.. but it would be nice to be able to have the lnbc1.. invoice blob directly in the initial
/.well-known/lnpay/-response and not have to do an additional request using the returned "callback"-URL.reply
Oh, I think I didn't understand you. Yeah, it would be nice to just be able to make a GET request to something like https://lnproxy.org/.well-known/bcurlp/support and get a fresh onchain donation address. I guess it could be part of the lnurl spec, it's kind of like auth, not really dependent on lightning but nice to have in the same spec so you can use one key.
reply