Describe the bug
Current implementation regenerate the remove nonce for every incoming message.
This leads to:
1) waste CPU consumption
2) mismatched ID if the remote peer generate the nonce with a different mechanism
Expected behaviour
When a message is received from the network, the carried nonce should be used to calculate the BinaryID
Describe the bug Current implementation regenerate the remove nonce for every incoming message. This leads to: 1) waste CPU consumption 2) mismatched ID if the remote peer generate the nonce with a different mechanism
Expected behaviour When a message is received from the network, the carried nonce should be used to calculate the
BinaryID