Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
feature: Lightning payment requests via BIP21/lightning prefix
See original GitHub issueWe could support paying to lightning invoices via BIP21 URIs using the &lightning= key or by using the lightning: prefix, see
https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.md#encoding-overview
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Payment request formats - Bitcoin Design
An introduction to the different bitcoin payment request formats. ... Most other lightning payment request formats build on top of invoices.
Read more >Sending and Receiving Bitcoin with Lightning - Cash App
Lightning ; To get started sending Bitcoin with the Lightning Network: Tap the Payments '$' tab on your Cash App to get to...
Read more >Understanding Lightning Invoices - Builder's Guide
Lightning invoices may be prefixed with lightning: to signal in hyperlinks which software can be used to pay the invoice. Ideally, in the...
Read more >LND Overview and Developer Guide
Developer resources and documentation for the Lightning Network Daemon. ... Lightning Network; Payment Channels ... Payment Requests; Payment flow.
Read more >Bitcoin's Lightning Network Could Be Getting a Privacy Upgrade
Receiving payments, requesting refunds, and opening and closing payment ... “BOLT 12 adds a ton of functionality to Lightning invoices.
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 Free
Top 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
Note: BOLT11 fallback addresses are currently being implemented in the branch named
seamless_lightning(warning: that branch includes a wallet db upgrade)
Feel free to have a look.
There are many ways to do it, with different implications and complexities. I think the easiest, is to call
parse_URIinsidemaybe_extract_bolt11_invoice. https://github.com/spesmilo/electrum/blob/3e42f2f33d56308455a5c75a460f2262c7a576bd/electrum/util.py#L1053 https://github.com/spesmilo/electrum/blob/3e42f2f33d56308455a5c75a460f2262c7a576bd/electrum/util.py#L938 This has the implication that if thelightningkey is set inside a bip21 URI, then we always use it, and in that case we disregard all the other fields in the bip21 URI.