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

Should be a nullable ForeignKey on Subscription.

https://stripe.com/docs/api/subscriptions/object#subscription_object-latest_invoice

Tentatively add to 2.2 milestone since it seems like it should be simple (potentially would hit a cyclic sync issue though, due to Invoice.subscription relation).

This should actually be made the default, because we use non-strict forwarding. We could make the method accept channelId, channelIds and nodeId.

See the spec recommendation:

Implementations using non-strict forwarding should consider applying the same fee schedule to all chann

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.