Consensus on periodic duty may result in constant leader ordering

[corverroos]

Problem to be solved

Consensus on info_sync duty is triggered every epoch (32 slots). That means that any cluster size that is a divisor of 32 will have a constant leader order, i.e., the same peers will be leader for round 1 and then for round 2 and for round 3 in each instance.

Proposed solution

Change the naive leader function to something like this: https://github.com/protolambda/eth2-shuffle

Note that this is a breaking change...

[thomasheremans]

Breaking change