What Is Liquid Staking?

Introduction

Liquid Staking is a way to stake assets in a proof-of-stake network without giving up the ability to use or trade the value you staked. That sounds almost contradictory at first. Staking is supposed to lock capital so the network can rely on it, while liquidity is supposed to let capital move freely. Liquid staking exists because users want both: the yield and security role of staking, and the flexibility of a transferable asset.

That tension is the key to understanding the whole topic. In ordinary staking, your tokens become economically less mobile for some period of time. Sometimes there is a minimum stake, sometimes you need validator infrastructure, and almost always there is some delay to exit. Liquid staking takes that locked position and creates a new token that represents it. You no longer move the original staked asset directly; instead, you move the receipt for that asset.

This is why liquid staking has become important across several ecosystems. On Ethereum, pooled staking services emerged because the protocol does not natively let many small holders combine funds inside the protocol itself to reach the 32 ETH validator threshold. On Solana, Marinade issues mSOL, a token representing a stake position in its pool. In each case, the same basic idea appears: convert a hard-to-move staking claim into a token that can circulate.

The benefit is obvious. The cost is subtler. Once a staking position becomes a token, it inherits the advantages of markets and composability, but also their fragility. The token can trade at a discount, be used as collateral, become leveraged, or concentrate power in a few protocols. So liquid staking is not just a convenience feature. It changes the shape of staking itself.

Why does liquid staking exist and what problems does it solve?

Proof-of-stake systems ask participants to put assets at risk in order to help secure the network. That creates an alignment mechanism: if validators behave correctly, they earn rewards; if they fail badly enough, they can be penalized. But this mechanism works partly by making the stake sticky. Capital cannot be perfectly free to move every second if it is also meant to back consensus commitments.

For users, that stickiness creates three practical frictions. The first is size. Some systems or service models require a meaningful minimum deposit. Ethereum solo staking famously requires 32 ETH per validator. The second is operations. Running validators means maintaining hardware, software, and keys, or trusting someone else to do it. The third is time. Even when withdrawals are supported, unstaking is rarely instantaneous. Queue limits and throughput rules exist to protect the network, which means exits can be delayed.

Liquid staking is a response to those frictions. It pools deposits, delegates validator operation to a service or set of operators, and gives depositors a transferable token representing their claim on the pooled stake. Economically, the service is saying: you do not need to hold the original locked position directly; you can hold a tokenized claim on it instead.

That claim can then be traded or posted as collateral. This is the real breakthrough. The token is not merely a UI abstraction for your stake. It is a way to separate two roles that were previously fused together: the locked capital that backs validators, and the movable asset that users want in their portfolio.

How does liquid staking convert locked stake into a tradable token?

At a high level, liquid staking has a simple structure. A user deposits the base asset into a protocol or service. The protocol stakes that asset, directly or through operators. In exchange, the user receives a liquid staking token, often abbreviated as an LST, that represents a claim on the underlying staked position and its rewards.

The exact mechanics vary, but the invariant is the same: there is some pool of underlying staked assets, and there is some token whose value is supposed to track a pro rata claim on that pool. If the underlying pool earns rewards, the token holder should benefit. If the pool suffers penalties or slashing, the token holder should bear that loss too. Without that link, the token would not be a meaningful representation of stake.

What changes across designs is how that link is expressed. Some tokens are rebasing. In a rebasing design, the number of tokens in your wallet changes over time to reflect rewards. Lido’s stETH works through an internal shares system in which a user’s balance is computed from their shares and the protocol’s total pooled ether. As pooled ether changes, balances change too. This is why stETH does not behave like a perfectly ordinary ERC-20 in every respect: balances can rise without normal transfer activity.

Other designs are non-rebasing. In that model, your token count stays fixed, but each token gradually becomes redeemable for more of the underlying asset. Marinade’s mSOL on Solana is a clear example. Its on-chain price is defined by the ratio total_staked / tokens_minted, so rewards show up as an increasing value per token rather than an increasing token balance.

These two models feel different to users, but economically they are solving the same accounting problem. You need a way for rewards and penalties at the validator layer to flow through to token holders without requiring every holder to manually claim and reinvest every epoch.

Example: How liquid staking works for a small ETH holder

Imagine Alice has 5 ETH and wants staking rewards, but she does not want to run a validator and cannot solo stake anyway because she does not have 32 ETH. She deposits her ETH into a liquid staking protocol. The protocol combines Alice’s ETH with deposits from many other users, and that pooled capital is assigned to validators run by a set of operators.

In return, Alice receives a liquid staking token. Depending on the design, she may receive exactly 5 units of a token whose balance later rebases upward, or she may receive a token whose quantity stays fixed while its redemption value slowly increases. Either way, Alice now holds a tokenized claim on the pooled stake.

A few things can happen next, and each shows why liquid staking matters. If Alice simply holds the token, she is economically similar to a passive staker: rewards flow through, minus protocol or operator fees. But if she needs liquidity, she does not necessarily wait for validator withdrawals. She can sell the token on a market to someone else. If she wants to borrow against it, she may use it as collateral in DeFi. In that moment, the original staked ETH remains committed to validators, but the economic exposure to that stake has moved to a new holder or been embedded in a more complex position.

This is the core trick. The network sees capital still backing validators. Users see a token that behaves like an asset they can move. Liquid staking works because those two perspectives can be separated, at least most of the time.

Pooled staking vs. liquid staking: what’s the difference?

People often blur pooled staking and liquid staking, and the confusion is understandable. Many liquid staking systems are also staking pools. But the concepts are not exactly the same.

Pooled staking means many users combine funds so staking becomes accessible below the native threshold or without running infrastructure themselves. That pool may or may not issue a transferable token. If it does not, the user has pooled access to staking, but their position may still be operationally or economically illiquid.

Liquid staking adds the missing piece: a tokenized claim that can circulate independently of the underlying staking position. Ethereum.org’s explanation of pooled staking makes this distinction clearly. Some pools issue tokens representing the staked ETH and rewards, enabling use in DeFi; others are mediated more directly and require more trust, without the same tokenized liquidity.

So the organizing principle is this: pooled staking solves access, while liquid staking solves access plus mobility. The second is strictly more ambitious, and therefore usually comes with more design complexity.

Why you can’t instantly withdraw the underlying asset from liquid staking

A common misunderstanding is that liquid staking makes staking itself liquid at the protocol level. It usually does not. What it creates is a liquid market around an illiquid underlying process.

That distinction matters most when users want the base asset back. There are generally two ways out. The first is a protocol-level redemption path: you hand back the liquid staking token and wait for the protocol to source the underlying asset through its withdrawal machinery. The second is a market exit: you sell the token to someone else for the base asset or for another asset.

These paths behave differently under stress. A market sale can be fast, but only at whatever price buyers are willing to pay. A protocol redemption aims at the underlying value, but it is constrained by the staking system’s own withdrawal rules and queues.

Ethereum is a good example of why that matters. Validator withdrawals became natively supported with the Capella upgrade, and the execution layer now includes consensus-validated withdrawal operations. But those withdrawals are not arbitrary, user-triggered bank-style payouts. The consensus layer computes expected withdrawals, limits how many can be included per payload, and sweeps through validators in a deterministic way. In other words, the protocol is designed to make withdrawals possible without letting mass exits destabilize validator accounting.

That means a liquid staking token on Ethereum can be redeemable, but not infinitely or instantly redeemable. Services such as Lido therefore distinguish between on-protocol withdrawal queues and secondary-market swaps. That is not an implementation detail. It is a consequence of the fact that the underlying stake remains embedded in a consensus system with throughput limits.

The same logic appears elsewhere. In Cosmos chains, the staking module explicitly models unbonding as a time-delayed process, with queue semantics and an UnbondingTime parameter. Delegator shares there are just internal accounting units, not fungible transferable assets. A liquid staking design built on top has to wrap those delayed, non-fungible staking rights into something fungible and tradable. The wrapper can hide the waiting from the user only if a market or reserve absorbs it.

