0 sats \ 2 replies \ @lnproxy 17 Dec 2022 \ parent \ on: Lightning @-address but for on-chain? bitcoin
parsing a bolt11 invoice is not hard, there's no reason an onchain wallet should not be able to do it.
write
preview
50 sats \ 1 reply \ @Lumor OP 17 Dec 2022
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
10 sats \ 0 replies \ @lnproxy 17 Dec 2022
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