You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the max evidence age in the cosmos sdk is not effective since the Time field in the ABCI evidence is propagated with the block time in which the evidence was reported.
Relevant code in Tendermint getBeginBlockValidatorInfo
for i, ev := range block.Evidence.Evidence {
// We need the validator set. We already did this in validateBlock.
// TODO: Should we instead cache the valset in the evidence itself and add
// `SetValidatorSet()` and `ToABCI` methods ?
valset, err := LoadValidators(stateDB, ev.Height())
if err != nil {
panic(err) // shouldn't happen
}
byzVals[i] = types.TM2PB.Evidence(ev, valset, block.Time)
}
return commitInfo, byzVals
That allows validators to be rejailed/slashed if the evidence is older than the maxAge but within the Tendermint max evidence age.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
hendrikhofstadt
changed the title
Max evidence ago not effective
Max evidence age not effective
Jan 8, 2019
Currently the max evidence age in the cosmos sdk is not effective since the Time field in the ABCI evidence is propagated with the block time in which the evidence was reported.
Relevant code in Tendermint
getBeginBlockValidatorInfo
That allows validators to be rejailed/slashed if the evidence is older than the maxAge but within the Tendermint max evidence age.
For Admin Use
The text was updated successfully, but these errors were encountered: