Conversation
Provide a restricted recovery node that scans BIP84 and bounded v2 counterparty-closed scripts while connecting only to allowlisted peers. Keep recovery persistence isolated from ordinary node data and resume Bitcoin Core scans safely across restarts and shallow reorgs. Expose the flow through Rust and UniFFI. Use the published LDK recovery branch until the corresponding changes are available upstream. Co-Authored-By: HAL 9000
Exercise counterparty-close recovery using Esplora, Electrum, RPC, and REST. Require recovered funds to become spendable and remain available after restarting from persisted recovery state. Co-Authored-By: HAL 9000
|
👋 Thanks for assigning @tankyleo as a reviewer! |
tnull
marked this pull request as draft
September 18, 2026 11:43
tankyleo
self-requested a review
September 18, 2026 18:35
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
2 participants
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.
Restoring a seed recovers wallet keys but does not reconstruct lost channel state. LDK Node currently lacks a dedicated recovery flow for discovering and sweeping eligible channel outputs after counterparties force-close, leaving users without a straightforward recovery path when node data is lost.
Add a restricted recovery mode, exposed through Rust and UniFFI, that connects only to allowlisted peers and scans for BIP84 wallet funds and bounded v2 counterparty-close outputs. Recovery uses isolated persistence, supports all chain backends, and safely resumes Bitcoin Core scans across restarts while handing discovered channel outputs to the sweeper.
Based on https://git.rust-bitcoin.org/lightningdevkit/rust-lightning/pulls/5009