Added: Support for non-final onion messages hops to self#8862
Open
21M4TW wants to merge 1 commit intoElementsProject:masterfrom
Open
Added: Support for non-final onion messages hops to self#886221M4TW wants to merge 1 commit intoElementsProject:masterfrom
21M4TW wants to merge 1 commit intoElementsProject:masterfrom
Conversation
e27e1f4 to
609f3e2
Compare
609f3e2 to
22ab977
Compare
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
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.
onion_message_parse: Adding a loop to process non-final onion messages hops to self, such as when dummy hops are used for a node with no announced channel. This allows to fully verify these hops and to properly derive the last path key, which can then be used for signing invoices, such as when combined with #8853 . This will also be useful when generating invoices that contain blinded paths with multiple hops.
Important
26.04 FREEZE March 11th: Non-bugfix PRs not ready by this date will wait for 26.06.
RC1 is scheduled on March 23rd
The final release is scheduled for April 15th.
Checklist
Before submitting the PR, ensure the following tasks are completed. If an item is not applicable to your PR, please mark it as checked:
tools/lightning-downgrade