stETH is a balance-sheet instrument, not a “supply narrative” token
stETH is where ETH staking yield turns into tradable inventory. The token’s job is simple: represent a pro-rata claim on ETH pooled and staked through Lido, while staying transferable across DeFi rails. Lido’s core contract is itself the rebasing ERC-20 that users hold as stETH.
Two properties matter for market structure. First, stETH is rebasing. Balances update when Lido applies oracle reports, which is typically about once per day. Second, stETH is not intended to be a hard peg to ETH on secondary markets. For a contrast with hard-pegged designs, see our USDC review.
The clean mental model is “staking fund shares that float.” Lido mints stETH when ETH is submitted and burns it when redeemed. That means there is no max supply in the usual tokenomics sense, because supply scales with how much ETH the protocol is running and how much stETH is outstanding. CoinGecko also reflects this with Max Supply = ∞.
The wrapper wstETH exists because a lot of DeFi plumbing still breaks on rebasing balances. For the wrapped version’s mechanics and positioning, see our wstETH review.
Supply mechanics: mint, rebase, burn, and the real “unlock schedule”
stETH supply is elastic because it is accounting for pooled ETH. Lido implements rebasing via a shares system where the user’s shares stay constant while total pooled ETH changes. Lido documents the balance relationship as: balanceOf(account) = shares[account] * totalPooledEther / totalShares.
The rebase is not cosmetic. It is the protocol’s settlement cycle. Lido states that token supply increases or decreases algorithmically based on Beacon Chain staking rewards (or slashing penalties), execution-layer rewards, and, since withdrawals, fulfilled withdrawal requests. Lido also flags an integration edge: stETH does not emit Transfer() events on rebase.
The oracle cadence is the closest thing stETH has to an “emission schedule.” Lido documents that stETH balances are recalculated daily when the oracle reports consensus-layer balance updates. The oracle system is a 9-member committee with a quorum of 5.
On the withdrawal side, Lido V2 introduced an in-protocol primary redemption path for ETH. Lido announced Lido V2 as live on May 15, 2023, with Ethereum withdrawals enabled through the protocol. This mattered because Ethereum enabled validator withdrawals at the protocol layer on April 12, 2023 (the Shapella upgrade).
Lido’s Withdrawal Queue turns redemption into a time-queued liquidity event. Requests are FIFO and finalized in daily batches when the AccountingOracle updates protocol balances and burns the corresponding stETH. The WithdrawalQueue contract mints an unstETH NFT representing the queued claim and burns it on claim.
Two mechanical details become microstructure details under stress. A single withdrawal request has a minimum of 100 wei and a maximum of 1000 ETH, so large exits must be chunked. And the request’s ETH amount is bounded by the stETH deposited at request time, meaning the user does not earn new rewards while their stETH is locked in the queue. That “foregone rebase” is an explicit cost of immediacy if you choose the primary redemption path instead of secondary liquidity.
Fees and fiscal flows: fee-minted dilution, split across modules
Lido’s protocol fee is taken from staking rewards, not from principal. Lido states the protocol fee is 10% of staking rewards, set by the DAO and changeable via governance. If you want a quick glossary for the terms used here, see our tokenomics FAQ.
The important part is how the fee is implemented. Lido collects the fee by minting new stETH shares and assigning them to fee recipients. Mechanically, that is dilution in share terms rather than a token transfer that you can point to on a block explorer. It shows up as a slightly lower growth rate of stETH holders’ balances than the gross staking return.
Fee split is not a single static number anymore because Lido is modular. Lido’s protocol fee page states the fee is currently 10% and is “split into two parts” (node operator fee and treasury fee), and that each staking module has its own fee split. For the Curated Module specifically, Lido documents the split as 90% to stakers via stETH rebases, with the remaining 10% split 5% to node operators and 5% to the DAO treasury.
Two more nuances that matter in downside scenarios. Lido states the protocol fee is waived during periods of negative net rewards, when consensus-layer penalties exceed earned rewards. And Lido explicitly allows negative rebases if penalties or slashing events dominate rewards.
Net-net, stETH is a yield-bearing inventory asset with an embedded fee that is realized through share minting. That tends to be under-modeled by people who only look at “total supply” and “circulating supply.” The fee is the real long-run drag, and the withdrawal pathway is the real short-run peg discipline.
Liquidity and float concentration: stETH trades inside an arbitrage band
There are two exit routes by design. You can swap stETH on secondary markets for instant liquidity, or you can go through the Withdrawal Queue for primary redemption. Lido frames both exit routes explicitly, and flags that secondary market prices may differ from ETH based on supply and demand.
That creates an arbitrage band rather than a peg. If stETH trades cheap, an arbitrageur can buy stETH and redeem through the protocol. But they inherit three frictions that define the floor:
- Time risk: withdrawal times depend on queue size, buffer availability, and validator exit dynamics.
- Carry leakage: stETH locked in the queue does not accrue new positive rewards beyond the request’s bounded redemption logic.
- Discrete settlement: finalization is coupled to oracle reporting and batching, not continuous redemption.
On the upside, stETH can trade rich in “risk-on” phases when stETH is used as collateral and yield-bearing base money. That premium is not magic. It is balance sheet demand meeting limited spot liquidity, especially if a lot of free float is tied up in lending positions, LP positions, and structured products that do not want to unwind.
wstETH is the plumbing token for that leverage loop. Lido explicitly recommends operating on shares and/or using wstETH for integrations because many protocols are not designed for rebasable balances. The market consequence is that “stETH liquidity” is often synthetically routed through wstETH venues, wrappers, and lending markets. In stress, those venues can unwind in correlated fashion, turning what looks like diversified liquidity into a single crowded door.
One more microstructure detail that’s easy to miss. stETH has a protocol-level oracle sanity regime that bounds how fast accounting can move. Lido documents oracle sanity limits including a max reported APR sanity check of 27% and a max reported staked-ether decrease of 5%. These constraints are safety features. They also mean stETH’s accounting can be intentionally conservative during extreme conditions, which can widen short-horizon basis risk versus “mark-to-market ETH.”
Governance control: stETH is governed indirectly through Lido DAO and privileged roles
stETH itself is not a governance token. But the parameters that shape stETH’s cashflows, validator set, oracle set, and safety modes are governed. Lido states the Lido DAO manages key protocol parameters such as fees and assigning node operators and oracles, with decisions made through voting power of LDO holders.
From a market-structure lens, “governance risk” is less about drama and more about who can change the rules that define the arbitrage band. Fee rate changes, module fee split changes, oracle configuration changes, and withdrawal flow changes all map into basis risk for stETH holders and for anyone running leveraged stETH books.
Lido’s own documentation describes a tight surface area for supply mutation: oracle report application, and, in newer architecture, the ability for stVaults to mint/burn external shares under defined control surfaces. Even if you never touch stVaults, the existence of additional mint paths changes how you should think about “circulating supply.” It is not a single pipe.
The oracle side is explicit. Lido documents the oracle committee as 9 participants with a quorum of 5, and that identical reports from 5 members are required for report finalization. Lido also documents that if oracles do not report or do not reach quorum, the daily rebase does not occur until quorum is reached.
Governance is the trade-off layer. It buys narrative stability around “decentralized staking infra.” It also makes parameter stability probabilistic. stETH markets price that as a spread, not as a forum post.
Risk register: basis risk dominates, because liquidity is the product
Lido’s own known risks page highlights an oracle-committee compromise scenario where a majority could report incorrect balances and trigger significant negative rebases. That is real. But in practice, the most common way stETH hurts people is not a protocol failure. It is a liquidity event where stETH becomes the release valve for leveraged ETH exposure.
Dominant risk: stETH-ETH liquidity dislocation under forced selling.
Mechanism-level, this is about time. Primary redemption is asynchronous and depends on the withdrawal queue, buffer availability, and validator exit dynamics. Secondary markets clear instantly, but at a price. Lido explicitly notes stETH can trade away from ETH and is not meant to be pegged.
Under calm conditions, arbitrage compresses the spread. Under stress, the spread widens because the arb becomes balance-sheet constrained. If you buy discounted stETH to redeem, you are warehousing queue time, execution risk, and the fact that queued stETH does not keep earning new upside the way freely-held stETH does. When the marginal holder is a leveraged book that needs ETH now, not ETH later, the market clears at the discount required to pull in new balance sheet.
That is where float concentration bites. stETH tends to be used as “productive collateral,” and productive collateral gets rehypothecated. When risk limits tighten, everyone reaches for the same exits at the same time. The withdrawal queue is not a circuit breaker for price. It is a circuit breaker for redemption. Price can gap anyway.
In other words, the design trade-off is explicit. Narrative stability comes from a conservative, oracle-mediated accounting system and a structured withdrawal process. Liquidity shocks come from the same structure when the market wants continuous redemption and gets batch finalization instead. That tension never goes away. It only goes quiet.
If you are building products that depend on stETH liquidity, it is worth doing explicit scenario work on depeg magnitude versus queue time, and mapping that into liquidation waterfalls. If you need help pressure-testing those scenarios or reviewing parameter sensitivity, this is where focused tokenomics consulting looks more like market-structure engineering than like a supply chart.
Top 3 risks
Liquidity depeg and reflexive deleveraging, Trigger: sharp risk-off move or cascading liquidations in venues using stETH/wstETH as collateral. Mechanism: secondary liquidity clears at a discount because primary withdrawals are queued and finalize in batches, while some holders must sell immediately. Who bears it: leveraged borrowers, LPs providing stETH liquidity, and any strategy promising “near-ETH” liquidity. Measurable indicators: stETH/ETH spot basis on major venues, withdrawal queue size and projected wait, and on-chain lending health factors for positions collateralized by stETH/wstETH.
Negative rebase from penalties or slashing, Trigger: validator underperformance, penalties, or slashing large enough to outweigh rewards in a reporting window. Mechanism: Lido’s rebase can be negative, reducing balances proportionally; protocol fee is waived during negative net rewards, but stETH holders still absorb the loss via lower total pooled ETH per share. Who bears it: all stETH holders, plus downstream holders using stETH as collateral with tight liquidation thresholds. Measurable indicators: oracle-reported share rate change, validator penalty events, and any observed negative or stalled rebase periods.
Oracle/governance integrity shock, Trigger: oracle compromise, governance capture, or prolonged oracle quorum failure. Mechanism: Lido relies on an oracle committee of 9 with quorum 5; a majority compromise can report incorrect balances and trigger significant negative rebases, and quorum failure can delay rebases and withdrawals finalization. Who bears it: stETH holders, DeFi protocols integrating stETH/wstETH, and any market maker warehousing stETH basis. Measurable indicators: oracle committee changes, failed/delayed report finalizations, and governance proposals affecting fee rates, module configuration, or oracle roles.
This article is part of our Tokenomics Deep Dive series.
