LRT vs LST vs Native Staking: Rewards, Risks, and Trade-offs

What is the difference between native staking, an LST, and an LRT?

The short version is that native staking locks ETH into Ethereum's validator system, an LST represents a claim on staked ETH, and an LRT represents a claim on assets that are usually staked and then restaked to provide security for additional services. The three labels describe different layers, not three guaranteed levels of return.

With native staking, a validator deposits ETH, runs validator software, proposes or attests to blocks, and earns protocol rewards for doing the job correctly. A solo validator generally requires 32 ETH, although staking providers can handle the technical work or pool deposits from smaller holders. The reward source is relatively direct, but the capital is less flexible and operational mistakes can reduce returns.

An LST, or liquid staking token, is issued by a staking protocol when ETH is staked on behalf of users. Examples include stETH from Lido and rETH from Rocket Pool. You can usually transfer, lend, trade, or use the token in DeFi rather than waiting for the underlying ETH to exit staking. That convenience creates new dependencies on the issuer, validators, contracts, liquidity, and the token's accounting method.

An LRT, or liquid restaking token, adds another use for staked ETH. The underlying ETH or LST may continue earning Ethereum staking rewards while being committed to extra networks called actively validated services, or AVSs. The extra reward is compensation for extra duties and extra failure modes. It is not a free second yield layer.

Risks come before rewards

The popular strategy of stacking native staking, an LST, and an LRT can look like a simple way to maximize yield. In practice, each layer adds a fresh trust and failure surface. An LRT position may depend on the Ethereum protocol, the staking provider, an LST contract, a restaking contract, an operator, one or more AVSs, price oracles, bridges, and DeFi venues where the token is used.

Those risks can interact. A smart-contract exploit may force withdrawals or freeze a token. A market panic can push an LST or LRT below the value of its underlying assets. A validator or operator failure can create penalties. If many positions rely on the same operator, client, bridge, oracle, or LST, the losses can become correlated instead of independent.

Slashing is a protocol penalty for serious validator misbehavior, such as signing conflicting messages. It is different from ordinary downtime, which usually causes missed rewards or smaller penalties, but a large incident can involve both an immediate penalty and a forced exit. Restaking can increase the consequences because an operator may be responsible for duties outside Ethereum's base consensus.

There are real reminders that staking infrastructure can fail. In 2023, Lido disclosed that 20 validators operated by one provider were slashed after infrastructure and signing-key issues. The loss was small relative to the system, but it showed that a liquid token can spread an operational event across many holders. Ethereum's early beacon-chain period and the 2020 Medalla testnet failure also exposed the danger of correlated validator outages, even though that testnet event was not a mainnet customer wipeout.

Restaking has produced serious near-miss scenarios as well. Rapid growth in deposits, complex operator arrangements, contract upgrades, and integrations can concentrate risk before users understand it. A protocol may advertise that slashing is limited or not yet active, but that changes the current loss mechanism rather than removing economic risk. Governance, withdrawal restrictions, depegging, and a bad integration can still hurt holders.

Native ETH staking is the baseline yield, not a guarantee

Native staking is the cleanest benchmark for comparing other strategies. A validator earns rewards from Ethereum's protocol for participating correctly, plus possible execution-layer income from proposing blocks and including transactions. The amount varies with the total amount of ETH staked, validator performance, network activity, and the frequency and value of block proposals.

People sometimes call this the native staking yield floor. That phrase should be handled carefully. It means a relatively direct baseline before adding LST, LRT, leverage, lending, or incentive rewards. It is not a guaranteed minimum return. A validator can earn less through downtime, client problems, missed duties, penalties, fees charged by a provider, or changes in Ethereum's issuance and transaction activity.

Capital access is another defining feature. A validator can request an exit, but the ETH does not necessarily become available immediately. Ethereum uses an exit queue to manage how quickly validators leave, and the waiting time depends on the number of other validators exiting. After the validator exits, withdrawals and provider processing can add further timing considerations. A liquid token may trade immediately, but that is market liquidity, not the same thing as a guaranteed redemption window.

Native staking also has a smaller software stack than a typical LRT strategy. You still face custody, validator, client, key-management, and provider risks, but you are not automatically relying on an extra restaking contract, AVS rules, or LRT market-making pool. For a long-term ETH holder who does not need to move the position, this simpler setup can be a meaningful benefit.

