-
Notifications
You must be signed in to change notification settings - Fork 1k
LSP-Plugin: Add MPP support #8948
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
Open
nepet
wants to merge
39
commits into
ElementsProject:master
Choose a base branch
from
nepet:plugins/lsps2/mpp-fsm
base: master
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.
Open
Changes from all commits
Commits
Show all changes
39 commits
Select commit
Hold shift + click to select a range
5bb5b20
plugins(lsps2): add session FSM for LSPS2 payment collection
nepet be17713
plugins(lsps2): add session actor with action executor boundary
nepet a99b066
plugins(lsps2): add session manager and unify HTLC handling
nepet 75d5157
plugins(lsps2): add integration tests for session lifecycle
nepet c71d0cd
plugins(lsps2): add restart recovery for session persistence
nepet 06924fd
plugins(lsps2): simplify DatastoreProvider to focused trait
nepet 00a4925
plugins(lsps2): add EventSink trait for session event notification
nepet 0d243fc
plugins(lsps2): decouple lsps2 crate from CLN-specific types
nepet 9e68cfd
plugins(lsps2): simplify actor and session manager
nepet b4c0a31
plugins(lsps2): make collect timeout dev config
nepet 36297f7
plugins(lsps2): route recovered sessions through forward_event path
nepet 7adf8ff
lsps2: adding list_finalized_sessions to the DatastoreProvider
bea0ae9
plugins(lsps2): fix onion failure codes sent when failing HTLCs
nepet f916634
plugins(lsps2): key HTLCs by (incoming channel, htlc id)
nepet 28ed3de
plugins(lsps2): forward replayed HTLCs to recovered sessions
nepet 793179d
plugins(lsps2): prevent double channel funding for one payment hash
nepet 493664f
plugins(lsps2): fail held HTLCs before cltv expiry, not after
nepet 599a847
plugins(lsps2): spawn only one channel-poll task per session
nepet 7182dcb
plugins(lsps2): harden recovery loop and fee-overflow handling
nepet 2515cf3
plugins(lsps2): advertise client_trusts_lsp and validate payment size…
nepet 9f098d2
plugins(lsps2): fix opening fee base and zero extra_fee TLV
nepet 2c8519d
plugins(lsps2): make channel reserve opt-in and pin datastore compat
nepet 1f476fc
plugins(lsps2): only abandon session once no forwarded parts remain
nepet 55aed02
plugins(lsps2): cleanups from review
nepet ac1791b
plugins(lsps2): make finalize_session idempotent
nepet 36df5e3
plugins(lsps2): only expire offers when starting a new session
nepet 1d2005f
plugins(lsps2): always release funding inputs when abandoning
nepet f3464a8
pytest: cover finalize_session over an existing finalized entry
nepet 683f792
docs: add experimental lsps options to config
nepet eefbb9c
plugins(lsps2): Add u16 zero len to TEMPORARY_CHANNEL_FAILURE
nepet d099586
tests: wait for mempool on lsps2 tests
nepet 6e498d6
tests: relax collect timeout on lsps2 plugin tests
nepet f96ae4d
tests: shorten long test name
nepet eae4b5b
plugins(lsps2): route parts by scid, not payment hash alone
nepet e1d2d81
plugins(lsps2): fund at most one channel per jit scid
nepet af9a571
plugins(lsps2): monitor recovered sessions for channel death
nepet b79a82b
plugins(lsps2): release the channel when recovery finds all forwards …
nepet 995c06e
plugins(lsps2): bound variable-amount payments by the policy size range
nepet b052087
tests: channel_ready wait is bounded
nepet 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 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
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
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
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
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
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.
Is there no way to identify a peer that is unable to set a zero-reserve and reply based on that, rather than setting the degraded mode as default, and asking users to configure an extra flag to get the desired default behavior? Also this means a node is either fully non-0-reserver or fully 0-reserve, no mixing possible.
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.
Please, do not amend this PR, create a new follow up one. experimental changes are not logged in the changelog anyway.