Skip to content

Conversation

tnull
Copy link
Collaborator

@tnull tnull commented Oct 13, 2025

  • We fix an oversight introduced in 9977903 where we switched Cargo.toml to use local dependencies instead of pointing to an appropriate upstream commit
  • We account for Splicing-related events
  • We account for KeysManager taking a new flag for v2-payment-key derivation.

@tnull tnull requested a review from joostjager October 13, 2025 08:13
@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Oct 13, 2025

👋 Thanks for assigning @joostjager as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

- We fix an oversight introduced in 9977903
  where we switched `Cargo.toml` to use local dependencies instead of
  pointing to an appropriate upstream commit
- We account for Splicing-related events
- We account for `KeysManager` taking a new flag for v2-payment-key
  derivation.
@tnull tnull force-pushed the 2025-10-bump-to-latest-LDK-splicing branch from ef393bf to 2276157 Compare October 13, 2025 08:15
LdkEvent::SplicePending { .. } => {
debug_assert!(
false,
"We currently don't support splicing, so this event should never be emitted."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to double check - no splicing api is exposed in ldk-node and therefore this should never happen? I don't know the api, but is it possible for the counterparty to initiate this and get us to move along?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there is a new reject_inbound_splices on UserConfig that defaults to true. So we'll have to manually opt into splicing support as part of the integration PR.

@tnull tnull merged commit 4cbd1bb into lightningdevkit:main Oct 13, 2025
8 of 15 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.

3 participants