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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
channeldb+invoices: add spontaneous AMP receiving + sending via SendToRoute #5108
channeldb+invoices: add spontaneous AMP receiving + sending via SendToRoute #5108
Changes from all commits
8fe4de8
82b4f11
135a0a9
c2729cb
438b03a
be66984
174d577
7bed359
7e2f5a1
3fb70dd
88b72ab
24d283e
6780f74
0b5be85
2a49b59
90a2550
ea934e1
cfa9e95
00581ef
352ce10
888af51
730b718
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this end up causing all the HTLCs w/ the same set ID to be cancelled back? If so this could be useful for probing using AMP as we can just repeat a share when we send things over, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would need to check (part of the TODO w/ adding more tests around invalid HTLC sets). as far as probing though, repeating the same share on a different HTLC won't hit this check since it's keyed by CircuitKey. we really shouldn't hit this check ever anyways, it is more of a sanity check to prevent us from making incorrect transitions at the db level.