Level 3 · How it worksThe village#206

Slashing explained: sign two pages and pay a fine, sign them with a crowd and pay it all

Slashing is Ethereum's punishment for signing two contradictory things: two blocks for one slot, two votes for one target, or a vote that surrounds another. The validator loses a small slice at once, is forced out over about 36 days, and loses far more if many others were slashed at the same time.

Ben has a deposit in the box by the well, and one evening he's drawn to write the page. He writes two. In one, he paid Anna for the firewood. In the other, he didn't. He shows the first page to half the village and the second to the other half.

The trouble is that Ben signed both. Two pages for one turn, same signature, and any villager who sees both can carry them to the well. The village doesn't need to know which page was honest. Two signatures that contradict each other are proof enough.

So part of Ben's box is taken, his name is struck off the signers' list, and his coins stay locked for weeks while the village checks whether anyone else did the same thing. That's slashing: the punishment for saying two things at once.

What it is

Slashing is the penalty Ethereum's protocol applies to a validator that signs contradictory messages. ethereum.org lists exactly three ways to earn it (ethereum.org):

  • Double proposal: "proposing and signing two different blocks for the same slot".
  • Double vote: "double voting", attesting to two candidates for the same block.
  • Surround vote: "attesting to a block that 'surrounds' another one (effectively changing history)". The new vote's span from source to target wraps around an earlier vote's span, as if to replace what that vote supported.

The specification checks the last two with one function, commented simply "# Double vote" and "# Surround vote" (Phase 0 spec). Being offline is not on the list.

How it works

The penalty comes in three steps, each set in the specification.

  1. At once: a small slice. Since the Pectra upgrade of 7 May 2025 (ethereum.org), the immediate penalty is the validator's effective balance divided by 4,096 (Electra spec). For 32 ETH, that's 0.0078125 ETH. For a validator holding the maximum 2,048 ETH, it's 0.5 ETH. Before Pectra the divisor was 32, so a 32 ETH validator lost a full 1 ETH (Bellatrix spec). Whoever reports the offence gets a reward of the same size, shared with the block proposer who includes it.
  2. The forced exit. The validator is thrown out and can't withdraw until 8,192 epochs have passed (Phase 0 spec). At 6.4 minutes an epoch, that's about 36.4 days. ethereum.org rounds it to 36.
  3. Halfway: the correlation penalty. Around day 18, a second penalty arrives. It takes the stake of everyone slashed in the 36-day window, multiplies it by 3, divides by all active stake, and charges that fraction of the validator's own balance (Electra spec). ethereum.org calls it the "correlation penalty".

Now the sum, with 44,339,549 ETH of active stake, read on 19 November 2026 from beaconcha.in, for one 32 ETH validator:

  • Slashed alone: 3 times 32, divided by 44,339,549, times 32 is about 0.00007 ETH. With the first slice, the total is under 0.008 ETH.
  • Slashed with 39 others at the same time (1,280 ETH in all): about 0.0028 ETH more.
  • Slashed together with one-third of all stake (about 14.8 million ETH): 3 times one-third is one. The whole 32 ETH is gone.

That's the design. A single slip costs little. A coordinated attack, the kind that could break finality, costs the attackers everything.

A real case. On 10 September 2025, SSV Network's monitoring saw two slashing waves: one validator at 11:51 UTC and a cluster of 39 at 13:17 UTC. The 39 belonged to the staking firm Ankr, which confirmed "an internal maintenance mistake that ran a parallel validator instance outside of SSV" (SSV Network). A second copy of the same validators, signing alongside the first. Nobody was trying to cheat.

Why it matters

  • Cheating gets a price tag. Without slashing, signing every version of history would be free. With it, contradicting yourself costs stake.
  • Mistakes cause it too. The Ankr case shows the pattern: a second machine running the same key as the main one.
  • Big operators carry bigger risk. One operator's mistake hits all its validators at once, and the correlation penalty grows with the crowd.

Where people get it wrong

  • "Offline validators get slashed." No. Offline costs small penalties, and the inactivity leak if the whole chain stops finalising. Slashing needs a contradictory signature.
  • "A slashing costs 1 ETH." It did before 7 May 2025. Since Pectra, the first slice is 1/4,096 of the effective balance; the correlation penalty can be far larger.
  • "Slashing is for attackers only." The Ankr case was an operator running one key in two places, with no attack in sight.
  • "Your ether is back the next day." A slashed validator waits about 36 days before it can withdraw.

Never run one key twice

If you stake yourself, the most important rule fits on a sticky note: one key, one machine. A spare that switches on automatically "just in case" is how honest operators end up signing two pages. When you move a validator, switch the old one off first and wait.

Ben tried to sign two pages on purpose. Good luck, Ben. Anna's only risk is doing it by accident, and she has the sticky note.

Frequently asked questions

What is slashing in Ethereum?

Slashing is the penalty for a validator that signs contradictory messages: two blocks for one slot, two conflicting votes, or a vote that surrounds an earlier one. The validator loses part of its stake and is removed from the network.

How much ETH do you lose when slashed?

Since the Pectra upgrade on 7 May 2025, the immediate penalty is 1/4,096 of the effective balance, 0.0078125 ETH for a 32 ETH validator. A correlation penalty follows around day 18, which is tiny for a lone validator and can reach the whole balance if one-third of all stake is slashed together.

Can you get slashed for being offline?

No. Being offline costs small penalties for missed votes. Only if the chain stops finalising does the inactivity leak start, which drains offline validators faster, but that is still not slashing.

How long does a slashed validator wait to withdraw?

8,192 epochs, about 36 days. The validator is forced to exit and can't withdraw its remaining balance until that period ends.

What usually causes slashing?

Operator mistakes can cause it as well as attacks. In September 2025, 39 validators were slashed after an internal maintenance mistake at Ankr ran a parallel validator instance, according to SSV Network's post-mortem.

Sources

  1. ethereum.org, Proof-of-stake rewards and penalties
  2. Ethereum consensus specs, Phase 0 beacon chain (is_slashable_attestation_data, EPOCHS_PER_SLASHINGS_VECTOR)
  3. Ethereum consensus specs, Bellatrix beacon chain (PROPORTIONAL_SLASHING_MULTIPLIER_BELLATRIX, MIN_SLASHING_PENALTY_QUOTIENT_BELLATRIX)
  4. Ethereum consensus specs, Electra beacon chain (slash_validator, process_slashings)
  5. ethereum.org, The history of Ethereum (Pectra, 7 May 2025)
  6. SSV Network, Slashing post-mortem, September 2025
  7. beaconcha.in, Epoch 490,260 (19 November 2026, 10:24:23 UTC): active stake

Read next.