-
Notifications
You must be signed in to change notification settings - Fork 371
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
Support async ChannelMonitorUpdate
persist for claims against closed channels
#3414
Open
TheBlueMatt
wants to merge
7
commits into
lightningdevkit:main
Choose a base branch
from
TheBlueMatt:2024-09-async-persist-claiming-from-closed-chan
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+368
−270
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
140b76f
Always require a `PeerState` for the CP when claiming an HTLC
TheBlueMatt 94d0735
Set closed chan mon upd `update_id`s at creation not application
TheBlueMatt 3adbe07
Add an additional variant to `handle_new_monitor_update!`
TheBlueMatt 599e1ab
Support async `ChannelMonitorUpdate`s to closed chans at runtime
TheBlueMatt 6ae8047
Don't double-claim MPP payments that are pending on multiple chans
TheBlueMatt 10033b5
Support async `ChannelMonitorUpdate`s to closed chans at startup
TheBlueMatt cd65840
DRY the pre-startup `ChannelMonitorUpdate` handling
TheBlueMatt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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.
Oops, something went wrong.
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.
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.
For my understanding, does this PR make the duplicate-
PaymentForwarded
issue worse or is it the same as before?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.
Uhhh, if you're using async monitor updating maybe? It shouldn't change anything for non-async monitor update users, but of course for async monitor update users it should only change things (incl a new spurious event) in cases where what we did before was just unsafe.