f drop long-since stale comment that was the result of a 2017-era misunderstanding of the spec

Author: TheBlueMatt

lightning/src/ln/channel.rs

@@ -3535,10 +3535,6 @@ impl<Signer: Sign> Channel<Signer> {
 			false
 		};
 
-		//TODO: Note that this must be a duplicate of the previous commitment point they sent us,
-		//as otherwise we will have a commitment transaction that they can't revoke (well, kinda,
-		//they can by sending two revoke_and_acks back-to-back, but not really). This appears to be
-		//a protocol oversight, but I assume I'm just missing something.
 		if need_commitment_update {
 			if self.channel_state & (ChannelState::MonitorUpdateFailed as u32) == 0 {
 				let next_per_commitment_point = self.holder_signer.get_per_commitment_point(self.cur_holder_commitment_transaction_number, &self.secp_ctx);