You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed native crash (SIGABRT) during stale channel monitor recovery. The CounterpartyCommitmentSecrets store was not reset when force-syncing the
monitor's update_id, causing provide_secret() to fail validation after
a few commitment round-trips. The failed update triggered a ChannelMonitorUpdateStatus mode mismatch panic in the ChannelManager.
Fix: reset the secrets store in force_set_latest_update_id so new secrets
build a fresh, consistent tree. (rust-lightning fork change)
Added set_accept_stale_channel_monitors builder API for one-time recovery when channel
monitors are stale compared to the channel manager (e.g., after migration overwrote newer
monitors with stale backup data). Defers chain sync and sends probes to heal monitors via
commitment round-trips.
Added BuildError::DangerousValue variant to distinguish stale channel monitor failures
from other ReadFailed causes, enabling precise app-side recovery logic.
Depends on patched rust-lightning fork (ovitrif/rust-lightning#0.2.2-accept-stale-monitors-v2).