At any given time, there are any number of validators registered in the state
machine. Each block, the top
MaxValidators (defined by
who are not jailed become bonded, meaning that they may propose and vote on
blocks. Validators who are bonded are at stake, meaning that part or all of
their stake and their delegators' stake is at risk if they commit a protocol fault.
For each of these validators we keep a
ValidatorSigningInfo record that contains
information partaining to validator's liveness and other infraction related
In order to mitigate the impact of initially likely categories of non-malicious protocol faults, the Cosmos Hub implements for each validator a tombstone cap, which only allows a validator to be slashed once for a double sign fault. For example, if you misconfigure your HSM and double-sign a bunch of old blocks, you'll only be punished for the first double-sign (and then immediately tombstombed). This will still be quite expensive and desirable to avoid, but tombstone caps somewhat blunt the economic impact of unintentional misconfiguration.
Liveness faults do not have caps, as they can't stack upon each other. Liveness bugs are "detected" as soon as the infraction occurs, and the validators are immediately put in jail, so it is not possible for them to commit multiple liveness faults without unjailing in between.
To illustrate how the
x/slashing module handles submitted evidence through
Tendermint consensus, consider the following examples:
[ : timeline start
] : timeline end
Cn : infraction
Dn : infraction
Vb : validator bonded
Vu : validator unbonded
Single Double Sign Infraction
A single infraction is committed then later discovered, at which point the validator is unbonded and slashed at the full amount for the infraction.
Multiple Double Sign Infractions
Multiple infractions are committed and then later discovered, at which point the validator is jailed and slashed for only one infraction. Because the validator is also tombstoned, they can not rejoin the validator set.