Crypto Newbie / Simulators / Restaking Slashing
Restaking AVS Slashing Cascade Simulator
Restaking (EigenLayer, Symbiotic, Karak) lets you re-use your staked ETH to secure additional services called AVS. Each extra AVS pays you yield BUT introduces additional slashing conditions. When operators have shared infrastructure (single node config affecting multiple AVS), a single bug can trigger correlated slashing across everything. Delegators bear the loss pro-rata. This simulator runs the cascade math so you can see the true risk profile of restaking before opting in.
Operators
| Operator | Self stake (ETH) | AVS running | Total stake |
|---|---|---|---|
| Pro operator (P2P) | avs1, avs2, avs3, avs4 | 700.000 ETH | |
| Mid operator (Stakefish) | avs1, avs2 | 96.000 ETH | |
| Small operator | avs1, avs3 | 42.000 ETH |
Delegators
| Delegator | Stake (ETH) | Delegated to |
|---|---|---|
| Whale delegator | ||
| Mid delegator | ||
| Retail delegator | ||
| Small delegator |
AVS roster
| AVS | Slash % |
|---|---|
| Oracle (EigenDA) | |
| Bridge (Hyperlane) | |
| Coprocessor (Ritual) | |
| L2 sequencer (Mantle) |
Trigger a fault
Plain ETH staking vs restaking — the slashing surface
Plain ETH staking: one slashing condition (Ethereum consensus). Worst case: 1/32 stake immediate + correlation penalty if many slash together. Restaking on EigenLayer: ETH base layer slashing + each AVS's own slashing conditions. Run 5 AVS = 6 different slashing surfaces. A single misconfigured operator can be slashed multiple times in one event. The yield boost must compensate for this multiplied risk.
Why correlation matters more than nominal slash %
If each AVS has 5% slashing risk per year independently, your total annual slashing risk on 5 AVS is roughly 25%. But if those AVS share infrastructure (same node, same operator, same client software), the actual events are correlated. When the operator messes up, ALL the AVS that share that infrastructure slash simultaneously. The realistic max-loss isn't 5% × 5 = 25%; it's closer to a single 25-30% event because they all hit at once. EigenLayer's 'unique stake' allocation tries to limit this but operators still concentrate.
Delegators bear the loss — they don't run the infrastructure
When you delegate to an operator, your stake is slashable for that operator's mistakes. The operator's commission (5-15% of rewards) is supposed to compensate them for the risk of running infrastructure. But the SLASHING bill goes to YOU pro-rata to your share of the operator's total stake. Pick a bad operator and your delegation can lose 10-30% in a single event. Operator selection on EigenLayer is dramatically more important than picking an Ethereum validator (where slashing is rare and capped).
Math vs marketing — what restaking yields really pay
EigenLayer's marketing emphasises the YIELD STACK: ETH staking 4% + AVS rewards 2-8%. Sounds great. The risk math: an additional 2-8% yield in exchange for 5-15% additional slashing risk per year on the entire stake. If you're delegated to an operator running 5 AVS and one bug hits, you lose 20-30% in an instant. The pure-math comparison: if the extra yield doesn't exceed (slashing probability × expected loss), restaking is a bad trade. For most retail, the answer is currently: stick with plain ETH staking.
Frequently asked questions
+How do I assess an operator's slashing risk?
Check (1) how many AVS they run — more = higher correlation surface. (2) Their operator track record on plain Ethereum staking (no missed attestations, no past slashings). (3) Whether they run isolated infrastructure per AVS or shared. (4) Their commission — abnormally low commission often means under-resourced operations. Avoid operators with > 5 AVS, < 1 year track record, or 0% commission as their marketing hook.
+Can I un-restake to avoid a brewing slash event?
There's a withdrawal queue on EigenLayer — 7-21 days depending on circumstances. During this period your stake is still slashable for the operator's misbehaviour. You can't 'see slashing coming' and exit fast enough; the withdrawal delay is intentionally designed so you can't escape a brewing issue. The defence is operator selection BEFORE restaking, not reactive withdrawal.
+What's the difference between restaking and re-staking with the same validator?
Plain ETH staking = your validator only validates Ethereum. Restaking = your validator's stake is ALSO at risk for whatever AVS the operator opts in to. The operator decides which AVS to run; you, as delegator, can only choose which OPERATOR to delegate to. Picking 'no AVS' operators (rare) gives plain-staking yield with no extra risk — but most operators stack AVS for the yield boost.
+Is EigenLayer the only restaking protocol?
No. EigenLayer is the largest by TVL (~$15B in 2026), but Symbiotic, Karak, and Babylon (Bitcoin-based restaking) are growing competitors. Each has different slashing mechanics — Symbiotic is more modular (per-AVS customisable slashing), Karak uses a more conservative shared-stake model. The principles are similar; the implementation details vary. The risk math we run here applies to all.
+What's a realistic worst-case restaking loss?
Hardware operator failure during a contentious AVS upgrade: estimate 20-40% slash across multiple correlated AVS. Smart contract bug in EigenLayer itself (low probability): 100% loss. Operator turning malicious (low probability but happened with smaller stake setups): 100% of stake delegated to that operator. The simulator above demonstrates the cascade math; real worst cases are typically the cascade outcomes amplified by less-favourable correlation factors than defaults shown.