Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
With MPP and Trampoline (and particularly the combination of the two), we need to keep track of multiple amounts, recipients and fees. There's a trampoline fee and a fee to reach the first trampoline node. The trampoline nodes must appear in the route, but not as payment recipients. Adding new fields to payment events and DB structs lets us distinguish those. We also relax the spec requirement about feature graph dependencies. The requirement to include `var_onion_optin` in invoice feature bits was added after the first Phoenix release. Phoenix users will thus have non spec-compliant invoices in their payment history. We accept invoices that don't set this field; this is a harmless spec violation (as long as we set it in new invoices).
- Loading branch information
Showing
35 changed files
with
1,036 additions
and
535 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.