Restaking commits assets to additional service obligations that can bring rewards and penalties. EigenLayer coordinates restakers, operators and services. To understand an exposure, trace the deposited asset to the operator, the service receiving slashable stake and the conditions for getting the asset back.
“Borrowing Ethereum's trust” is an incomplete shortcut. A service does not automatically acquire the entire Ethereum validator set, every Ethereum security property or compensation for every failure. Its actual protection depends on its contracts, operators, allocated stake and enforcement rules.
On this page: Who does what · Calculate a slash · Separate yield and return · Map the exit
Follow the asset through three roles
The protocol overview describes restakers providing assets, operators running service software and AVSs defining work and incentives. Current documentation uses “Autonomous Verifiable Services”; older materials often expand AVS as “Actively Validated Services.”
The restaking guide distinguishes native ETH restaking through validator withdrawal credentials and EigenPods from deposits of supported ERC-20 assets, including liquid staking tokens. A liquid restaking token issued by another protocol adds that provider's own contracts and redemption arrangements.
Delegation and allocation are separate steps. A restaker delegates to an operator; the operator can allocate stake to specific Operator Sets. These group operators under an AVS's requirements. The useful review unit is the actual operator-and-set exposure, not just the platform's total deposits.
One pool does not give every service an unlimited claim
Under Unique Stake, a slashable allocation belongs exclusively to one Operator Set and is slashable by that set's AVS. This refines the earlier article's broad description of the same capital being exposed across services.
| Allocation | Amount at this snapshot |
|---|---|
| Operator Set A | 80 units, or 40% |
| Operator Set B | 60 units, or 30% |
| Not allocated to these sets | 60 units, or 30% |
Assume all allocations are active and unchanged, and A imposes a penalty equal to 25% of its allocated amount. Ignore rewards, new deposits, withdrawals and other penalties for this exercise.
Is the loss 25% of all 200 units?
No. The assumed loss is 80 × 25% = 20 units, or 10% of the starting pool. Under this snapshot, A's authority concerns its 80-unit allocation. It does not give A authority to slash B's separate 60 units. The remaining total is 180 units before other changes.
This arithmetic is a teaching model, not a substitute for contract share and magnitude accounting. Actual allocations change over time. Also, “unallocated to these sets” does not mean risk-free: contract, underlying-asset and other applicable staking risks remain. Several sets can suffer separate problems during the same incident.
Read the slashing authority, not just the advertised security
Eigen Labs announced mainnet slashing in April 2025. Current slashing documentation says AVSs define the conditions and have substantial flexibility. A penalty need not always follow a fault that is objectively provable on-chain.
Slashed assets may be burned or, for eligible redistributable configurations, sent to a specified recipient. Redistribution does not automatically mean the harmed end user is reimbursed. Read the recipient, decision process, permissions and safeguards for the particular set.
A useful question: if an operator is accused of failing its task, who decides, what evidence is required, who can change the decision rules, and where do the slashed assets go? A large TVL number answers none of these questions.
A positive reward rate can coexist with a negative result
The rewards documentation describes AVS token distributions and operator fee splits. A reward is a separate cash-flow or token-flow item, not a guarantee that the principal stays intact. Record the reward asset, distribution period, eligibility and costs before comparing rates.
Starting value: 200
Base rewards: +6
Additional service rewards: +4
Fees and other costs: −1
Loss from the illustrative penalty above: −20
Ending value: 189; net change: −5.5%.
The gross rewards in that example equal 5% of the starting value, yet the total result is negative. It assumes unchanged asset prices and ignores timing and tax. If rewards are paid in a different token, their conversion value must also be measured; percentages in different assets cannot simply be added.
For a liquid restaking token, an executable sale price introduces another variable. A displayed claim worth 1 unit is different from a buyer offering 0.97 units now. That three-percent discount in a hypothetical sale is an exit cost, even if the protocol's accounting value has not changed.
Map the exit before treating the balance as cash
Safety delays mean that reducing an allocation does not instantly eliminate every slashing exposure. The restaking documentation also describes withdrawal delays and fixed-duration vaults. A provider wrapping the position may add its own queue or liquidity constraints.
Do not assume one universal withdrawal time across native ETH, an LST deposit, a duration vault and a third-party liquid restaking token. For the actual route, write down the request step, remaining exposure, waiting conditions, completion transaction and asset received. For native ETH, account for applicable Ethereum validator-exit steps as well.
Planning exercise: suppose you need a payment by Friday but can only verify that a withdrawal request was accepted on Wednesday. You still do not know that funds will be available on Friday. The missing facts are the queue status, applicable delays and completion requirements. An accepted request is not a completed payout.
A record to keep when reviewing restaking
- Asset and wrapper: what was deposited, and what claim is held now?
- Operator and sets: where is stake allocated, and how can this change?
- Penalty authority: who can slash, under which process and to which recipient?
- Rewards: what has actually accrued or been received, after fees?
- Exit: which steps remain before the desired asset is usable?
To separate the underlying network from added service risks, read how Ethereum works. For another example of the difference between a token balance and usable proceeds, see BUIDL's transfer and redemption routes.