Skip to content
Blockchain

How do I slash a restaker whose off-chain output is wrong but unprovable on-chain?

84

Opportunity

EigenLayer activated slashing in April 2025 with roughly $15 billion restaked across 40 AVSs. As of mid-2026, zero slashing events have been recorded. Most AVS tasks, including oracle feeds, off-chain compute, and AI inference, produce outputs that an on-chain verifier cannot falsify without re-executing the same workload at equivalent cost. The fallback mechanism is EIGEN token-weighted social slashing, which requires a supermajority vote and is gameable by any operator with sufficient stake concentration. Additionally, operators must actively opt into each AVS's slashing terms rather than inheriting them automatically, so the security model accumulates coverage incrementally and unevenly across the network.

Why it matters

Restaking security that cannot be enforced against the most common class of faults collects a risk premium without delivering the protection, and protocols that build on top of it inherit a guarantee that cannot be redeemed.

How I score the opportunity

The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.

Severity9/10

How much pain it causes when it shows up.

Frequency7/10

How often people actually run into it.

Whitespace8/10

How little good tooling exists for it today.

More problems worth solving