What it is
Restaking lets someone who has already staked a crypto asset (like ETH, to help secure a blockchain) opt in to also back additional services with that same stake, instead of only earning rewards from the base chain. Those additional services — often called "actively validated services" — get security guarantees for free (they don't need to bootstrap their own token and validator set), and the staker earns extra yield for taking on the extra risk. It's essentially renting out the same collateral twice.
How it works
- A user stakes a base asset (e.g., ETH) with a validator, either directly or through a liquid staking token, to secure a base chain like Ethereum.
- The user (or their staked position) opts in to a restaking protocol, which lets them delegate that same stake's economic weight to one or more additional services — oracles, bridges, data availability layers, other appchains.
- Each service defines its own rules ("slashing conditions") for what counts as misbehavior specific to that service, separate from the base chain's own rules.
- Operators run the software for these services and are the ones actually doing the validating; restakers delegate stake to operators, who take a cut of rewards.
- If a service detects a violation of its rules by an operator, a portion of the delegated stake backing that operator can be slashed (destroyed or redirected), even though the underlying asset was originally staked for a completely different chain.
- In exchange for this added slashing risk, the service pays out additional rewards (in its own token or fees) on top of the base staking yield.
- Restakers can typically choose which services to opt into, controlling their own risk-reward tradeoff, and can withdraw from a service (subject to unbonding delays) if they want to stop backing it.
Why designers use it
- Gives new protocols instant access to a large pool of economically-committed capital and validators without needing to launch and distribute their own token from scratch.
- Lets existing stakers earn additional yield on capital that would otherwise sit idle earning only base staking rewards.
- Creates a marketplace for "security as a service," letting infrastructure specialize (data availability, oracles, bridges) while sharing a common trust and capital base.
Failure modes
- Correlated slashing: a bug or attack affecting one service can trigger slashing across many restakers simultaneously, since the same underlying stake backs multiple systems at once.
- Operator concentration: if too much delegated stake flows to a small number of professional operators, a single operator's failure or misbehavior can cascade across every service it secures.
- Cascading risk stacking: opting into many services multiplies the number of independent ways to get slashed, so total risk can compound in ways that are hard for an average staker to evaluate.
- Base-chain contagion: because the underlying collateral also secures the base chain, a severe restaking-related loss event can spill over and affect confidence in the base chain's own security.
- Complexity and opacity: slashing conditions for niche services are often hard to audit, so restakers may not fully understand what behavior actually triggers a penalty until it happens.
What to check before using it
- Read the slashing conditions for every service you opt into, not just the headline yield — understand exactly what operator behavior can cost you money.
- Check operator concentration: how much total stake is delegated to the operators you're using, and what happens to you if they get slashed or go offline.
- Understand unbonding/withdrawal delays for each service, since you may not be able to exit quickly if a service starts looking risky.
- Verify whether slashing has actually been enabled and tested for a given service, or whether it's still a theoretical mechanism with rewards live but penalties not yet enforced.
- Consider your total stacked risk across all services you're restaked into, not each one in isolation.