Ethereum validators are slashable for proposing two blocks in one slot, double-voting, or making a surround vote.
The three contradictions
Ethereum Mainnet treats slashing as a cryptographic judgment about signed messages, not a general punishment for poor uptime.
- Proposer equivocation: the validator signs two different beacon blocks for the same slot.
- Double voting: the validator signs two different attestations with the same target epoch.
- Surround voting: one attestation’s source and target checkpoints enclose the source and target of another vote, implying incompatible views of chain history.
Missing an attestation, proposing late, or going offline normally causes ordinary penalties or lost rewards. It does not, by itself, create slashable evidence.
When a transfer touches Ethereum Mainnet, keep this validator layer separate from the route itself; the broader Manta Bridge question concerns the cross-network path, while slashing concerns contradictory signatures.
How a slash is enforced
- A validator key signs two messages that cannot both be valid under the consensus rules.
- A node preserves the messages and checks their BLS signatures, validator index, slot or epoch, and attestation data.
- A block proposer includes the proof as a proposer-slashing or attester-slashing object.
- The beacon-chain state transition verifies the evidence, marks the validator as slashed, and begins its forced exit.
The important detail is that nobody has to decide which message was honest. The contradiction is the offense. Two valid signatures from the same validator are enough to prove that its key endorsed mutually incompatible outcomes.
That makes key management part of consensus security. Running one signing key on two active machines, restoring a stale validator database, or migrating clients without its slashing-protection history can produce a genuine double vote. A redundant setup intended to improve availability can therefore create the exact evidence the protocol is designed to punish.
Who pays, and what changes the cost?
The slashed validator pays from its own effective balance. The block proposer that includes valid evidence receives a protocol reward, creating a financial reason to carry out enforcement instead of ignoring it.
The size of the loss depends on more than the individual mistake. Ethereum applies an initial penalty, then a later correlation penalty tied to the total effective balance slashed during the relevant window. One isolated validator signing twice may lose a relatively small fraction; many validators producing conflicting signatures together can face a much larger reduction, potentially consuming most or all of their stake.
Cross-Consensus Messaging can move instructions between consensus systems, but it does not alter these Ethereum predicates. A bridge, relayer, or application can change the route a user takes; it cannot make two conflicting attestations acceptable.
FAQ
Is an offline validator slashable?
Usually no. Extended inactivity can trigger penalties and, when finality is lost, an inactivity leak. Slashing requires specific conflicting signed messages, which is why protecting signing history matters more than simply keeping a machine online.
Top comments (0)