How often it happens
How likely is a validator to be slashed? Ethereum’s own records give a dated answer. A public beacon node’s head state, read at 10:09 UTC on November 10, 2026, listed 594 validators with the slashed flag set, out of a registry of about 2.4 million that have ever joined.
Every one of the 594 was already past the date when its remaining ether could be withdrawn, and the most recent had reached that point on September 26, 2026. None sat in the two statuses the beacon API uses for a validator slashed within the last 8,192 epochs, so no Ethereum validator had been slashed in the 36 days or so before that reading.
What gets a validator slashed
Ethereum.org’s rewards and penalties page lists three offenses. A validator can propose and sign two different blocks for the same slot, attest to two different candidates in the same vote, or cast a vote that “surrounds” an earlier one, which amounts to rewriting history. Each leaves signed evidence behind, and a block proposer that includes it in a block is paid a reward.
What it costs, day by day
Penalties follow the Electra version of the consensus specification, and the beacon node reports the constants it runs with. The figures below are for a 32 ETH validator.
| When | What happens | Size |
|---|---|---|
| Day 1 | Initial penalty, forced exit starts | 1/4,096 of effective balance, 0.0078125 ETH |
| About day 18 | Correlation penalty | Three times the share of all stake slashed in the 36-day window, applied to the balance |
| About day 36 | Validator becomes withdrawable | Whatever is left |
The correlation penalty is the one that bites in a mass event. With 44.4 million ETH staked that morning, one validator slashed alone would lose about 0.00007 ETH more. If a third of all stake were slashed inside the same window, each of those validators would lose everything. Throughout the 36 days a slashed validator also pays small attestation penalties, because ethereum.org says it is still present on the network without submitting votes.
The mistake people make
The common mix-up is to treat going offline as a slashing offense. Ethereum.org’s solo staking guide says downtime brings penalties that grow with the number of other validators offline at the same time, “but does not result in slashing.” The same guide says keeping your keys loaded on only one machine at a time, and running a minority client, minimizes the risk.
Rules vary by network. Solana’s Agave client still files slashing under its design proposals, which begin “We intend to implement slashing rules.” Exchanges that stake for customers can promise to cover slashing losses, a service the SEC’s Division of Corporation Finance listed in its May 29, 2025 staking statement. If your staking runs through a platform, check whether its terms include that cover before you rely on it.