Handle cases where a remote node sent an unexpected echo message #23
Description
The remote node might have sent an echo message where the round did not expect any, or not sent one when one was expected. This should be a provable offense in both cases. Should we make the node sign a serialized Option<EchoBroadcast>?