A concrete example
Conflicting validator signatures can be slashable; merely missing a duty is a different situation.
In context
Slashing penalises specified consensus offences such as conflicting signatures. Ordinary downtime generally incurs different penalties; it is not synonymous with slashing. Insufficient participation can delay finality even if some blocks continue to be produced. Reusing validator signing keys on two active machines can create dangerous conflicting behaviour.
The related mechanism, visually
- 01Validator duties
- 02Single coordinated signer
- 03Attestations and proposals
- 04Rewards or protocol penalties
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
Ethereum validators propose blocks when selected and attest to their view of the chain. Rewards compensate participation in those duties, while missed duties and slashable behavior are different categories of failure. Ordinary downtime should not be described as automatically equivalent to signing conflicting messages. Validator operation also depends on execution and consensus software working together.
Put the mechanism into context
An operator loses contact with its primary machine and considers starting a backup. Write an incident checklist that distinguishes a disconnected monitoring dashboard from a stopped signing process. The exercise is about safe coordination, without running a real validator.
Apply it in the workshop →What this mechanism does not guarantee
A backup machine can create risk if it signs simultaneously with the original using the same validator identity. Recovery procedures must prevent duplicate signing, not just maximize uptime. Provider and client concentration can create correlated failures even when many validator keys exist. Withdrawal timing and any service wrapper add further operational constraints.
Explore the full explanation
Ethereum proof of stake and slashing
Validators commit ETH and participate in proposing blocks and attesting to the chain.