Restaking in 2026: LSTs, LRTs, Yield Stacking, and Leverage Risk
A precise guide to liquid staking and restaking: how LSTs and LRTs differ, where yield comes from, how leverage changes liquidation risk, and what reward claims require verification.
TLDR: Restaking can stack base staking yield, restaking/AVS economics, protocol incentives, and DeFi yield—but those are separate return sources with separate risks. Do not treat a points balance as APY, do not combine unrelated Solana LST or synthetic-dollar products into “EigenLayer restaking,” and do not use leverage without modeling health factor, borrow cost, depeg risk, and liquidation paths.
What Is the Difference Between Staking, Liquid Staking, and Restaking?
These terms are often collapsed into one “yield stack,” but they describe different systems.
Native staking commits an asset to a network's validator/security mechanism.
Liquid staking gives the depositor a transferable token representing a staked position, usually called an LST. The token can then be used elsewhere in DeFi.
Restaking extends economic security from already-staked assets into additional services or validation systems. Liquid restaking protocols can issue an LRT that packages the underlying staking/restaking position into a transferable token.
The distinctions matter because risk compounds as assets move through more layers.
| Layer | Example risk category | Typical return source |
|---|---|---|
| Base asset | ETH price / chain risk | None by itself |
| Native staking | validator/slashing/operational risk | staking rewards |
| LST | smart-contract + peg/liquidity risk | staking rewards |
| Restaking / AVS | additional slashing / protocol risk | AVS or restaking economics |
| LRT | issuer, accounting, withdrawal, liquidity risk | packaged staking/restaking returns |
| Lending / LP layer | liquidation, oracle, IL, borrow risk | lending or trading fees |
| Incentive program | eligibility and token uncertainty | points / rewards if actually distributed |
A “four-layer yield” is not one yield source. It is four contracts and risk assumptions stacked together.
Which Protocols Belong in the Same Category?
FarmDash tracks several protocols that may appear near each other in a portfolio but are not equivalent.
Ether.fi and Renzo are examples of liquid-restaking-oriented products associated with Ethereum restaking infrastructure.
EigenLayer is restaking infrastructure rather than simply another LST issuer.
Ethena is a synthetic-dollar / yield system, not an Ethereum restaking protocol.
Sanctum is part of the Solana liquid-staking ecosystem, not an EigenLayer-style Ethereum restaking layer.
Putting all four into one “restaking leaderboard” creates misleading comparisons. Research should compare like with like first, then compare portfolio roles second.
Where Does Restaking Yield Come From?
Separate each component explicitly.
1. Base staking return
The underlying staked ETH can earn protocol staking rewards. The rate changes with network conditions and validator economics.
2. Restaking or service rewards
Additional services may compensate economic security. The form, timing, and amount of that compensation depend on the actual restaking protocol and service.
3. Protocol incentives
An LRT issuer may run a points, loyalty, referral, or token program. Those units are not the same thing as realized yield unless a conversion and distribution are actually defined.
4. Secondary DeFi yield
The LST/LRT may be supplied to lending markets, LPs, vaults, or structured products. That can add yield while also adding another smart contract, oracle, liquidity, or leverage dependency.
A useful dashboard should keep these sources separate rather than adding a speculative future token to APY.
What Is the Correct Way to Evaluate an LST or LRT?
Before comparing headline yield, inspect:
- redemption path — can the token be redeemed directly, queued, or only sold on a market?
- market depth — what happens to price at the size you need to exit?
- exchange rate — rebasing, share-price appreciation, or another accounting model?
- validator / operator design — who controls staking operations?
- slashing exposure — what events can reduce principal?
- restaking exposure — which services add risk?
- oracle dependencies — how does lending collateral value the token?
- withdrawal timing — what delay applies under normal and stressed conditions?
- contract upgradeability — what roles can change implementation or parameters?
- reward evidence — are points or incentives currently documented by the issuer?
The “highest APY” number is rarely enough.
What Happens When You Add Leverage?
A common leveraged loop is conceptually:
- acquire an LST or LRT;
- post it as collateral;
- borrow another asset;
- convert the borrowed asset into more collateral;
- repeat.
That increases exposure, but it also reduces the distance between the current account state and liquidation.
For a leveraged loop, track:
[ ext{Net carry} = ext{staking/restaking yield}
- ext{secondary yield}
- ext{borrow cost}
- ext{swap/slippage cost}
- ext{expected depeg/liquidation cost} ]
Points should be shown separately because their monetary value may be unknown.
Health factor is not a static safety guarantee
A health factor can deteriorate because:
- collateral price falls;
- borrowed asset rises;
- collateral depegs from its reference asset;
- borrow APY increases;
- oracle parameters change;
- liquidation thresholds change;
- accrued interest grows debt;
- liquidity vanishes and deleveraging becomes expensive.
A threshold that looks safe in calm markets can disappear quickly during a correlated exit.
What Is Depeg Risk?
An LST or LRT can trade below its expected redemption value when holders need liquidity faster than the redemption path can provide it.
If the token is also collateral, a market depeg can cause liquidations even when the underlying staking position remains economically intact.
That creates two prices to monitor:
- the protocol's redemption/accounting value;
- the liquid market price used by traders and potentially by oracles.
The gap between them is not free arbitrage unless the redemption timing, queue, fees, counterparty risk, and capital lock-up are all modeled.
Are Points the Same as Yield?
No.
A points program can be economically interesting, but points are not APY unless there is a defined, realizable conversion.
Represent points with:
- current program status;
- first-party source;
- accrual rule if published;
- season or deadline if published;
- exclusions if published;
- conversion unknown when unpublished.
Do not turn historical airdrops into an assumed future return.
How Should You Compare Restaking Opportunities?
A useful comparison matrix looks like this:
| Dimension | Question |
|---|---|
| Base return | What part comes from native staking? |
| Additional security | What restaking/slashing exposure exists? |
| Token liquidity | How deep is the LST/LRT market? |
| Redemption | How and when can principal leave? |
| DeFi composability | Where can the token be used as collateral or LP inventory? |
| Leverage | What liquidation/oracle dependencies appear? |
| Incentive evidence | Is a current points/reward program actually documented? |
| Contract risk | Upgrade keys, audits, incidents, dependencies? |
| Operational complexity | How many protocols must work for the stack to unwind cleanly? |
The best portfolio fit is the one whose risk sources you understand and can monitor—not necessarily the one with the largest displayed percentage.
What Should an Agent Monitor?
For a restaking position, an agent should track:
- token balance and share/exchange rate;
- market price versus redemption value;
- protocol and market liquidity;
- lending health factor;
- borrow APY;
- oracle price;
- withdrawal queue status;
- current program status;
- data freshness and confidence;
- all dependencies required to unwind.
When a key upstream feed is stale, the agent should reduce confidence or refuse a state-changing recommendation rather than extrapolating silently.
What Are the Main Hazards?
- Smart-contract risk across each layer.
- Slashing risk from staking/restaking conditions.
- Liquidity and depeg risk in LST/LRT markets.
- Oracle risk when tokens are used as collateral.
- Liquidation risk from leverage.
- Borrow-rate risk that destroys positive carry.
- Withdrawal-queue risk during stress.
- Concentration risk when several “different” products share the same underlying validator, oracle, or liquidity venue.
- Incentive uncertainty when points have no guaranteed conversion.
Frequently Asked Questions
Is Ethena a restaking protocol?
No. Ethena can sit near restaking assets in a yield portfolio, but its synthetic-dollar design and risk model are different. It should not be counted as an EigenLayer-style restaking protocol.
Is Sanctum Ethereum restaking?
No. Sanctum belongs to the Solana liquid-staking ecosystem. It has different underlying assets, validators, liquidity, and protocol mechanics.
Does an LRT point balance count as APY?
Not unless the points have a defined and realizable conversion. Until then they are an incentive unit, not realized yield.
Is leveraged restaking safe if the health factor is above 1?
No. A health factor above the liquidation threshold only describes the current state under the current oracle and parameters. It can deteriorate rapidly.
Use FarmDash as a Control Surface
Use FarmDash to organize wallet context, protocol evidence, and risk signals. Verify current incentive terms and live market conditions before treating any restaking or points strategy as actionable.