The block issuing relies on an interval to issue validation blocks and thus might over-issue on a given slot

[alexsporn]

Right now we rely on the timed taskexecutor to properly tick at the correct interval (based on SlotDurationInSeconds and ValidationBlocksPerSlot). When the executor ticks we take time.Now() as the block issuing time.

If the validator issues more blocks than ValidationBlocksPerSlot it will get punished with negative mana and the account will get locked, thus blocking any future validation blocks from being broadcasted to the network.

Relying just on ticks might not be a good idea here. We should maybe also keep track of the amount of blocks issued per slot to avoid edge-cases where we could issue more blocks than we want.