fix: update LND4 IP and bump ldk-node to rc.26#798
Open
ben-kaufman wants to merge 8 commits intomasterfrom
Open
fix: update LND4 IP and bump ldk-node to rc.26#798ben-kaufman wants to merge 8 commits intomasterfrom
ben-kaufman wants to merge 8 commits intomasterfrom
Conversation
4 tasks
ovitrif
previously approved these changes
Feb 22, 2026
Collaborator
There was a problem hiding this comment.
utAck
To fix CI & local building, we need to swap ldk-node builds from Jitpack to GH packages, as we can't use jitpack anymore due to repo size growing over 500mb:
![]() |
|---|
I've prepared 2 PRs for ldk-node:
- fix: switch Kotlin publishing to GitHub Packages PR to rc.26 hotfix branch
- fix: switch Kotlin publishing to GitHub Packages PR to main branch
- define NodePeer data model to enrich known peers with names - use card UI for peers listed in node dev screen - show all node details regardless of dev mode on or off - extract node dev screen viewmodel
- define NodePeer data model to enrich known peers with names - use card UI for peers listed in node dev screen - show all node details regardless of dev mode on or off - extract node dev screen viewmodel - add padding between ldk debug screen peer input and buttons
Collaborator
|
Needs fix for ldk-node package source from: |
feat: peer cards with labels + use ldk-node from GH
ovitrif
approved these changes
Feb 23, 2026
piotr-iohk
approved these changes
Feb 23, 2026
Collaborator
piotr-iohk
left a comment
There was a problem hiding this comment.
Tested on mainnet wallet with inactive channels.
After installing this version channels are operational again.
(using unsigned mainnet build for sim)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

This PR:
34.65.186.40to34.65.153.174after the node migrationPeerStore::add_peersilently ignoring address updates for existing peersWithout the ldk-node fix, existing installs would keep retrying the stale cached IP indefinitely even after the app pushes the updated address via
Node::connect.Description
LND4's IP changed during a node migration. The hardcoded fallback address in Env is updated, and the ldk-node dependency is bumped to include the peer address upsert fix (synonymdev/ldk-node#53).
Preview
N/A — no UI changes.
QA Notes
34.65.153.174)Made with Cursor