Slashing Conditions

Restaking's tradeoff: more yield, more risk. Each AVS defines its own slashing conditions. If an operator violates them — signing conflicting data, going offline during critical periods, or producing invalid proofs — their restaked ETH (and their delegators' ETH) gets slashed. Multiple AVS slashings can compound.

⚡ Slashing Impact Simulator

Your Restaked ETH 100 AVSs Your Operator Validates 3 Slashing Penalty per AVS (%) 5 AVSs Slashed Simultaneously 1

Starting Stake

100 ETH

Total Slashed

5.00 ETH

Remaining

95.00 ETH

Loss %

5.0%

🔍 Types of Slashable Offenses

✍️

Double Signing

Signing two conflicting attestations for the same slot/task. Provable on-chain with two signatures.

High Severity

📴

Downtime / Inactivity

Failing to respond to validation tasks within the required window. Usually lower penalties.

Medium Severity

❌

Invalid Computation

Submitting incorrect proofs, wrong oracle prices, or invalid state transitions. Verified via fraud/validity proofs.

High Severity

🤝

Collusion

Multiple operators coordinating to produce false consensus. Hardest to detect, most damaging.

Critical Severity

🛡️ Slashing Safeguards

✅ For Restakers

Choose operators with strong track records
Diversify across multiple operators
Monitor which AVSs your operator validates
7-day withdrawal delay gives time to react
Check operator's insurance coverage

🏗️ Protocol-Level

Veto committee can cancel unfair slashings
Slashing caps per AVS (max % per incident)
Fraud proof windows before slashing executes
Gradual rollout — AVSs start with lower penalties
On-chain slashing evidence required (not subjective)