The control finding
Staked ETH via Lido. No blocklist, though the withdrawal path depends on Lido governance and validator behaviour.
- Named controller
- No token-freeze administrator; Lido DAO governs the protocol
- Holder’s position
- stETH represents a claim on ETH staked through Lido's validator set. Balances rebase daily to reflect accrued consensus rewards net of protocol fees.
- Redemption or exit
- Holders withdraw 1:1 for ETH through Lido's on-chain withdrawal queue, subject to the queue's processing time, or exit through a market instead.
Dependencies an advisor should record
- Lido DAO governance decisions
- Lido's node operator set and its slashing exposure
- The withdrawal queue and its processing time
- Ethereum consensus and validator exit mechanics
- Any wrapper, bridge, or protocol built on stETH
Why this distinction matters
stETH's rebasing balance is itself a dependency: protocols that cannot handle rebasing tokens force holders into wstETH instead. An advisor should record that liquidity and validator behavior, not an issuer, are the practical constraints on exit timing.
No single issuer or administrator has an address-level freeze function at this layer. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.
Questions before use
- Does the exact contract and chain match the instrument reviewed here?
- Which party can mint, burn, pause, upgrade, block, or redeem?
- Does the client have direct redemption access or only secondary liquidity?
- What protocol, bridge, wallet, and custodian dependencies are added?
- Which event would force review or exit?
Primary sources
Primary documents can change. This profile records the control interpretation reviewed on 2026-08-06; verify current terms before implementation.