Earning twice on the same ETH: what it really means
Restaking lets ETH already staked on Ethereum, or a liquid staking token, also serve as collateral securing other services. Earning Ethereum rewards and extra service rewards on the same assets has drawn attention, but every additional service that relies on the stake is another set of conditions under which it can be lost.
Here we cover how restaking works, where the extra rewards come from, and when slashing occurs, with a hypothetical validator calculation. It also covers withdrawal and liquidity constraints and the risks to check in documentation and contracts.
How restaking is structured
In a restaking protocol, stakers deposit assets and delegate them to operators. Operators opt into external services, such as data availability, oracles, or bridge validation, and perform the work those services require. The stake acts as collateral that can be cut if the operator breaks the rules.
EigenLayer's documentation describes a system in which each service defines its own slashing conditions and operators decide how much stake to allocate to each service. Restaking risk therefore depends not on Ethereum's rules alone but on the rules and implementation of every service involved.
Security services and extra rewards
External services pay rewards in exchange for borrowed security, often in their own tokens. If those tokens fall in price, the real value of the reward falls with them. However high the advertised rate, check which token it is paid in and how liquid that token is.
Early-stage services tend to pay more, but untested code and operations can mean unexpected slashing risk. Unlike base Ethereum staking rewards, restaking rewards differ completely from one service to another.
A hypothetical validator
The table follows a hypothetical staker with 32 ETH staked, half of which (16 ETH) is allocated to two external services, over one year with and without a slashing event.
| Item | ETH per year | Note |
|---|---|---|
| Base Ethereum staking reward (3%) | +0.96 | Protocol rewards |
| Service A reward (2% on 16 ETH allocated) | +0.32 | Paid in Service A's token |
| Service B reward (1.6% on 16 ETH allocated) | +0.256 | Paid in Service B's token |
| Total with no slashing | +1.536 (4.8%) | About 1.8 points from restaking |
| Service B slashes 10% of allocated stake | -1.6 | Operator error or rule violation |
| Total after one slashing | -0.064 | A year's rewards lost and then some |
The 0.576 ETH of extra rewards was wiped out by a single 1.6 ETH slash. Slashing conditions and their likelihood, not the reward rate, decide the outcome.
When slashing happens
Ethereum's own slashing applies only to clear violations such as double signing, and the conditions are public, as Ethereum.org's page on rewards and penalties explains. Restaking services set their own conditions, which can include failing to provide data on time or signing incorrect results.
The danger is that bugs in the code that judges violations, or errors by those operating a service, can penalize honest operators. If one operator participates in many services, an incident at one can affect all of that operator's delegators.
Withdrawal and liquidity limits
Withdrawing restaked assets often requires passing through a restaking-protocol withdrawal delay on top of Ethereum's exit queue. Slashing for earlier violations can still apply during that delay, so the risk does not end the moment you request withdrawal.
Liquid restaking tokens can be sold on the market, but they may trade at a discount to the underlying assets or have thin liquidity. Every additional layer of contracts adds smart-contract risk.
Ethereum.org's staking overview frames base staking as a trade-off between rewards and responsibilities. Restaking stacks further trade-offs on top, and each layer deserves the same scrutiny as the first.
Checking documents and contracts
Before restaking, work through these checks.
- Find which services your chosen operator participates in and how much stake is allocated to each.
- Read each service's slashing conditions, who decides violations, and any slashing history.
- Check which tokens rewards are paid in and how liquid and volatile they are.
- Add Ethereum's exit queue to the restaking protocol's withdrawal delay to estimate the real time to exit.
- Review audit reports, upgrade powers, and emergency pause powers for the contracts involved.
Limits of evaluating restaking
Restaking is changing quickly; slashing features are being rolled out in stages and rules change often. The absence of past slashing does not guarantee its absence in future.
The reward and slashing rates here are hypothetical. Before participating, check Ethereum.org and the restaking protocol's current documentation along with the date of each, and calculate for yourself whether the extra reward compensates for the extra risk.