f comment

Author: TheBlueMatt

lightning/src/ln/channelmanager.rs

@@ -817,7 +817,7 @@ macro_rules! handle_chan_restoration_locked {
 				// funding_locked if there have been no commitment updates, so the only channel
 				// monitor update which could also be associated with a funding_locked would be
 				// the funding_created/funding_signed monitor update. That monitor update failing
-				// implies that we won't send funding_locked until its been updated, so we can't
+				// implies that we won't send funding_locked until it's been updated, so we can't
 				// have a funding_locked and a monitor update here (so we don't bother to handle it
 				// correctly below).
 				assert!($funding_locked.is_none());
@@ -828,6 +828,9 @@ macro_rules! handle_chan_restoration_locked {
 			}
 
 			if let Some(msg) = $funding_locked {
+				// Similar to the above, this implies that we're letting the funding_locked fly
+				// before it should be allowed to.
+				assert!(chanmon_update.is_none());
 				$channel_state.pending_msg_events.push(events::MessageSendEvent::SendFundingLocked {
 					node_id: counterparty_node_id,
 					msg,