The trade-off is that native staking may be inconvenient. A solo validator requires technical competence, reliable hardware or cloud infrastructure, secure key handling, and monitoring. A custodial service reduces some operational work but adds counterparty and provider risk. A pooled staking arrangement improves accessibility, yet it moves you toward the LST model and its protocol-specific risks.

How LSTs add liquidity and accounting choices

An LST turns a less liquid staking position into a transferable token. Instead of waiting for native ETH to complete the exit process, you can sell the LST or use it as collateral, subject to available market liquidity and the rules of the venue. That flexibility can be valuable when your holding period is uncertain, but it also introduces a market price that can diverge from the value of the underlying staked ETH.

LSTs generally use one of two accounting styles. A rebasing token changes the token balance in a wallet as staking rewards accrue. stETH is the familiar example. Your unit balance can increase over time, although the market price may still move independently. A wrapped or non-rebasing token keeps the unit balance stable while its exchange rate against the underlying asset changes. wstETH and rETH use versions of this approach.

Neither method makes the return higher by itself. Rebasing can be easier to understand if you watch your balance, but some DeFi applications do not handle changing balances well. Wrapped-token accounting can work better for integrations, but you must check the exchange rate and not mistake a stable token count for a stable dollar value. In both cases, fees, validator performance, and market conditions affect what you can redeem or sell.

The central LST risk is not only whether validators earn rewards. It is whether the token remains trusted, liquid, and correctly connected to its underlying assets. A smart-contract bug, governance failure, bad oracle, custody problem, or loss of confidence can cause an LST to trade at a discount. Arbitrage can help restore the price over time, but arbitrage is not a promise and can fail during a market shock.

Protocol concentration matters too. A large provider may have strong infrastructure and deep liquidity, but a large share of the network can create systemic dependence. Lido's LDO token governs parts of the protocol's parameters and ecosystem, but holding LDO does not turn stETH into a risk-free asset or give every holder direct control over validator operations. Governance can change, and token ownership is not the same as an insurance policy.

Before using an LST in DeFi, check whether the application recognizes the exact token, how it values the token, and what happens if the token trades below its underlying value. A lending market can liquidate collateral at an unfavorable price even when the underlying staking system has not been hacked. Smart-contract composability creates opportunities, but it also links separate failure modes.

How LRTs create a second reward and risk layer

Restaking lets already staked ETH or an LST support additional services. These services may need operators to verify data, run middleware, provide availability, or enforce other rules. An LRT packages exposure to that activity into a transferable token, so the holder does not have to manage every operator relationship directly.

The LRT headline yield can combine several components: native ETH staking rewards, fees from restaking services, protocol incentives, trading income, and points. These components are not equally durable. Native staking rewards come from Ethereum's rules, while AVS payments depend on actual demand and fee arrangements. Incentives can be reduced or discontinued, and points may never become transferable or valuable.

The AVS layer changes the meaning of slashing. A validator can remain honest under Ethereum's consensus rules while an operator makes a mistake under another service's rules. The loss might be imposed through a restaking contract, an operator agreement, or an AVS mechanism. The exact conditions depend on the design, and users must read the current terms rather than rely on a general statement that restaking is safe.

This is why an 8% LRT headline should not be compared directly with a 3% or 4% native staking rate. The difference is partly a risk premium, partly a subsidy, and possibly partly a temporary accounting effect. You should ask what must go wrong for the extra return to disappear, what losses you could suffer, whether the token can be redeemed, and who receives the fees before treating the number as income.

There can also be uncertainty about who carries a loss. Some systems may socialize penalties across a pool. Others may assign them to a particular operator, token, vault, or strategy. A stated cap on slashing does not remove the chance of a smart-contract exploit, an oracle error, a bridge failure, or an LRT discount. It only describes one part of the risk design.

For a deeper comparison of major restaking architectures and their trade-offs, see EigenLayer vs Symbiotic: How Restaking Models Differ. The key point is that the platform name is not enough. You need to understand which contracts hold assets, which operators perform work, which AVSs can impose penalties, and how withdrawals work in the version you are using.

Why points are not the same as staking rewards

Points programs are designed to encourage deposits, usage, referrals, or participation before a protocol has finalized its incentive system. They may later be linked to a token distribution, but that outcome is not guaranteed. A points balance is not ETH, not a contractual claim on revenue, and not necessarily transferable.

Points also make comparisons harder. A dashboard may display a high projected annualized rate based on points, but the calculation can depend on an assumed future token value, a changing points schedule, or a deposit multiplier. If the protocol changes the rules, adds more participants, delays a launch, or excludes certain wallets, the expected value can fall to zero.

