Restaking in Crypto Explained: How It Differs From Liquid Staking
Restaking explained: how it reuses staked capital to secure additional services, where the extra yield comes from, the slashing and correlation risks, and how it differs from liquid staking.
Last updated: 29 July 2026
Restaking is the most interesting and most misunderstood idea in staking since liquid staking itself. The pitch is seductive: take capital you have already staked and use it a second time, earning additional yield without additional deposits. Something for nothing, apparently.
It is not something for nothing. Restaking is a real innovation with a real economic rationale, and the extra yield is compensation for a specific extra risk that most explanations skip past. This guide covers what restaking actually is, where the yield comes from, what can go wrong, and how it differs from the liquid staking many people confuse it with.
Educational only, not financial advice.
A quick recap: what staking does
On a proof-of-stake blockchain, validators lock up capital as a bond and are paid to produce and validate blocks honestly. If they misbehave, part of that bond can be destroyed. This penalty is called slashing, and it is what makes the security economic rather than merely aspirational: attacking the chain has to cost more than it could earn.
The staked capital is therefore doing one job: securing one network.
What is restaking?
Restaking lets already-staked capital be committed as security for additional services beyond the base chain. The same stake continues securing the underlying network while also backing other systems that need economic guarantees, and it earns fees from those systems on top of base staking rewards.
The problem it solves is genuine. Any new service needing its own economic security, an oracle network, a data availability layer, a bridge, a sequencer, faces a bootstrapping problem: it must attract billions in capital before anyone can trust it. Restaking lets these services rent security from an existing pool instead of building one from scratch.
That is the core insight. Restaking is a marketplace for economic security, with staked capital as the supply side and new protocols as the demand side.
What restaked capital actually secures
The services buying this security are usually called actively validated services. Typical examples include oracle networks needing honest price reporting, data availability layers, cross-chain bridges, rollup sequencers, and specialised co-processors. Each defines its own conditions for correct behaviour, and its own penalties for violating them.
Where the extra yield comes from
This is the question that matters, and the answer is unromantic: you are being paid to accept additional slashing conditions.
When you restake, you agree that your capital can be penalised not only for misbehaviour on the base chain but also for failures in each service you back. The additional yield is a risk premium for accepting those additional ways to lose money.
This reframes the proposition entirely. Restaking is not free extra return on idle capital. It is selling insurance: you collect a premium, and you pay out if the insured event occurs. Whether the premium is adequate depends on how well you understand the events you have underwritten, which is exactly what the marketing tends not to dwell on.
Restaking vs liquid staking
These are routinely conflated, including by people who should know better. They solve different problems.
| Liquid staking | Restaking | |
|---|---|---|
| Problem solved | Staked capital is illiquid | New services cannot bootstrap security |
| What you get | A transferable token representing your stake | Additional fees from services you secure |
| Added risk | Smart contract risk; the token can trade below the underlying | Additional slashing conditions per service |
| Extra yield source | None inherently; you can deploy the token elsewhere | Fees paid by the services being secured |
| Worst case | Token depegs or contract fails | Principal is slashed by a service you backed |
The clearest way to hold the distinction: liquid staking changes the form of your stake, restaking changes the job of your stake. Liquid staking makes a locked position tradable. Restaking puts the same capital to work securing more things, and exposes it to more ways of being penalised.
They also compose. Liquid restaking, where you restake and receive a liquid token representing that position, stacks both sets of risk in a single instrument. Convenient, and further from the underlying than most holders appreciate.
The risks, stated plainly
Compounded slashing exposure
Each service you back adds conditions under which your capital can be penalised. Back five services and you hold five independent sets of rules, each written by a different team, each with its own bugs. Your downside is not diversified by taking on more, it is accumulated.
Correlated failure
The systemic concern. If a large share of a network's stake is restaked across overlapping services, a single flawed service could trigger slashing across a meaningful fraction of validators simultaneously. That is a base-layer security event caused by something built on top of it.
This is why several researchers have argued for conservative limits on how much of a chain's security should be reused. Whether the incentives in practice respect those limits is an open question.
Opacity
Ask a restaker which services their capital backs, and what each can slash for. Many cannot answer, particularly when they hold a liquid restaking token that allocates on their behalf. Risk you cannot enumerate is risk you cannot price.
Contract risk on top
Restaking adds contract layers between you and your stake: the restaking protocol, each service's logic, and any liquid wrapper. Every layer is code that can fail independently of the base chain, which may be running perfectly while you lose funds anyway.
Where JewelSwap stands
To be direct: JewelSwap does liquid staking, not restaking. We are not going to blur that line to catch a trend.
Across MultiversX, Sui and Radix, JewelSwap's model is a dual-token liquid staking design. You deposit a native asset and mint a base liquid staking token, JWLSUI, JWLEGLD or JWLXRD. Protocol-Owned Liquidity means you can receive up to 1.1 minted per 1 deposited, while the base token remains 1:1 backed. Staking the base token gives you the appreciating S-variant, whose exchange rate rises daily as rewards accrue. Unstaking from the S-variant back to the base token is instant and free, and redeeming to the native asset carries a 10-day unbonding period during which you hold a transferable claim NFT.
The distinction matters for your risk. Your stake secures its own chain and nothing else. There are no additional slashing conditions from third-party services, because your capital is not underwriting any. What remains is ordinary staking risk plus smart contract risk, which is a narrower and more legible set than a restaked position carries.
If you want yield beyond base staking rewards, JewelSwap's route is to deploy your liquid staking token into yield farming or money markets, where the source of return is transparent: trading fees and borrower interest. Different risk, and one you can actually trace. Our liquid staking guide covers the full model.
Should you restake?
A reasonable framework:
- Can you name every service your capital secures? If not, you cannot assess the risk you hold.
- Do you know the slashing conditions for each? Vague reassurance that slashing is "rare" is not a risk assessment.
- Is the premium worth it? A few extra percentage points against a tail risk of losing principal is a trade you should price deliberately.
- How many layers deep are you? Liquid restaking tokens sit several contracts away from the underlying stake.
- Would a failure be survivable? Slashing hits principal, not just yield.
Restaking is a legitimate mechanism doing real work in the security market. It is also frequently sold as extra yield with the risk transfer left unmentioned. Both things are true.
Frequently asked questions
What is restaking in crypto?
Restaking lets capital already staked on a proof-of-stake network be committed as security for additional services, such as oracle networks, bridges or data availability layers. The stake keeps securing the base chain while also backing those services, earning their fees on top of base staking rewards.
How is restaking different from liquid staking?
Liquid staking gives you a transferable token representing a staked position, solving illiquidity. Restaking commits the same capital to secure additional services, solving bootstrapping for new protocols. Liquid staking changes the form of your stake; restaking changes its job and adds slashing conditions.
Where does restaking yield come from?
From fees paid by the services your capital secures. It is a risk premium for accepting additional slashing conditions, not free return on idle capital. Economically it resembles selling insurance: you collect a premium and pay out if the insured event occurs.
Is restaking safe?
It carries meaningfully more risk than plain staking. Each service adds independent slashing conditions, correlated failures could affect many validators at once, and liquid restaking tokens add further contract layers. The relevant question is whether the extra yield compensates for risks you can actually enumerate.
What is slashing?
The destruction of part of a validator's staked capital as a penalty for misbehaviour, such as going offline or signing conflicting blocks. It makes proof-of-stake security economic: attacking the network must cost more than it earns. Restaking extends slashing exposure to additional services.
Does JewelSwap support restaking?
No. JewelSwap offers dual-token liquid staking on MultiversX, Sui and Radix, not restaking. Your stake secures its own chain and takes on no third-party slashing conditions. Additional yield comes from deploying your liquid staking token into yield farming or money markets, where the return source is transparent.
Keep reading
