sz status reports is_running: true even when LDK's chain sync is failing. During the 2026-04-23 testing window the LQWD Esplora endpoint was unreachable for ~6 minutes (DNS resolution failure); LDK logged repeated Sync of Lightning wallet failed errors but sz status showed no degradation.
Operator/agent monitoring sz status during this window saw a healthy-looking node while it was effectively offline for chain data.
Recommended fix — extend sz status with chain-sync health fields:
{
"is_running": true,
"esplora_healthy": true,
"last_successful_sync_age_seconds": 12,
"last_sync_error": null
}Populate from LDK's chain source state (or a thin wrapper that tracks the last successful Esplora call). Agents can then alert / retry / fall back when esplora_healthy: false.
Source: agent feedback from LQWDClaw v2 testing 2026-04-23, item #16. Severity: low (observability gap).
sz statusreportsis_running: trueeven when LDK's chain sync is failing. During the 2026-04-23 testing window the LQWD Esplora endpoint was unreachable for ~6 minutes (DNS resolution failure); LDK logged repeatedSync of Lightning wallet failederrors butsz statusshowed no degradation.Operator/agent monitoring
sz statusduring this window saw a healthy-looking node while it was effectively offline for chain data.Recommended fix — extend
sz statuswith chain-sync health fields:{ "is_running": true, "esplora_healthy": true, "last_successful_sync_age_seconds": 12, "last_sync_error": null }Populate from LDK's chain source state (or a thin wrapper that tracks the last successful Esplora call). Agents can then alert / retry / fall back when
esplora_healthy: false.Source: agent feedback from LQWDClaw v2 testing 2026-04-23, item #16. Severity: low (observability gap).