f update panic string

Author: TheBlueMatt

lightning/src/ln/channel.rs

@@ -3833,12 +3833,14 @@ impl<Signer: Sign> Channel<Signer> {
 								panic!($err_msg, log_bytes!(self.channel_id), log_pubkey!(self.counterparty_node_id));
 							}
 						}
-						log_and_panic!("We have fallen behind - we have received proof that if we broadcast remote is going to claim all our funds.\n\
-							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\
-							More specifically, this means you have a bug in your implementation which can cause loss of funds, or you are running with an old backup, which is unsafe.\n\
+						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\
+							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\
+							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\
 							If you have restored from an old backup and wish to force-close channels and return to operation, you should start up, call\n\
 							ChannelManager::force_close_without_broadcasting_txn on channel {} with counterparty {} or\n\
-							ChannelManager::force_close_all_channels_without_broadcasting_txn, then reconnect to peer(s).");
+							ChannelManager::force_close_all_channels_without_broadcasting_txn, then reconnect to peer(s).\n\
+							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\
+							See https://github.com/lightningdevkit/rust-lightning/issues/1565 for more info.");
 					}
 				},
 				OptionalField::Absent => {}