Skip to content

Conversation

@joostjager
Copy link
Contributor

@joostjager joostjager commented Jan 13, 2026

This aligns ldk-server with ldk-node's own approach of tracking upstream main rather than releases.

Update to ldk-node git rev d1bbf978 which requires passing NodeEntropy
explicitly to the builder. Also adds handling for new NodeError variants
HrnParsingFailed and InvalidScriptPubKey.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Jan 13, 2026

👋 Thanks for assigning @benthecarman 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.

Copy link
Collaborator

@tnull tnull left a comment

Choose a reason for hiding this comment

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

Not opposed, though I'll leave it to Ben to decide.

It might become more complicated if Server would ever want to take a dependency on rust-lightning or bitcoin-payment-instructions directly, though we probably don't want to do that but rather use LDK Node's crate re-exports anyways.

Copy link
Collaborator

@benthecarman benthecarman left a comment

Choose a reason for hiding this comment

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

Yeah I don't imagine we will have any conflicts with deps, we should be able to get everything from ldk-node.

@benthecarman benthecarman merged commit 6b8c6af into main Jan 13, 2026
14 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.

5 participants