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
Syncing.checkSync(keyManager, d, channelReestablish) match {
1706
-
caseres: SyncResult.LocalLateProven=>
1707
-
log.warning(s"counterparty proved that we have an outdated (revoked) local commitment!!! ourLocalCommitmentNumber=${res.ourLocalCommitmentNumber} theirRemoteCommitmentNumber=${res.theirRemoteCommitmentNumber}")
1708
-
// their data checks out, we indeed seem to be using an old revoked commitment, and must absolutely *NOT* publish it, because that would be a cheating attempt and they
1709
-
// would punish us by taking all the funds in the channel
1710
-
handleOutdatedCommitment(channelReestablish, d)
1711
-
caseres: Syncing.SyncResult.LocalLateUnproven=>
1712
-
log.warning(s"our local commitment is in sync, but counterparty says that they have a more recent remote commitment than the one we know of (they could be lying)!!! ourRemoteCommitmentNumber=${res.ourRemoteCommitmentNumber} theirCommitmentNumber=${res.theirLocalCommitmentNumber}")
1713
-
// there is no way to make sure that they are saying the truth, the best thing to do is ask them to publish their commitment right now
1714
-
// maybe they will publish their commitment, in that case we need to remember their commitment point in order to be able to claim our outputs
1715
-
// note that if they don't comply, we could publish our own commitment (it is not stale, otherwise we would be in the case above)
1716
-
handleOutdatedCommitment(channelReestablish, d)
1717
-
caseres: Syncing.SyncResult.RemoteLying=>
1718
-
// they are deliberately trying to fool us into thinking we have a late commitment
1719
-
log.warning(s"counterparty is lying about us having an outdated commitment!!! ourLocalCommitmentNumber=${res.ourLocalCommitmentNumber} theirRemoteCommitmentNumber=${res.theirRemoteCommitmentNumber}")
log.warning(s"counterparty proved that we have an outdated (revoked) local commitment!!! ourLocalCommitmentNumber=${res.ourLocalCommitmentNumber} theirRemoteCommitmentNumber=${res.theirRemoteCommitmentNumber}")
2275
+
// their data checks out, we indeed seem to be using an old revoked commitment, and must absolutely *NOT* publish it, because that would be a cheating attempt and they
2276
+
// would punish us by taking all the funds in the channel
2277
+
handleOutdatedCommitment(channelReestablish, d)
2278
+
caseres: Syncing.SyncResult.LocalLateUnproven=>
2279
+
log.warning(s"our local commitment is in sync, but counterparty says that they have a more recent remote commitment than the one we know of (they could be lying)!!! ourRemoteCommitmentNumber=${res.ourRemoteCommitmentNumber} theirCommitmentNumber=${res.theirLocalCommitmentNumber}")
2280
+
// there is no way to make sure that they are saying the truth, the best thing to do is ask them to publish their commitment right now
2281
+
// maybe they will publish their commitment, in that case we need to remember their commitment point in order to be able to claim our outputs
2282
+
// note that if they don't comply, we could publish our own commitment (it is not stale, otherwise we would be in the case above)
2283
+
handleOutdatedCommitment(channelReestablish, d)
2284
+
caseres: Syncing.SyncResult.RemoteLying=>
2285
+
// they are deliberately trying to fool us into thinking we have a late commitment
2286
+
log.warning(s"counterparty is lying about us having an outdated commitment!!! ourLocalCommitmentNumber=${res.ourLocalCommitmentNumber} theirRemoteCommitmentNumber=${res.theirRemoteCommitmentNumber}")
0 commit comments