Assuming the set of validateers is unpermissioned, we still want to limit the number of active validateers because there is no benefit in higher distribution - but some disadvantages:
confirmation time goes up (until we have TOP pool gossiping)
networking overhead increases
risk of forks increases in certain scenarios
It is still undefined, however, how this limiting should be implemented.
It could be implemented purely on L2 validateer code side, but this issue targets the sidechain pallet because this may be a more publicly transparent treatment of the limiting
brenzi
commented
1 year ago
Assuming the set of validateers is unpermissioned, we still want to limit the number of active validateers because there is no benefit in higher distribution - but some disadvantages:
It is still undefined, however, how this limiting should be implemented.
It could be implemented purely on L2 validateer code side, but this issue targets the sidechain pallet because this may be a more publicly transparent treatment of the limiting