Malice reports

[SurfingNerd]

Get HbbftMessageMemorium extended by:

Sealing Message

• Good - first 2f + 1 of the messages
• Late - Contributed, but with an older Epoch Number. The difference between current Epoch and Latest Epoch is tracked.
• Error - Did send message that could not be decrypted.

General Messages

• Good message
• Invalid Message

Contributions

• Good - did send a contribution.
• Invalid: A node did send contributions for transactions that is invalid - e.g. has been already included in previous block.

Bad Message Evidence

store evidence of bad messages

• config_bad_message_evidence_reporting Store evidence about bad sealing messages.

• - 0 means "do not store evidence", just track numbers.

• > 0 stores evidence at first on heap, later on it is stored on disk.

every node has the ability to report malice behavior of other nodes.

dependency: #94

[SurfingNerd]

we got all we need for the early epoch end connectivity reports, but we need to rewrite this to be block based anyways.