Solo machine must use misbehaviour provided timestamp

[colin-axner]

Summary of Bug

The solo machine uses the timestamp currently set in the consensus state to process misbehaviour. This is incorrect. Signatures signed at the same sequence but a different timestamp (anything greater than the consensus state timestamp) would fool the light client, but fail misbehaviour validation.

Solution

The timestamp needs to be a parameter provided in the misbehaviour for each signature.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned