When a user deposits ETH into a liquid staking pool, the operation is presented as an efficiency improvement: reduced minimum capital, no hardware, a transferable token.
I disagree with the optimistic reading. Liquid staking did not suppress the risk associated with validation; it redistributed that risk across contracts, operators, and third-party protocols that depositors rarely evaluate with the same rigor they apply to yield.
The 32 ETH barrier was real and remains the industry’s strongest commercial argument. An individual validator requires capital, stable connectivity, continuous monitoring, and operational knowledge.
Pools solved access. The problem is that the solution introduced an intermediary into a function that the original design of the consensus layer left in the hands of the key holder.
An LST Is Not ETH
A liquid staking token (LST) is not ETH. It is a contractual claim on ETH held by a third party, with issuance, redemption, and governance rules defined by a smart contract. The distinction matters in accounting, credit analysis, and regulatory treatment. Treating stETH or rETH as functional equivalents of ETH ignores the intermediation layer both instruments represent.
Accrual mechanisms complicate accounting. Rebasing tokens adjust the holder’s balance, while appreciation models concentrate yield in the redemption price. For a credit protocol, each design requires a different oracle and its own liquidation policy. An integrator that treats both models as equivalent assumes exposure it did not measure.
Validator and Infrastructure Concentration
A protocol managing close to 30% of staked ETH does not only accumulate fees: it accumulates influence over block production and over governance decisions that affect the entire network.
Decentralization of the validator set is not measured by the number of holders, but by the number of operators with effective control over signing keys.
Permissioned operator sets concentrate trust in a small group selected by the protocol itself. Permissionless models, such as Rocket Pool, distribute validation across thousands of operators with collateral requirements in RPL.
Both approaches have costs: the first concentrates, the second raises operational expenses and transfers collateral token volatility to node economics.
Block production adds another layer of dependency. Proposer-builder separation (PBS) and the widespread use of MEV-Boost concentrate block construction in a reduced number of relays and builders. A pool operator that delegates block construction inherits exposure to infrastructure over which the depositor has neither visibility nor control.
Restaking: Additional Yield, Correlated Penalties
Restaking added a new dimension to the problem. Reusing ETH or an LST as collateral to secure external services (AVS) multiplies slashing conditions on the same capital. Additional yield is paid for with additional exposure, and the correlation between penalty sources is not low: an operational failure can trigger simultaneous penalties across multiple protocols.
Slashing is infrequent in relative terms, and low frequency is often used as an argument to minimize its weight. The statistic does not cover the relevant scenario: a coordinated failure of a large operator, a configuration error replicated across hundreds of validators, or a defective upgrade. In a pool, the penalty is socialized across all depositors, including those who did not choose the operator.
Composability and Leverage
Composability amplified the effect. An LST deposited as collateral in a credit market, borrowed in ETH, and staked again generates leverage on an asset whose price depends on confidence in the token issuer. In a market correction, liquidations pressure the LST price, oracles update, and depegging accelerates through mechanics, not panic.
Depegging does not require a protocol collapse. It is enough for direct redemption to face the exit queue of the consensus layer, which can extend for days or weeks depending on aggregate demand. A holder who needs immediate liquidity sells on the secondary market at a discount and records a loss that accumulated yield rarely offsets.
The secondary market functions as a pressure valve. When exit demand exceeds redemption capacity, the token price absorbs the imbalance. The valve relieves the protocol and shifts the cost to the holder, who discovers that the promised liquidity was a market condition and not a property of the instrument.
Governance, Regulation, and Absence of Hedging
Protocol governance operates with parameters that directly affect the depositor: fees, operator selection, upgrade contracts. Those who do not participate in votes delegate decisions over their capital to a reduced quorum. Governance capture does not require a hostile takeover; it requires indifference from everyone else.
If an LST is classified as a security, the issuer’s operation changes, and with it the token’s availability on regulated platforms. The depositor who ignored the legal dimension assumed counterparty risk without an associated price and without sufficient disclosure at the time of subscription.
There is also a lack of hedging instruments. There is no deep market to insure contract failure in staking protocols, and available premiums cover a limited set of events. Without a price for risk, capital allocation is guided by comparative APY, an insufficient criterion for an exposure with fat-tailed distributions.
The Counterweight That Deserves Recognition
I recognize the counterweight. Pools reduced the cost of entry, professionalized node operations, and increased participation in validation. Some protocols incorporated dual governance mechanisms and withdrawal processes for operators. The balance is not negative in terms of access; it is deficient in transparency about what the depositor actually owns.
Public discussion, however, remains anchored in yield. A higher APY communicates greater compensation per unit of time, not lower risk per unit of capital. As long as comparison between protocols is made exclusively by nominal return, the market will continue to reward more fragile structures without demanding proportional disclosure.
Three Verifiable Criteria Before Allocating Capital
I propose three verifiable criteria before allocating capital to a pool. First, disclosure of the operator set and the distribution of signing keys. Second, on-chain verification of deposits to the consensus layer deposit contract, without relying on reports issued by the protocol itself. Third, an explicit diversification policy by issuer, with exposure limits defined before seeking yield.
At the industry level, I argue that protocols should publish self-imposed limits on their share of total staked ETH and report aggregate restaking exposure. A market that does not know the size of the correlation between its collateral cannot estimate the depth of a cascading liquidation or the probability of a disorderly exit.
Regulators, for their part, have a narrow but useful margin for action: require risk disclosure comparable to that of financial products with counterparty exposure, and clarify the status of LSTs before volume concentrates further. Regulatory ambiguity does not protect the user; it delays the adoption of reporting standards the industry could adopt on its own initiative.
My position is direct: liquid staking is a legitimate tool and a poorly accounted risk. The industry advanced in accessibility and retreated in traceability. Depositors obtained yield and ceded control over keys, operators, and governance decisions they did not choose and in many cases cannot audit.
The pending debate is not whether to stake, but what is being purchased when doing so through an intermediary. A token representing ETH held by a third party incorporates counterparty risk, contract risk, liquidity risk, and governance risk into a single position.
As long as yield is shown without the structure that sustains it, the investor will continue buying exposure to third-party decisions with the expectation of buying ETH.
Be the first to comment