# Evidence Handling
Tendermint blocks can include
which indicates that a validator committed malicious behavior. The relevant information is
forwarded to the application as ABCI Evidence in
abci.RequestBeginBlock so that
the validator an be accordingly punished.
Currently, the evidence module only handles evidence of type
Equivocation which is derived from
Equivocation submitted in
block to be valid, it must satisfy:
Evidence.Timestamp >= block.Timestamp - MaxEvidenceAge
Evidence.Timestamp is the timestamp in the block at height
block.Timestamp is the current block timestamp.
Equivocation evidence is included in a block, the validator's stake is
reduced (slashed) by
SlashFractionDoubleSign, which is defined by the
of what their stake was when the infraction occurred (rather than when the evidence was discovered).
We want to "follow the stake", i.e. the stake which contributed to the infraction
should be slashed, even if it has since been redelegated or started unbonding.
In addition, the validator is permanently jailed and tombstoned making it impossible for that validator to ever re-enter the validator set.
Equivocation evidence is handled as follows:
Note, the slashing, jailing, and tombstoning calls are delegated through the
which emit informative events and finally delegate calls to the
x/staking module. Documentation
on slashing and jailing can be found in the x/staking spec