Restaking: reusing security, and stacking the risk
Restaking lets staked capital secure additional services for additional rewards. The same capital now backs several promises, which is precisely what makes the returns and the risks larger.
Reviewed by Kayla Peterson, DeFi Research Analyst · Last reviewed November 11, 2026

On this page
Restaking allows capital already staked to secure a blockchain to also back other services — oracle networks, bridges, data availability layers — and earn additional rewards for doing so. The appeal is obvious: the same capital works twice. The risk is the mirror image: the same capital can be penalised by several unrelated systems, and those penalties can arrive together.
What problem does it solve?
New networks and middleware need economic security, and bootstrapping it from scratch is expensive: you must attract capital, issue a token to pay for it, and hope the token holds value. Restaking lets them rent security from an existing pool of staked capital instead, paying rewards rather than building a validator set of their own.
For stakers, it converts idle security into a yield-bearing service. For the ecosystem, it lowers the barrier to launching services that need honest participants. Both are genuine benefits, and both depend on the penalties being real.
How does it work?
- You opt in, directing your staked position — or a liquid staking token representing it — to a restaking protocol.
- You choose operators, who run the software for the services you are backing.
- Each service defines its own conditions and penalties for failing them.
- Rewards flow from the services that are paying for security.
- Your capital remains subject to the base network's own rules as well.
What are liquid restaking tokens?
As with liquid staking, a token can represent a restaked position so it stays usable. That token now sits three layers deep: the underlying asset, the staking protocol, the restaking protocol — and often a fourth if it is then used as collateral somewhere. Each layer adds contract risk and a claim on the same underlying capital.
Why is correlated risk the real concern?
Restaked capital, restaking operators and the services they secure overlap heavily. A bug in widely used operator software, a mistake by a large operator, or a shared dependency failing can trigger penalties across several services simultaneously — precisely the scenario where the diversification implied by 'many services' turns out to be illusory.
| Layer | Adds | Failure mode |
|---|---|---|
| Base staking | Consensus rewards | Validator penalties where the network enforces them |
| Liquid staking | Liquidity, contract exposure | Contract exploit; discount to redemption value |
| Restaking | Service rewards, new slashing rules | Penalty from a service's conditions |
| Liquid restaking token | Usability, another contract | Exploit; depeg; liquidation if used as collateral |
Is the base chain at risk?
Restaking does not change consensus rules, so a failure in a restaked service cannot invalidate blocks or rewrite the chain. The concern raised by researchers is subtler and worth stating plainly: if enough stake is committed to arrangements with correlated risk, a large simultaneous loss could disrupt validation broadly, and social pressure to intervene at the base layer becomes a governance problem rather than a technical one.
How should you approach it?
- Treat the extra reward as payment for extra risk, and try to price it rather than accept it.
- Read each service's slashing conditions — they are the actual contract you are entering.
- Diversify operators, and prefer those with published infrastructure practices.
- Avoid stacking restaking on top of leverage; one adverse event then hits from two directions.
- Size the position for a total loss of that layer, since it is a young mechanism with limited history.
- Start from our guides to staking and liquid staking if any layer below this one is unfamiliar.
How do you evaluate a service before backing it?
Each service you opt into is a separate commitment with its own rules, and the rewards are usually presented together while the conditions are documented separately. Reading them individually is the work.
- What exactly triggers a penalty, and is it objective — a provable fault — or subject to interpretation?
- How large is the penalty relative to the reward being offered?
- Who can change the conditions after you have opted in, and is there a delay before changes take effect?
- How long has the service been live, and has any penalty ever been enforced?
- How much overlap does it share with the other services you back — same operators, same software, same dependencies?
A service that cannot answer the first question precisely is asking you to underwrite an undefined risk for a defined reward. That is not automatically a bad trade, but it is a different trade from the one the yield figure implies.
- 1. Proof of stake and validator penalties — ethereum.org
- 2. Staking overview — ethereum.org
- 3. Smart contract security — ethereum.org
Frequently asked
What is restaking?
Committing already-staked capital to also secure additional services, which pay rewards and impose their own penalty conditions on that capital.
Is restaking riskier than staking?
Yes. It adds contract risk and new slashing conditions defined by systems with far less operating history than the base chain, on top of the original staking exposure.
What is a liquid restaking token?
A transferable token representing a restaked position. It keeps the capital usable and adds another contract layer between you and the underlying asset.
Can restaking break the base blockchain?
It does not change consensus rules, so it cannot invalidate blocks. The concern is indirect: heavy correlated exposure among validators could cause broad disruption and difficult governance decisions.
How do I judge whether the reward is worth it?
Identify every layer between you and the underlying asset, name what each would have to do wrong, and ask whether the additional yield compensates for all of them together.

Mason Walker is an Ethereum & Layer-2 Editor at Crypto Almanac Daily, where he covers the rapidly evolving Ethereum ecosystem with a focus on staking, Layer-2 networks, rollups, protocol upgrades, and smart contract infrastructure. His reporting explores how Ethereum's technical innovations shape decentralized finance, tokenization, and Web3 applications. Mason specializes in breaking down complex protocol changes, network scalability solutions, validator economics, and the growing adoption of optimistic and zero-knowledge rollups into accessible, research-driven analysis. Before joining Crypto Almanac Daily, Mason covered blockchain infrastructure and emerging financial technologies, developing expertise in Ethereum's architecture and the broader smart contract ecosystem. His work combines technical accuracy with clear explanations, helping readers understand both the engineering behind blockchain networks and their real-world market implications. At Crypto Almanac Daily, Mason writes daily news, protocol deep dives, ecosystem updates, educational guides, and long-form research articles, providing readers with reliable insights into Ethereum's ongoing development and its role in the future of decentralized finance and digital assets.
This guide is educational and general in nature. It is not financial, investment, legal or tax advice, and it does not account for your circumstances. Crypto assets are volatile and you can lose the money you put in. See our editorial policy and methodology.


