Lidodao: how Lido's wstETH avoids balance rebases
Lido's wstETH reflects stETH rebases in its conversion rate, leaving a holder's wstETH count unchanged by the rebase. Lido DAO governs the liquid staking protocol behind these tokens. This representation fits DeFi applications whose accounting assumes token balances change only through transfers, minting or burning.
Aave V2's direct stETH integration
Aave V2 integrated stETH directly. Its aToken accounting followed an Aave liquidity index, so passing stETH rebases through to depositors required a custom
AStETH
implementation combining that index with a stETH share-based rebasing index.
Conversions between nominal stETH and aSTETH balances also introduced rounding at wei precision. Deposits could mint slightly less aSTETH than the requested stETH amount. Exact-amount operations had to handle the documented 1-2 wei stETH transfer corner case.
Aave V3 uses wstETH as collateral. The wrapper fits accounting systems built for non-rebasing balances without requiring Aave V2's custom handling of stETH rebases.
The rate carries the rebase
The wrapper holds stETH as backing and mints wstETH according to the share-based conversion. Unwrapping burns wstETH and releases the corresponding stETH at the applicable rate. Obtaining ETH through the staking protocol uses its separate withdrawal mechanism.
Positive stETH rebases increase the amount of stETH each wstETH represents. A negative rebase following validator penalties can reduce that amount. Transfers, minting and burning can change a wstETH balance, but a rebase on its own does not.
On Ethereum mainnet,
wstETH.stEthPerToken()
exposes the wrapper's stETH-per-wstETH conversion rate. This rate describes a token conversion, while a secondary-market swap executes at the selected venue's price and liquidity. Trading stETH or wstETH for ETH can involve slippage and a premium or discount relative to the underlying ETH value.
Oracle updates and underlying risks
stETH rebases normally follow daily accounting-oracle reports. A missing quorum, lack of Ethereum consensus finality or failed oracle sanity checks can delay an update. wstETH reflects the resulting stETH conversion rate; wrapping does not create an independent reward calculation or guarantee a daily increase.
Holding wstETH still involves smart-contract risk and possible losses in the underlying staked ETH. Using wstETH as collateral also introduces the selected lending market's liquidation risk.
Minting routes and network boundaries
Existing stETH can be wrapped into wstETH. The Ethereum wrapper also supports staking ETH directly into wstETH, with Lido's staking rate limits still applying to that shortcut. Lido V3 stVaults provide another route to mint stETH or wstETH against vault collateral, under their own vault mechanics and fee arrangements.
Most bridged wstETH deployments cannot unwrap locally into stETH. Networks where stETH is also available use the LIP-22 token design, so Ethereum mainnet wrapper behavior cannot be assumed for every destination. Where a bridged token lacks share bookkeeping, an application needs an appropriate wstETH/stETH rate feed.
Decision checklist for token support
- If balance accounting assumes changes only through transfers, minting or burning, wstETH fits that model; valuation still needs its applicable conversion rate.
- If integrating stETH directly, account for shares and rebases, including rounding in exact-amount operations.
- For a bridged deployment, confirm local wrapping or unwrapping support and the rate feed the application can read.
- For collateral use, assess the specific market's price feed and liquidation rules; an unchanged token count does not stabilize collateral value.