lightning
Here are 411 public repositories matching this topic...
-
Updated
Dec 1, 2020 - Python
I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.
Of course, piping is a solution, but not for development in Jupyter Notebook, for example.
-
Updated
Nov 27, 2020 - Python
Would be useful to have deleteinvoice RPC method (opposite to createinvoice) to be able to cleanup expired invoices
-
Updated
Jul 30, 2020 - JavaScript
-
Updated
Sep 6, 2020 - TypeScript
-
Updated
Nov 29, 2020 - Shell
-
Updated
Nov 25, 2020 - JavaScript
-
Updated
Nov 24, 2020 - JavaScript
-
Updated
Jan 2, 2018 - Swift
Description of the Issue
When an invoice has expired, Joule should not allow the 'Confirm' payment button to be clicked. It should be disabled, gray, and/or show 'Expired'.
Additionally, the Reject button is no longer appropriate after expiry. It should simply be replaced with a 'Close' button.
Steps to Reproduce
Create an invoice that expires, and then leave the payment dialog
-
Updated
Nov 18, 2020 - JavaScript
-
Updated
Dec 1, 2020 - TypeScript
-
Updated
Nov 13, 2020 - C
Some candidates for removal that could easily be re-implemented inside Spark:
-
superagent(only used for a simple HTTP GET request, can be replaced with the built-in http module) -
helmet(sets security headers) -
js-yaml(only used to format objects in a human-readable manner, we don't really need yaml) -
nanoid(secure random string generator) -
is-ip(few-liner depende
-
Updated
Nov 30, 2020 - PHP
-
Updated
Mar 30, 2020 - Python
-
Updated
Nov 27, 2020 - JavaScript
-
Updated
Nov 26, 2020 - Shell
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
Nov 23, 2020 - JavaScript
-
Updated
Mar 15, 2020 - TypeScript
This might be a good idea and sufficiently easy to implement.
Just leaving the suggestion here for the future.
-
Updated
Nov 30, 2020 - Shell
-
Updated
Dec 1, 2020 - Rust
Improve this page
Add a description, image, and links to the lightning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lightning topic, visit your repo's landing page and select "manage topics."
Background
When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.
In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the