esETH
The non-rebasing 1:1 ETH-pegged wrapper that unifies multiple liquid staking tokens into a single denomination layer for the entire protocol.
The Problem
A protocol that accumulates an ETH-denominated treasury faces a choice: which form of ETH do you hold?
Raw ETH earns nothing. Liquid staking tokens (LSTs) earn validation rewards — but each one comes with trade-offs. stETH rebases, breaking smart contract accounting. rETH has limited liquidity. cbETH is controlled by a single US-regulated entity. weETH carries EigenLayer systemic exposure. Picking one means concentrating risk in a single staking provider. Holding several means managing parallel accounting for each.
ETH Strategy needs a single, composable token to denominate its entire treasury — one that earns staking yield, diversifies provider risk, and doesn't break DeFi integrations. No existing LST does all three. So the protocol built esETH.
What is esETH?
esETH is a non-rebasing ERC-20 that wraps multiple liquid staking tokens into a single unified representation. It is not a retail staking product — it is the denomination layer for the entire ETH Strategy treasury.
Every piece of ETH in the protocol — treasury holdings, bonding proceeds, lending collateral, staking rewards — is denominated in esETH.
Supported underlying tokens:
wstETH
Lido
Non-rebasing wrapper of stETH
Largest LST by TVL (~$18.6B); deep liquidity; 800+ operators
rETH
Rocket Pool
Non-rebasing
Most decentralized (3,200+ permissionless operators post-Saturn I)
cbETH
Coinbase
Non-rebasing
Institutional-grade; net APY ~2.9%
weETH
ether.fi
Non-rebasing wrapper of eETH
Restaking exposure; 300+ operators via DVT
aWETH
Aave
Interest-bearing (rebasing in Aave context)
Lending yield diversification; different risk profile from staking
By wrapping all five behind a single interface, esETH gives the protocol diversified staking exposure while keeping internal accounting clean.
How esETH Works
Minting
Deposit any supported LST (or raw ETH) and receive esETH at a 1:1 ratio with the ETH value of the deposit.
The mint amount is determined by the underlying LSTs' native exchange rate functions (e.g., wstETH's stEthPerToken()), not by external oracles or AMM prices. The LST deposit is converted to its ETH value, and that same amount of esETH is minted — 1 esETH is always worth exactly 1 ETH.
Slippage protection: Use previewMint() to check the exact output before executing.
Redeeming
Burn esETH to receive any supported LST the contract currently holds.
Unlike minting, redemption depends on the contract's current LST holdings. If the treasury has rebalanced and holds mostly wstETH, redeeming for rETH may fail due to insufficient balance. Always check previewRedeem() first.
This is a two-step exit: esETH → LST → (then use the LST's own withdrawal to get raw ETH if needed).
1:1 ETH Peg
esETH is always pegged 1:1 with ETH. 1 esETH = 1 ETH, by design.
Unlike wstETH, rETH, or cbETH — where the exchange rate increases over time as yield accumulates — esETH maintains a fixed 1:1 relationship with ETH. Yield from the underlying LSTs is harvested separately and directed to the protocol, not embedded in the token's value.
1 esETH = 1 ETH, always. The peg is maintained by construction: yield is extracted before it can accrete to the token value.
Yield Harvesting
This is the key design difference between esETH and every other LST.
In wstETH, rETH, cbETH, and weETH, yield is embedded — either as changing balances (stETH) or as a rising exchange rate (wstETH, rETH, cbETH, weETH). The holder's token silently becomes worth more over time.
esETH separates yield from the token entirely. The underlying LSTs continue earning staking rewards, but those rewards are harvested periodically and directed to the protocol's yield receiver — not reflected in esETH balances or its 1:1 ETH peg. This means:
esETH holders do not earn yield directly. Holding esETH outside the protocol earns nothing. The yield goes to the protocol, which distributes it to STRAT stakers via StakedStrat.
Accounting is transparent. Treasury holdings (esETH balances) and revenue (harvested yield) are distinct line items, not mixed together.
Balances are perfectly predictable. Your esETH balance only changes on transfer, mint, or burn. Never from a rebase. Never from yield accumulation. This makes esETH trivially composable in any DeFi context.
The harvested yield is the economic engine that pays STRAT stakers. More underlying LST yield → more esETH harvested → more rewards streamed to stakers. See STRAT Staking and STRAT Economics for how this flows through.
esETH in the Protocol
esETH is not a standalone product — it's infrastructure that every other protocol component depends on.
Treasury Denomination
The protocol treasury is split into two pools, both denominated in esETH:
Encumbered holdings — esETH reserved to back conversion rights from convertible notes. Locked until a note holder exercises their conversion-to-ETH right.
Unencumbered holdings — esETH available for lending, yield distribution, and operations. The protocol's "free" capital.
Bonding Proceeds
When a user purchases a convertible note, the ETH they send is wrapped into esETH and split between encumbered and unencumbered holdings. The buyer never holds esETH — they receive CDT + an NFT option instead. The esETH stays in the treasury.
Staking Rewards
Harvested yield from esETH's underlying LSTs flows to the StakedStrat contract as esETH, where it streams to STRAT stakers over 7-day periods.
Lending Collateral and Disbursement
In Treasury Lending, borrowers receive esETH from the unencumbered treasury and repay in esETH. Interest payments (in esETH) flow to STRAT stakers.
Conversion and Redemption
Note holders who convert to ETH receive esETH from the encumbered pool. Post-expiry CDT redemption also pays out in esETH.
Why Not Use an Existing LST?
Provider risk
Concentrated in one staking provider
Diversified across 5 providers
Accounting
Simple but inflexible
Single token for all treasury operations
Yield handling
Embedded in token (rebasing or exchange rate)
Separated — captured as explicit protocol revenue
Composability
Full (if non-rebasing)
Full — standard ERC-20, predictable balances
Risk response
Sell the LST (market impact)
Disable minting for affected token via setTokenConfig() (surgical)
Integration complexity
Low for one; high for many
One interface regardless of underlying composition
For a protocol managing a multi-million ETH treasury with convertible notes, lending, and staking — where every operation needs clean denomination and every revenue stream needs explicit capture — a unified wrapper isn't a luxury. It's infrastructure.
For the full head-to-head comparison with stETH, rETH, cbETH, and weETH, see LST Comparison.
Token Details
Name
esETH
Symbol
esETH
Standard
ERC-20 with ERC-2612 permit
Decimals
18
Rebasing
No
Minting
Permissionless — anyone can deposit supported LSTs or raw ETH
Burning
On redemption — burn esETH to receive underlying LSTs
Ownership
Ownable2Step (protocol multisig)
Transferable
Yes — standard ERC-20 transfers
Status: esETH is deploying soon. Address will be published on the Contracts page before permissionless launch. esETH will initially be available for public mint and redeem in a limited capacity as part of the upcoming release.
Failure Modes and Gotchas
Underlying LST depeg or slashing. esETH does not insulate the treasury from losses in the underlying LSTs. If wstETH depegs, rETH suffers a slashing event, or any underlying protocol is exploited, the affected portion of esETH's backing declines. The wrapper provides diversification, not insurance. The protocol can respond by disabling minting for an affected LST via setTokenConfig(), but existing exposure remains.
Redemption depends on contract holdings. Unlike minting (which accepts any supported LST), redemption requires the esETH contract to actually hold the requested LST. If the treasury has rebalanced — e.g., selling rETH for wstETH — then redeeming for rETH may fail. Always call previewRedeem() before executing. This is a feature (it lets the protocol manage its LST allocation) but it can surprise users who assume symmetric mint/redeem.
esETH holders do not earn yield. This is the most common misconception. esETH looks like an LST, but it does not behave like one for the holder. The underlying staking rewards are harvested and directed to the protocol's yield receiver — not to esETH holders. Holding esETH in a wallet earns nothing. To earn yield from the protocol, you need to hold and stake STRAT.
Supported LST set is governance-configurable. The owner can add or remove supported LSTs via setTokenConfig(). A previously supported LST could be disabled for new mints — users holding that LST would need to swap it before minting esETH. A previously redeemable LST could also be disabled. Do not hardcode LST addresses in integrations; query the contract.
1:1 peg is not a market price. esETH is pegged 1:1 with ETH by construction, but if esETH trades on a DEX, the market price could diverge from the peg. For collateral valuation, lending markets, and portfolio display, always treat 1 esETH = 1 ETH — never use AMM spot price.
Rounding dust on maximum-balance operations. When transferring a user's entire esETH balance, 1–2 wei may remain due to integer division in exchange rate calculations. If your contract needs exact-balance transfers, read balanceOf() at execution time rather than using a cached value.
ERC-2612 permit front-running. A griefer can front-run your permit call by submitting the same signature first. The permit succeeds for the griefer, then your transaction reverts. Mitigation: wrap permit + action in a try/catch — if permit reverts, check if allowance is already set and proceed.
Harvest timing creates a small MEV window. Between the time underlying LST yields accrue and the time they are harvested to the yield receiver, there is a brief period where esETH's underlying LST backing is slightly more valuable than 1 ETH. This is mitigated by the protocol controlling harvest timing and by the yield receiver distributing rewards via 7-day streaming (preventing flash-harvest extraction).
For protocol-wide risks and mitigations, see Risks. For integration patterns and production warnings, see the Developer Integration Guide.
Last updated