lnrpc: add wallet_synced field to GetInfoResponse

In this commit, we add a new `wallet_synced` boolean field to the
GetInfoResponse message. This field exposes the wallet's internal sync
state with the backing chain source, providing visibility into whether
the wallet has caught up to the current chain tip.

This is distinct from the existing `synced_to_chain` field, which
represents a composite sync state that also considers the router and
blockbeat dispatcher. The new field allows callers to distinguish
between wallet sync delays and other subsystem sync states.
This commit is contained in:
Slyghtning committed 2026-02-05 08:45:53 +01:00
1 parent 44c6cc5a1c
commit 3c22c3e7fa
3 files changed
+2478 -2458

No files matched your search

+2470 -2458
View File
File diff suppressed because it is too large. Load diff
+4
View File
@@ -2118,6 +2118,10 @@ message GetInfoResponse {
// Indicates whether final htlc resolutions are stored on disk.
bool store_final_htlc_resolutions = 22;
// Whether the wallet is fully synced to the best chain. This indicates the
// wallet's internal sync state with the backing chain source.
bool wallet_synced = 23;
}
message GetDebugInfoRequest {
+4
View File
@@ -5556,6 +5556,10 @@
"store_final_htlc_resolutions": {
"type": "boolean",
"description": "Indicates whether final htlc resolutions are stored on disk."
},
"wallet_synced": {
"type": "boolean",
"description": "Whether the wallet is fully synced to the best chain. This indicates the\nwallet's internal sync state with the backing chain source."
}
}
},