LNURL does not work with c-lightning v0.11.0
See original GitHub issueWhen attempting to pay a LNURL invoice using Phoenix, BTCPay displays a QR code, Phoenix will scan it and show the amount, but attempting pay fails.
In the server log I see the following 400 error:
BTC/lnurl/pay/i/Jk5Sfw1M...?amount=29000
When I check the URL in a browser:
{"status":"ERROR","reason":"Lightning node could not generate invoice with description hash"}
I don’t (fully) understand how LNURL works, but I suspect that you need to use the new deschashonly
option for c-lighting (added in https://github.com/btcpayserver/btcpayserver/pull/3559).
See also https://github.com/btcpayserver/btcpayserver/pull/3559#issuecomment-1118829186
Issue Analytics
- State:
- Created a year ago
- Comments:25 (9 by maintainers)
Top Results From Across the Web
lnurl | Yarn - Package Manager
Node.js implementation of lnurl. The purpose of this project is to provide an easy and flexible lnurl server that you can run as...
Read more >libwallet
KeyEncrypt encrypts an HD priv key using a user-provided secret into a string We use SCrypt256 for key derivation and AES-CBC-PKCS7 for ...
Read more >ZEUS (@ZeusLN) / X
No problem. Zeus lets you save connection info for multiple nodes and jump between them with ease. LND, Core Lightning, and Eclair supported....
Read more >BlueWallet (@bluewalletio) / X
No Elon, non-custodial an open source. Just software running on your phone. ... Lightweight lightning node for React Native. Contribute to BlueWallet/rn-ldk ...
Read more >Why doesn't c-lightning allow you to open multiple ...
The temporary_channel_id is unique only within a single connection hence implying the possibility of multiple channels per peer/connection. As ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pavlenex glad you were able to reproduce! Yes, I did have that 3rd option selected. I initially found out while trying a lightning address, but it also happens when I manually create a LNURL invoice.
I did not dare to downgrade my production c-lightning node. I’m reckless, but there’s limits 😃
The problem was that my manual code for detecting the chain for each invoice was missing signet and was treating it as mainnet (default case).
Solved by skipping the LND
*chaincfg.Params
premade stuff and just passing the code manually.