Users can take more risk while chasing points. They may move an LST through several contracts, borrow to increase deposits, use a bridge, or provide liquidity for a thinly traded LRT. Each action can add smart-contract, liquidation, market, or custody risk. The points may be the least durable part of the strategy while the losses remain immediate and real.

Evaluate points as a speculative promotion, not as a guaranteed return. Separate the native staking reward from the restaking fee, the protocol subsidy, and the estimated points value. If you cannot calculate your result without assuming a future token price, the number is a scenario, not a yield quote.

Which option fits your holding horizon?

Your time horizon and liquidity needs usually matter more than the highest displayed annual percentage. A strategy that is reasonable for a holder who can wait through an exit queue may be unsuitable for someone who might need ETH this week. Your tolerance for contract reviews, protocol governance, token discounts, and operational complexity should also affect the choice.

Long horizon and low need for liquidity

Native staking can fit a holder who expects to keep ETH for years, accepts the exit queue, and can manage or outsource validator operations. The simpler reward source makes it easier to monitor what you are actually earning. A reputable staking provider may be practical for smaller holders, but outsourcing does not eliminate provider, custody, or fee risk.

Medium horizon with a need to move or use the position

An LST can fit someone who wants staking exposure while preserving the ability to trade or use the position in DeFi. The cost is exposure to the issuer, token liquidity, contract security, and price discounts. Keep a buffer rather than assuming every LST can be exchanged for ETH at a one-to-one market price during stress.

Shorter horizon or uncertain liquidity needs

Restaking through an LRT is difficult to justify when you may need the capital quickly. Even if the LRT trades continuously, its price can fall below the value of the underlying assets, and withdrawals can depend on queues or contract rules. A short holding period also gives temporary points programs less time to compensate for fees and price volatility.

High complexity tolerance and a defined risk budget

An LRT may fit only a holder who understands the specific contracts, operators, AVSs, withdrawal process, and liquidity venues, and who can afford a loss beyond ordinary ETH price volatility. Layering an LST and an LRT is not automatically diversification. If both depend on the same validator provider, bridge, oracle, or LST, the risks may move together.

One practical approach is to choose a maximum amount you are willing to expose to experimental restaking and keep the rest in a simpler form. Do not fund the riskier layer with borrowed money simply because its displayed yield is higher. Leverage can turn a temporary discount or delayed withdrawal into a forced loss.

How to compare the real return before choosing

Start with the net return, not the promotional rate. Subtract protocol fees, validator fees, borrowing costs, gas, trading spreads, bridge charges, and any expected tax or accounting burden that applies to you. Then consider whether the displayed reward is paid in ETH, another token, points, or a mixture. A reward that changes in value is not equivalent to a fixed ETH return.

Next, map the dependencies. For native staking, review the validator or provider, key management, fee policy, client diversity, and exit process. For an LST, add the token contract, redemption mechanism, reserve or validator disclosures, market liquidity, and oracle behavior. For an LRT, add every relevant operator, AVS, restaking contract, withdrawal rule, and slashing condition.

Look for the uncomfortable details in documentation. Who can pause deposits or withdrawals? Can governance upgrade the contract? Is there an emergency committee? What happens if an operator is offline? Which losses are absorbed by the protocol, the operator, or token holders? Is insurance available, and does it cover smart-contract exploits, slashing, depegging, or only a narrow event?

Review liquidity under stress rather than at a normal market hour. A deep pool today can become shallow if many holders try to exit together. A quoted exchange rate may come from an oracle or an illiquid pool rather than a guaranteed redemption. Test the withdrawal path with a small amount when possible, and keep records of which token you hold, where it is held, and what it represents.

Finally, compare the extra return with the extra risk premium you would personally require. If an LRT pays a few percentage points more but exposes you to several unaudited contracts and unclear slashing rules, the difference may not compensate you. There is no universal correct answer, and the safest choice for one holder can be too conservative or too complex for another.

Stay ahead of staking and restaking risk

Native staking, LSTs, and LRTs can all change as quickly as their contracts, validator sets, reward rules, and liquidity conditions change. Tracking those developments manually is difficult, especially when a headline yield hides whether the return comes from ETH rewards, temporary incentives, points, or leverage. Zippfeed brings together relevant ETH, LDO, staking, and restaking news with sentiment scoring marked bullish, neutral, or bearish, plus an importance rating, so you can distinguish routine updates from events that may affect your risk assessment.