blip-0060: trampoline payments to legacy Bolt11 invoices #60
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
[Trampoline routing](lightning/bolts#836) allows nodes to send payments with limited access to the network graph, by relying on trampoline nodes to compute the missing parts of the route. The BOLTs only specify how such payments can be made to recipients who either support the trampoline feature or use Bolt12 with a blinded path. This leaves a gap when paying legacy nodes that don't support any of those features. This bLIP provides a mechanism to pay such legacy invoices, by revealing some of the invoice data to the last trampoline node, who converts the trampoline payment to a standard payment.
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.
Trampoline routing allows nodes to send payments with limited access to the network graph, by relying on trampoline nodes to compute the missing parts of the route. The BOLTs only specify how such payments can be made to recipients who either support the trampoline feature or use Bolt12 with a blinded path. This leaves a gap when paying legacy nodes that don't support any of those features.
This bLIP provides a mechanism to pay such legacy invoices, by revealing some of the invoice data to the last trampoline node, who converts the trampoline payment to a standard payment.
@arik-so @joostjager as discussed during the last spec meeting, this is what we currently use to pay non-trampoline Bolt11 invoices.