Restaking
Understand restaking, shared security, additional services, slashing conditions, operator risk and the correlated-loss risks created by reusing staked collateral.
Reading progress — saved on this device
Restaking reuses already-staked or staking-derived economic collateral to secure additional protocols, services or validation tasks in exchange for additional rewards.
Learning objectives
- Explain the shared-security idea behind restaking.
- Identify how extra rewards correspond to extra duties or loss conditions.
- Analyse correlated slashing, operator and composability risk.
What it is
In ordinary native staking, stake secures one base network under its consensus rules. A restaking system allows that same or derivative stake to support additional services, sometimes called actively validated services or similar terms depending on the ecosystem.
The service gains access to an existing economic-security base, while restakers may receive additional compensation. The economic question is what new risk the restaker accepts for that incremental return.
How it works
Restaking can create a chain of claims: underlying asset → native staking position → liquid staking token → restaking receipt. Each layer has its own contracts, governance and liquidity.
Extra yield can come from service fees, token incentives or bootstrapping emissions. A high headline yield may be dominated by temporary reward tokens rather than durable cash-flow-like economics.
Slashing complexity is critical. If the same stake secures multiple services, one operational error, software bug or compromised operator can potentially affect several commitments.
Systemic risk grows when many protocols depend on the same restaking layer or operator set. A shock can propagate across services that appeared unrelated at the application level.
How to analyse it
Restaking analysis starts with the new obligation, not the advertised yield. Identify exactly what the stake is securing and who can impose or trigger penalties.
| Check | Why it matters | What to verify |
|---|---|---|
| Service duties | Different services create different failure modes. | Read task and slashing specifications. |
| Operator concentration | A few operators can create correlated operational risk. | Measure stake share and service overlap. |
| Reward quality | Emissions can make early APY misleading. | Separate fees from incentive tokens. |
| Exit and claim stack | Multiple wrappers can complicate liquidity. | Map redemption order and failure treatment at each layer. |
Model the worst common-mode failure rather than summing independent probabilities. If one operator controls many services, losses are not independent.
Also consider governance risk: changes to accepted services, slashing conditions or upgrade logic can alter the risk of a position after capital has been committed.
Worked example and thought exercise
Suppose native staking yields 4% and restaking adds a displayed 3%. If 2 percentage points of the extra return are temporary token incentives, the durable incremental reward may be closer to 1% before fees and slashing risk.
If the same operator serves five additional protocols, a single compromised key or software stack could create losses across several commitments rather than one isolated failure.
Thought exercise: when does “capital efficiency” become economic rehypothecation rather than genuine diversification?
Common mistakes and practical workflow
- Comparing restaking APY with native staking without isolating incremental risk.
- Treating service and operator failures as independent.
- Ignoring multiple receipt-token and redemption layers.
- Assuming token incentives are durable service revenue.
Practical workflow
- Identify the underlying staked asset and every wrapper.
- List each service and its penalty/slashing conditions.
- Measure operator and software concentration.
- Separate service fees from incentive emissions.
- Stress a common-mode operator or governance failure.
✅ Knowledge checkpoint
- What extra economic function does restaking provide?
- Why can shared security create correlated losses?
- How should token incentives be treated when evaluating restaking yield?
- What should be mapped in a multi-layer staking/restaking receipt stack?
FAQs
❓ Is restaking the same as liquid staking?
No. Liquid staking tokenises a staked claim; restaking reuses economic stake to secure additional services. They can be combined.
❓ Why are rewards higher?
Additional rewards compensate for extra services, risks or temporary incentives.
❓ Can restaking increase slashing risk?
Yes, depending on the system, because additional commitments can introduce additional penalty conditions.
❓ Is shared security diversification?
Not necessarily. If many services depend on the same stake or operators, failures can become more correlated.
📋 Summary
Restaking extends staked capital across additional security commitments. The incremental reward is meaningful only when compared with added slashing conditions, operator concentration, wrapper complexity and common-mode systemic risk.
Want this in a personalised order?
Take the crypto assessment and get a custom path of 10 modules matched to what you already know. Free, no card required.
Build my path →