What determines the price of a liquid staking token?

A liquid staking token is often spoken of as if it were simply “staked ETH in token form” or “staked SOL in token form.” That shorthand is useful, but incomplete. The token’s value comes from a bundle of claims and assumptions.

At minimum, the token depends on the underlying staked assets and rewards. But it also depends on the correctness of the smart contracts, the honesty and competence of validator operators, the accounting method that maps underlying stake to token balances, and the exit path that turns the token back into the base asset. If any of those layers fail, the token can deviate from the underlying asset economically even if the idea is sound in principle.

This is why prices on secondary markets can diverge from the protocol’s internal accounting value. Marinade’s documentation makes the distinction explicitly: mSOL has a protocol-computed “true price,” but it can trade at a different price on DEXs if the market pair is unbalanced. That difference is not a contradiction. It reflects the fact that one number is a claim on underlying pool value, while the other is a market-clearing price under current liquidity conditions.

The same is true for stETH. In calm conditions, users expect it to stay close to ETH because each token represents staked ETH plus accrued rewards. But if many holders want immediate ETH and the redemption path is slow, then the market price can fall below ETH. The token is still linked to staked ETH, but not in the sense of a perfect one-for-one cash equivalent.

How does liquid staking interact with DeFi and create leverage?

Once a staking claim becomes a token, DeFi will treat it like collateral, inventory, or funding material. That is almost inevitable. The token has yield, it is transferable, and it usually tracks a major base asset. Those are exactly the properties that make an asset attractive in lending markets, AMMs, and structured positions.

This is one reason liquid staking grew so quickly. Instead of choosing between earning staking rewards and keeping assets economically useful, users could try to do both. Ethereum.org notes that staked-ETH tokens can be used as DeFi collateral and swapped quickly between raw ETH and yield-bearing products. That extra utility is not peripheral to liquid staking’s success. It is central.

But here the mechanism that creates convenience also creates leverage. A user can deposit ETH, receive an LST, use the LST as collateral, borrow more ETH, restake it, and repeat. Research on stETH leverage staking describes exactly this loop across protocols like Lido, Aave, and Curve. The appeal is straightforward: if borrowing costs stay below staking-linked returns, the strategy can increase yield. The danger is equally straightforward: if the LST price falls or liquidity disappears, liquidations can force sales into an already stressed market.

This is why liquid staking should not be viewed only as a staking primitive. It is also a collateral primitive. Once it plays that role at scale, its risks stop being isolated to stakers and start affecting lending markets, liquidations, and broader DeFi solvency.

What are the different risks of liquid staking?

It helps to separate liquid staking risks by mechanism rather than mixing them together.

The first category is protocol and implementation risk. If a liquid staking service uses smart contracts, those contracts can contain bugs or design flaws. If the system depends on off-chain actors such as oracles or committees, they can misreport, fail, or be captured. Lido’s own documentation emphasizes that its accounting and oracle subsystems are critical to correct exchange-rate and reward accounting. Even audited systems remain exposed to residual risk.

The second category is validator and staking risk. Liquid staking does not remove the economics of proof of stake. Validators can underperform, miss rewards, or be slashed. If failures are correlated across many validators in the same service, losses can propagate to all token holders. The token is liquid, but the underlying activity is still staking.

The third category is liquidity and market risk. An LST may be redeemable in principle but trade at a discount in practice. This can happen because the underlying withdrawal path is slow, because market depth is thin, or because large holders need immediate exits. The 2022 stETH discount episode is the clearest widely cited example: the token’s market price diverged sharply from ETH under stressed conditions as selling pressure hit a relatively thin liquidity environment.

The fourth category is composability risk. Once the token is used across lending, leverage, and derivatives, local problems become system-wide problems. A modest depeg can trigger liquidations; liquidations create selling pressure; selling pressure widens the depeg. Research on leverage staking argues that this feedback loop can amplify contagion across protocols.

The fifth category is centralization risk. This one is structurally different because it affects not only token holders, but potentially the underlying blockchain. If a few liquid staking providers accumulate too much stake, they can concentrate validator power. Ethereum.org warns that staked-ETH tokens can produce cartel-like outcomes in which large amounts of staked ETH sit under a few organizations, creating conditions for censorship or value extraction. This is not merely a business concentration concern. In proof of stake, concentrated stake can alter the decentralization and neutrality of consensus itself.

How liquid staking can concentrate power and threaten decentralization

Liquid staking makes staking easier, and easier systems tend to attract more deposits. That sounds harmless until you remember what staking weight means in a proof-of-stake system. More deposits do not just mean more assets under management. They mean more influence over block production and network security.

So there is a built-in tendency toward concentration. Users often prefer the largest pool because it feels safer, has the deepest liquidity, and integrates most broadly across DeFi. Those advantages can reinforce themselves. Better liquidity attracts more users; more users deepen liquidity; deeper liquidity makes the token more useful as collateral; that usefulness attracts still more users.

This positive feedback is efficient from the user’s perspective but dangerous from the network’s perspective. A protocol can become systemically important both as a financial intermediary and as a large coordinator of validators. Rocket Pool’s positioning as a decentralized liquid staking protocol matters in this context because design choices around operator participation, permissioning, and node access are not cosmetic. They are attempts to resist the concentration pressure inherent in the product itself.

There is no perfect solution here. Liquid staking exists because users want convenience and liquidity; decentralization often requires fragmentation, redundancy, and a willingness to avoid the dominant option. That means some of the healthiest outcomes for the network may feel less frictionless for the user.

How to evaluate whether a liquid staking service is trustworthy

For a user or integrator, the important question is not simply whether a token is popular. It is whether the system preserves the link between token and underlying stake under realistic stress.

That depends on several concrete mechanisms. How are deposits controlled and routed to validators? Is the system primarily on-chain, or does it rely heavily on off-chain custody and coordination? How are rewards and losses accounted for? If there is an oracle, what information does it provide, how often, and what happens if it fails? What is the redemption path: direct withdrawals, secondary markets, reserves, or some combination? And how concentrated are the operators or governance powers that control changes to the system?

Ethereum.org suggests practical indicators such as whether a service is open source, audited, battle tested, trustless or custodial, permissionless for node operators, and attentive to execution and consensus client diversity. These are useful because they map to actual failure modes. A “liquidity token” is not enough. The surrounding system determines whether that token remains credible when conditions stop being normal.

Conclusion

Liquid staking takes an illiquid staking position and wraps it in a transferable token. That is the basic idea, and it explains both its usefulness and its risks.

It is useful because it lowers staking barriers, makes rewards accessible without running validators, and lets staked capital remain active in markets. It is risky because the token is only as sound as the contracts, operators, accounting, withdrawal path, market liquidity, and governance behind it; and because success can concentrate stake and spread stress across DeFi.

The simplest way to remember it is this: liquid staking does not eliminate staking’s lockup; it builds a marketable claim on top of it. That claim can be powerful, but it is never costless.

How do you build a crypto position over time or earn on it?

Build a position over time by scheduling recurring buys on Cube Exchange, then evaluate staking or yield options separately. Start by funding your Cube account and choosing the asset you want to accumulate; Cube executes the purchases and holds the position so you can decide about staking or liquid‑staking exposure later.

1. Fund your Cube account with fiat (bank transfer or card) or send crypto to your Cube deposit address.
2. Create a recurring buy: pick the asset, set frequency and amount, and confirm the settlement currency.
3. Choose an execution type: use a market order for immediate fills or a limit order to target a specific entry price for each scheduled buy.
4. Monitor performance and fees monthly, adjust the recurring settings if needed, and only after you have the position, research staking or liquid‑staking providers off‑platform before moving funds.