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
returnErr(ChannelError::Close("Peer sent a garbage channel_reestablish with secret key not matching the commitment height provided".to_owned()));
3825
3828
}
3826
3829
if msg.next_remote_commitment_number > INITIAL_COMMITMENT_NUMBER - self.cur_holder_commitment_transaction_number{
3827
-
returnErr(ChannelError::CloseDelayBroadcast(
3828
-
"We have fallen behind - we have received proof that if we broadcast remote is going to claim our funds - we can't do any automated broadcasting".to_owned()
log_and_panic!("We have fallen behind - we have received proof that if we broadcast our counterparty is going to claim all our funds.\n\
3837
+
This implies you have restarted with lost ChannelMonitor and ChannelManager state, the first of which is a violation of the LDK chain::Watch requirements.\n\
3838
+
More specifically, this means you have a bug in your implementation that can cause loss of funds, or you are running with an old backup, which is unsafe.\n\
3839
+
If you have restored from an old backup and wish to force-close channels and return to operation, you should start up, call\n\
3840
+
ChannelManager::force_close_without_broadcasting_txn on channel {} with counterparty {} or\n\
3841
+
ChannelManager::force_close_all_channels_without_broadcasting_txn, then reconnect to peer(s).\n\
3842
+
Note that due to a long-standing bug in lnd you may have to reach out to peers running lnd-based nodes to ask them to manually force-close channels\n\
3843
+
See https://github.com/lightningdevkit/rust-lightning/issues/1565 for more info.");
ChannelError::CloseDelayBroadcast(_) => {panic!("Wait is only generated on receipt of channel_reestablish, which is handled by try_chan_entry, we don't bother to support it here");}
0 commit comments