Can one EigenLayer service slash your whole stake?
One EigenLayer service can slash the stake assigned to it, but the risk depends on how much an operator allocates and what the service’s rules allow.
EigenLayer lets a service slash the stake an operator has assigned to it, but that does not automatically put every asset you restake at risk. EigenLayer lets operators use restaked assets to help secure extra services, which can set penalties for breaking their rules. The key question is how much stake the operator has put behind each service.
EigenLayer calls these services actively validated services, or AVSs. Operators choose which AVSs to support and allocate stake to their operator sets, the groups of operators serving them. For readers following eigen layer, this distinction helps explain where a service’s slashing power begins and ends.
Can one EigenLayer service slash all your stake?
It can slash the stake allocated to its operator set, up to the amount the protocol allows that service to slash. EigenLayer calls stake assigned this way “unique stake”: it is reserved for one operator set at a time, rather than being exposed to every service the operator runs.
So one AVS cannot simply reach across the operator’s entire restaked balance. But if the operator assigns a large share of that balance to one service, a severe penalty under that service’s rules could put that share at risk. The exact trigger and penalty depend on the AVS rules and how the operator has allocated stake.
How does EigenLayer decide what can be slashed?
The operator chooses an allocation from eligible restaked assets, and the AVS defines what counts as a breach. EigenLayer’s contracts check that the operator is registered or still within a period when it remains slashable, that the AVS can use the relevant asset strategy, and that stake is allocated to its operator set.
The AVS then specifies the share of that allocation to slash. That means a service can request a large cut of its assigned stake, potentially all of it, if its rules and the protocol conditions permit. The protocol does not decide whether the service’s penalty is fair; it enforces the slash request when the required conditions are met.
What happens if an operator serves several AVSs?
The operator can split its eligible stake across services. Since each portion is assigned to one operator set at a time, a slash by one service applies to its own allocation. Other allocated portions can still face penalties from their respective services, so the combined risk depends on the operator’s choices and the rules of every service it supports.
- Ask which AVSs the operator serves.
- Check how much stake is allocated to each operator set.
- Read the service’s stated slashable actions and penalty terms.
- Check whether the operator can still be slashed during a withdrawal or deallocation period.
What should a restaker check before choosing an operator?
Look at allocation and rules, not just the number of services. More services do not necessarily mean each one can slash the same stake, but a broad set of allocations can expose different portions to different penalties. Ask the operator how it allocates stake and how it reviews each AVS’s terms.
The practical answer is that one EigenLayer service can put the operator’s assigned stake at risk, not automatically the restaker’s whole balance. The size of that risk comes down to the allocation, the service’s rules and whether the operator remains slashable.