the previous logic where validateers had to announce their next block to be expected was too brittle and had no effective security benefit. All we need is:
only authorized enclaves may finalize
block numbers must increase monotonically
avoid forks
avoiding forks is still the naive solution: just finalize blocks from the first validateer appearing in the ShardStatus, which usually is the primary validateer who created the shard
closes #235
the previous logic where validateers had to announce their next block to be expected was too brittle and had no effective security benefit. All we need is:
avoiding forks is still the naive solution: just finalize blocks from the first validateer appearing in the ShardStatus, which usually is the primary validateer who created the shard