tss peers do not throw out the err when applying incorrect wiredMsg in keygen

[bnb-chain]

tss peers do not throw out the err when applying incorrect wiredMsg in keygen

[mungaij83]

This issue is affecting me as well. I can't move to round 2 if node x receives round 2 Message before round 1 message.

[notatestuser]

Hey @froyobin. As mentioned in the readme, in the transport layer sitting above tss-lib you should be using a 'session ID' in messages to differentiate the keygen sessions. The effect of this is that a message for a prior session should not even be able to reach tss-lib.

[froyobin]

@notatestuser Thank you for your reply, that make sense. I was thinking bout the scenario that the malicious nodes tamper the share and trying to send incorrect tss share to the victim with the session ID of this round.

[notatestuser]

@froyobin yeah. I think what you are looking for is covered in section 4.1 of the 2020 paper. The paper from 2018 that this lib implements does not provide identifiable aborts in keygen.

[froyobin]

@notatestuser Thank you. I will have a try with that one.