docs: add consensus pubkey docs (#19081)
Co-authored-by: Facundo Medica <14063057+facundomedica@users.noreply.github.com> Co-authored-by: samricotta <37125168+samricotta@users.noreply.github.com>
This commit is contained in:
co-authored by
Facundo Medica
samricotta
parent
d4614a1441
commit
2a95a4abdd
@@ -34,11 +34,11 @@ Also, it should be noted that this ADR includes only the simplest form of consen
|
||||
* In current Tendermint design, consensus key rotations are seen as power changes from LCD or IBC perspective
|
||||
* Therefore, to minimize unnecessary frequent key rotation behavior, we limited maximum number of rotation in recent unbonding period and also applied exponentially increasing rotation fee
|
||||
* limits
|
||||
* a validator cannot rotate its consensus key more than `MaxConsPubKeyRotations` time for any unbonding period, to prevent spam.
|
||||
* rotations are limited to 1 time in an unbonding window. In future rewrites of the staking module it could be made to happen more times than 1
|
||||
* parameters can be decided by governance and stored in genesis file.
|
||||
* key rotation fee
|
||||
* a validator should pay `KeyRotationFee` to rotate the consensus key which is calculated as below
|
||||
* `KeyRotationFee` = (max(`VotingPowerPercentage` *100, 1)* `InitialKeyRotationFee`) * 2^(number of rotations in `ConsPubKeyRotationHistory` in recent unbonding period)
|
||||
* `KeyRotationFee` = (max(`VotingPowerPercentage`, 1)* `InitialKeyRotationFee`) * 2^(number of rotations in `ConsPubKeyRotationHistory` in recent unbonding period)
|
||||
* evidence module
|
||||
* evidence module can search corresponding consensus key for any height from slashing keeper so that it can decide which consensus key is supposed to be used for given height.
|
||||
* abci.ValidatorUpdate
|
||||
|
||||
Reference in New Issue
Block a user