Update trampoline to use official spec values #2819
Draft
Conversation
This file contains hidden or 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
|
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #2819 +/- ##
==========================================
- Coverage 85.79% 85.79% -0.01%
==========================================
Files 235 235
Lines 21261 21372 +111
Branches 847 904 +57
==========================================
+ Hits 18241 18336 +95
- Misses 3020 3036 +16
🚀 New features to boost your workflow:
|
t-bast
force-pushed
the
trampoline-spec-version
branch
from
ee178c7 to
bd76a24
Compare
t-bast
force-pushed
the
trampoline-spec-version
branch
from
bd76a24 to
d33f661
Compare
t-bast
force-pushed
the
trampoline-spec-version
branch
2 times, most recently
from
cd8e468 to
3f459d3
Compare
t-bast
force-pushed
the
trampoline-spec-version
branch
from
b781e95 to
3d5a8fe
Compare
t-bast
force-pushed
the
trampoline-spec-version
branch
6 times, most recently
from
90fb0c1 to
c333cd4
Compare
t-bast
force-pushed
the
trampoline-spec-version
branch
3 times, most recently
from
18dc4e1 to
d2ad160
Compare
We add support for the official version of trampoline payments, as specified in lightning/bolts#836. We keep supporting trampoline payments that use the legacy protocol to allow a smooth transition. We hardcode the legacy feature bit 149 in a few places to make this work, which is a bit hacky but simple and should be removed 6 months after releasing the official version. We also keep supporting payments from trampoline wallets to nodes that don't support trampoline: this is bad from a privacy standpoint, but will be fixed when recipients start supporting Bolt 12.
We add support for trampoline payments to blinded recipients, where each node of the blinded path is used as trampoline node. This is particularly useful to include custom TLVs from the payer to the recipient.
When returning trampoline failures for the payer (the creator of the trampoline onion), they must be encrypted using the sphinx shared secret of the trampoline onion. When relaying a trampoline payment, we re-wrap the (peeled) trampoline onion inside a payment onion: if we receive a failure for the outgoing payment, it can be either coming from before the next trampoline node or after them. If it's coming from before, we can decrypt that error using the shared secrets we created for the payment onion: depending on the error, we can then return our own error to the payer. If it's coming from after the next trampoline onion, it will be encrypted for the payer, so we cannot decrypt it. We must peel the shared secrets of our payment onion, and then re-encrypted with the shared secret of the incoming trampoline onion. This way only the payer will be able to decrypt the failure, which is relayed back through each intermediate trampoline node.
t-bast
force-pushed
the
trampoline-spec-version
branch
from
d2ad160 to
68d8aa2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the feature bit and tlvs defined in the official spec PR (lightning/bolts#836) and add support for:
We also add the official spec test vectors.
We keep backwards-compatibility for current wallet users relying on the legacy trampoline protocol, but will likely drop support at some point. We should notify the Electrum folks and give them enough time to migrate to the new protocol before dropping support for the legacy one.