Skip to content

LSPS4 Splice In#16

Merged
amackillop merged 6 commits intolsp-0.7.0from
feature/lsps4-splice-in
Apr 1, 2026
Merged

LSPS4 Splice In#16
amackillop merged 6 commits intolsp-0.7.0from
feature/lsps4-splice-in

Conversation

@amackillop
Copy link
Copy Markdown

Handle SpliceChannel events and wire lifecycle hooks

  • Plumb fee_estimator into LiquiditySource for splice UTXO selection
  • Add splice_channel_for_lsps4() helper mirroring Node::splice_in()
  • Add open_channel_for_lsps4() helper extracted from OpenChannel handler
  • Handle SpliceChannel event: try splice, fallback to create_channel
  • Wire SpliceFailed to reset LSPS4 liquidity cooldown
  • Wire ChannelClosed to clear LSPS4 liquidity cooldown
  • Switch to local path deps for cross-repo development

martinsaposnic and others added 6 commits March 23, 2026 13:08
- Plumb fee_estimator into LiquiditySource for splice UTXO selection
- Add splice_channel_for_lsps4() helper mirroring Node::splice_in()
- Add open_channel_for_lsps4() helper extracted from OpenChannel handler
- Handle SpliceChannel event: try splice, fallback to create_channel
- Wire SpliceFailed to reset LSPS4 liquidity cooldown
- Wire ChannelClosed to clear LSPS4 liquidity cooldown
- Switch to local path deps for cross-repo development
Switch from lsp-0.2.0 (55f7619) to feature/lsps4-splice-in (f6c56daa9)
which includes the LSPS4 splice-in support.
Update to afe7b5bb0 which includes splice unit tests.
When splice fails because the channel is reestablishing (not usable
yet), don't fall back to create_channel. The timer retries in ~1s
once reestablishment completes.
Splices are zero-conf anyway, so using unconfirmed inputs adds no
additional risk. Prevents splice failures when the LSP wallet has
unconfirmed change from a previous splice.
@amackillop amackillop merged commit f424a65 into lsp-0.7.0 Apr 1, 2026
6 of 34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants