The control finding
Binance Staked ETH. An exchange IOU — Binance holds the underlying stake and controls the token. On-chain in form only.
- Named controller
- Binance
- Holder’s position
- A WBETH holder relies on Binance's representation that it holds the underlying staked ETH and will honor redemption. It is an exchange liability, not a decentralized protocol claim.
- Redemption or exit
- Redemption runs through Binance's platform under Binance's terms and processing times. There is no permissionless, on-chain exit path independent of Binance.
Dependencies an advisor should record
- Binance as issuer and custodian of the underlying stake
- Binance's compliance and account-restriction policies
- Binance's operational and solvency risk
- The chain and any bridge carrying the token
- The protocol or venue in which WBETH is deployed
Why this distinction matters
WBETH looks like a liquid staking token but functions like an exchange IOU: Binance, not a smart contract or DAO, sits at the center of the control map. An advisor should treat it as counterparty exposure to Binance first and staking exposure second.
A named organization or administrator controls issuance, transfers, reserves, redemption, or address restrictions. 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.