-
Notifications
You must be signed in to change notification settings - Fork 2
fix: delete vss network graph using new ffi client #775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: fix/node-stopping-bg-payments
Are you sure you want to change the base?
Conversation
82a5527 to
ba44df3
Compare
ba44df3 to
f120581
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3dfa34b to
e556b04
Compare
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
|
LGTM, testing ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't pay to Blink. tried amounts of 4000 and 500 sats
From the logs I can see the that the Blocktank node I have a channel with is missing but the others are present, that is why the channels was not reseted.
We should add another check if the connected peer is missing.
My peer id: 03816141f1dce7782ec32b66a300783b1d436b19777e7c686ed00115bd4b88ff4b
Closes #765
This PR:
Description
Builds on #740. The stale graph auto-recovery added in #765 attempted to deleted the graph from VSS using the app-level backup client but due to different key obfuscation namespacing in ldk-node, the graph backup was never deleted.
This PR switches to a dedicated LDK-specific FFI client implementation that points operations to the correct obfuscated file names backed up by ldk-node on VSS. This new VSS client implementation adjusted for supporting OPs on ldk-node backups is found in PR:
In practice this translate to successful LN payments to nodes that would otherwise fail, one example being payments to Blink wallet if having a stale graph in your wallet's VSS backups.
LDK-node already has the required mechanism to trigger redownload of the network graph if attempts to retrieve it from its backup on VSS fails. The cleanup mechanism is triggered when the graph is found to miss any of the expected trusted peers, which in turn triggers ldk-node to kick-off its re-download of the graph from the latest RGS server snapshot.
Preview
Test 1️⃣ - Payment to Blink
pay2blink.mp4
Test 2️⃣ - VSS app data preserved across
vss-rust-clientupdate0.4.0)0.5.5)QA Notes
Tip
No need to go all the way to replicate a stale graph on your VSS backup. To validate, simply test on mainnet some random LN payments to a couple wallets you have on other apps like Blink, Phoenix, WoS. If payments succeed, PR is good to be merged.
1. Verify stale graph reset clears VSS via FFI client
Network graph is stale, resetting and restarting...Cleared stale network graph from VSS (first delete)2. Verify VSS app data preserved across versions
master)