-
Notifications
You must be signed in to change notification settings - Fork 266
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Simplify trampoline test helpers (#2942)
We previously supported sending arbitrary trampoline payments in eclair, which added a bunch of complexity to many of our payment components. This was necessary because the first version of Phoenix was based on the eclair codebase. But Phoenix isn't based on eclair anymore and is now using https://github.com/acinq/lightning-kmp, which is the library that mobile wallets should use. Eclair is only meant to be used for server nodes that relay payments and have access to the full network graph, so it doesn't make sense ever to send trampoline payments (full source-routing will always be better). We thus refactor our trampoline client code to only be used for tests (to ensure that trampoline relay and trampoline receive are implemented correctly). We isolate the test payment lifecycle in a dedicated actor (`TrampolinePaymentLifecycle`) which simplifies other payment components (such as `PaymentInitiator`). This refactoring will make it easier to support the official version of trampoline while maintaining backwards-compatibility for older Phoenix wallets that use the non-official trampoline version.
- Loading branch information
Showing
19 changed files
with
413 additions
and
804 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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
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
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.