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

Something based on https://docs.djangoproject.com/en/3.0/howto/upgrade-version/ would be a good idea.

• Review the change log for breaking changes
• Upgrade one feature release at a time (eg 2.2.x to 2.3.x)
• Test for deprecation warnings before/after each feature release
• Suggestion to run ./manage.py djstripe_sync_models after feature release in order to populate new fields - link to h

Would be useful to have deleteinvoice RPC method (opposite to createinvoice) to be able to cleanup expired invoices