-
Updated
Sep 19, 2020 - SCSS
payments
Here are 796 public repositories matching this topic...
-
Updated
Sep 30, 2020 - Java
-
Updated
Sep 30, 2020 - Python
-
Updated
Sep 30, 2020 - Objective-C
-
Updated
Sep 8, 2020 - JavaScript
Add something similar to the ActiveSubscriptionRequiredMixin mixin proposed by @ZachPerkitny in dj-stripe/dj-stripe#1091 (comment)
Ensure this is documented in the "Checking if a customer has a subscription" usage section and a mixins reference section of the docs
-
Updated
Sep 30, 2020 - JavaScript
Would be useful to have deleteinvoice RPC method (opposite to createinvoice) to be able to cleanup expired invoices
-
Updated
Aug 27, 2020 - JavaScript
-
Updated
Sep 30, 2020 - Shell
-
Updated
Sep 29, 2020 - JavaScript
-
Updated
Aug 15, 2020 - Python
-
Updated
Jul 26, 2020 - CoffeeScript
-
Updated
Aug 3, 2020 - Swift
-
Updated
Apr 21, 2020 - Elixir
Description
Muitos dos nossos PRs não tem nenhuma instrução de como testar a feature ou o bug fix que foi desenvolvido e existem diversas consequências por conta disso. Por isso, seria interessante adicionar a sessão "Como testar" no arquivo .github/PULL_REQUEST_TEMPLATE.md.
-
Updated
Sep 29, 2020 - JavaScript
-
Updated
Sep 14, 2020 - HTML
Improve this page
Add a description, image, and links to the payments topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the payments 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