Summary : This Proposal is to limit the maximum number of keys per validator, per node and per shard. And also to limit dynamically the maximum number of keys per validator.
Background : Currently, we have large validators with a lot of keys. This represents a risk for the decentralization of the network and his security. Some crucial incoming features, such as the resharding and the external leader nodes depend directly on the decentralization of the network.
There is no limitation of number of keys per node.
There is no real limitation in terms of number of keys per validator (it’s currently 100+)
Motivation : These changes will help in the decentralization of the network and its security. By capping the maximum of keys and dynamically limit the number of keys, there will be more opportunities for the new validators to secure the network. Limiting the number of keys per node will strengthen the resilience of the network.
- Maximum cap of 24 bls keys per validator, starting from 32 (minus one every 10 epochs). The protocol will ignore all the keys added over the maximum. This will free 98 keys considering the current situation.
The maximum will decrease over time to transition smoothly. This will give the chance to the validators with some extra keys to communicate with their delegators and this will allow to onboard progressivily the new validators.
Dynamic key limitation : The protocol will prevent to add a new key if that makes your validator bid below the 0,65xEMS. Note : If a validator looses some stake and bid below the 0,65xEMS, the protocol won’t delete automatically his keys, but this validator will likely have to delete manually his keys to stay elected and once done he won’t be able to add a new one (if the bid is under 0x65xEMS)This dynamic limitation is required to guarantee that the released keys (by the max cap) are not all taken by the medium size validators. This limitation will also give some relief to the validators who were fighting for keys and less stress/tension is expected in the validator community.
Maximum of 6 keys per node : The protocol will limit the number of keys per node to 6. This will guarantee the validators to split their keys across the shards improving the security. Why 6? Because 4 (shards) x 6 (keys) = 24 maximum keys.
Maximum of 6 keys per shard per validator : The protocol will limit the number of keys to 6 per per shard per validator. This limit will apply once we reach the maximum of 24 keys.