Error: Error occurred during XX handshake: Error occurred while verifying signed payload: Peer ID doesn't match libp2p public key.

[ethereum1729]

Issue description

This error occurs often in the logs. Not quite sure what is the significance of this error, just to report it here.

Error logs

TRACE: Unable to dial peer QmRq....... Error:
    Error: Error occurred during XX handshake: Error occurred while verifying signed payload: Peer ID doesn't match libp2p public key.
        at Noise.performXXHandshake (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p-noise/dist/src/noise.js:186:19)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at async Noise.performHandshake (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p-noise/dist/src/noise.js:155:20)
        at async Noise.secureOutbound (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p-noise/dist/src/noise.js:80:27)
        at async Upgrader._encryptOutbound (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/src/upgrader.js:406:12)
        at async Upgrader.upgradeOutbound (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/src/upgrader.js:176:11)
        at async ClassIsWrapper.dial (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p-tcp/src/index.js:49:18)
        at async TransportManager.dial (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/src/transport-manager.js:111:14)
        at async /root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/src/dialer/dial-request.js:71:18
        at async /root/ot-node/6.0.0-beta.3.0.0/node_modules/p-some/index.js:53:19

[Valcyclovir]

I have the same error show up on all my nodes and it seems to be quite a critical error to half of my nodes. The ones that are strongly affected are unable to connect to any other nodes in the network, and therefore aren't able to submit any proofs / commit to any services. The others that manage to connect to a few nodes manage to function fine, but this error prevents them to connect to all possible nodes.

[NZT48]

This is not a critical error and it does not affect much of node functioning, it happens only after the restart of the node, but we have it in backlog to handle it.