The Tokenomics of ether.fi Staked ETH (EETH)

eETH’s “tokenomics” are really liquidity mechanics wearing a staking wrapper. The supply is elastic, the yield is rebased, and the exit path is a two-lane system where the fast lane can shut when buffer liquidity gets thin. That last part is what shapes market outcomes.

What eETH is in-product

ether.fi issues eETH as its liquid restaking token. Users deposit ETH into ether.fi’s LiquidityPool and receive eETH “shares” that represent a claim on the protocol-controlled ETH (some sitting liquid, most staked in validators, and also “natively restaked” through EigenLayer at the protocol level), as described in the LiquidityPool accounting.

Mechanically, eETH is a rebasing ERC-20. Your balance increases over time as the protocol updates pooled-ETH accounting and rebases holders.

Most DeFi integrations want a non-rebasing asset. ether.fi’s answer is weETH, a wrapped, non-rebasing representation of eETH that converts at the current share rate through the LiquidityPool.

On Ethereum mainnet, the canonical contracts are published by ether.fi in its deployed contracts: eETH 0x35fA164735182de50811E8e2E824cFb9B6118ac2, weETH 0xCd5fE23C85820F7B72D0926FC9b05b43E359b7ee, and the LiquidityPool 0x308861A430be4cce5502d0A12724771Fc6DaF216.

Structural history that matters for token behavior

ether.fi’s docs describe a progression from delegated staking to pooled liquid staking and restaking. In the current model, user deposits flow into a LiquidityPool that orchestrates validator creation and reward accounting, and eETH/weETH sit on top as the liquid representation.

One concrete implication is how exits are represented. The “standard” withdrawal path mints a WithdrawRequestNFT (an ERC-721) that represents a queued withdrawal claim.

Also, ether.fi’s docs state that legacy T-NFT and B-NFT mechanics were retired when the protocol migrated to the LiquidityPool model.

Supply mechanics: shares, rebases, and why “float” beats “FDV” here

eETH does not have a fixed supply schedule, a cap table allocation, or an “unlock calendar” in the normal tokenomics sense. Supply expands and contracts with user behavior. Deposit ETH, receive newly minted eETH shares. Redeem, burn eETH/weETH against ETH leaving the pool. For a different tokenomics case study on a liquid wrapper asset, see our LBTC tokenomics.

The clean way to think about eETH is the share accounting. ether.fi describes eETH balances as a function of TotalPooledEth, TotalShares, and the holder’s shares. The rebase is implemented by changing the relationship between pooled ETH and shares, so balances update automatically across addresses. Our tokenomics methodology treats this as a “float first” problem, not a supply-schedule problem.

That’s why tracker-reported “circulating supply” is a weak explanatory variable. What moves markets is effective circulating supply:

• How much eETH/weETH is sitting in liquid venues (AMMs, CEX listings, lending markets), ready to hit the bid.
• How much is economically locked by DeFi positioning (collateral loops, Pendle-style splits, LP vaults).
• How much can be converted into ETH through the protocol quickly, versus being forced into a queue.

eETH’s on-chain share supply can rise smoothly with deposits while tradable float can dry up fast when leverage builds on top of weETH. That mismatch is where depegs get born.

Exit mechanics and effective float: buffer liquidity, the queue, and the 0.3% fast lane

ether.fi explicitly runs a two-mode exit design.

Standard withdrawals are queued. The published withdrawal request flow is: unwrap weETH to eETH, call LiquidityPool.requestWithdrawal, receive a WithdrawRequestNFT representing the queued withdrawal, then finalize and claim when ready.

Instant withdrawals exist, but they are conditional and priced. ether.fi’s docs state the instant redemption charges a 0.3% fee and is rate-limited.

The gating condition matters more than the fee. Instant withdrawal is only allowed when buffer liquidity is above a low watermark that ether.fi documents as 1% of eETH TVL.

From a liquidity structure standpoint, this creates a predictable stress pattern:

• In calm markets, the fast lane pins eETH/weETH closer to ETH, because arbitrage can redeem against the pool (paying 0.3%) when secondary markets drift.
• In risk-off markets, the buffer gets drawn down. If it drops under the watermark, the fast lane shuts and price discovery moves to AMMs and OTC, with the protocol exit path shifting to “time” instead of “fee.”

Under the hood, the LiquidityPool tries to redeem from unbonded ETH first. If there is insufficient ETH available, the docs say it will queue full validator exits and process redemptions once ETH is released from the beacon chain.

ether.fi’s own staking write-up admits the protocol holds ETH in the liquidity pool to facilitate quicker withdrawals, and that this can marginally reduce returns.

One more float edge that’s easy to miss: ether.fi’s unstaking guide says unstaking is currently only supported on ETH mainnet. Users can deposit from L2s, but the protocol’s primary redemption UX is anchored to mainnet.

Rewards, fees, and fiscal flows (what actually accrues to eETH)

eETH is positioned to earn both staking and restaking economics. ether.fi’s docs frame eETH/weETH as “natively restaked” at the protocol level, so users do not need to lock an LST into EigenLayer strategy contracts to get restaking exposure.

For restaking, ether.fi’s eETH page claims “restaking emissions” are aggregated weekly, converted to ETH, and automatically deposited into the LST liquidity pool, increasing token value via rebasing without user claims.

The protocol-level split is stated in the reward split: the sum of staking rewards is split 90% to stakers, 5% to node operators, and 5% to the protocol. It also states that this applies to both staking and restaking rewards.

ether.fi also provides an example calibration: as of September 13, 2025, it states combined staking and restaking APR was 3.1%, implying protocol revenue of 31 basis points given the 10% aggregate take (node operator share plus protocol share).

Withdrawal behavior is also a revenue surface. ether.fi governance discussions describe protocol revenue generated “on the withdraw process” via two mechanisms: fast withdrawals charging the 0.3% fee and normal withdrawals that “forfeit yields during the exit process.”

From the eETH holder’s perspective, the key point is that rewards accrue by increasing pooled ETH relative to shares, and that update is mediated by an oracle report. The LiquidityPool increases total pooled ETH without increasing shares, lifting the value per share and distributing rewards to holders.

Governance and parameter control (and where discretion can hit the market)

eETH itself is not a governance token. The governance axis runs through ETHFI and protocol roles.

In ether.fi’s governance GitBook, the project states the ether.fi Foundation exists to carry out decisions of ETHFI token holders and steward the treasury and protocol.

That same governance page lists the kinds of parameters ETHFI holders can influence, including protocol fees and contract upgrades, and “green-lighting of node operators.”

On the technical side, ether.fi says upgrades to contracts are governed by a timelock and require appropriate roles via the RoleRegistry.

Practically, the most market-relevant governance-adjacent component is the oracle reporting loop. ether.fi describes EtherFiOracle as a decentralized reporting mechanism where a committee monitors the beacon chain and EigenLayer and submits reports. Once a report reaches the required quorum, it is published on-chain and used to update pooled ETH and trigger the rebase.

The docs do not publish, in the sections cited here, the committee size, quorum threshold, or report cadence as fixed numbers. That limits modelability. It also means “parameter stability” is partially social, not purely mechanical.

Risk analysis: ranked register (dominant risk is liquidity-driven)

ether.fi’s own documentation names smart contract, key management, and regulatory risk at a high level.

For eETH holders, the risk hierarchy is more specific. The token can be fundamentally solvent and still trade like a distressed asset if exits bottleneck. That’s the float reality. We cover comparable liquidity-driven failures in our crypto research reports.

Top 3 risks

1. Liquidity gate and depeg risk (dominant). Trigger: a rapid wave of redemptions that draws down the protocol’s unbonded buffer, pushing buffer liquidity below the low watermark for instant exits.

   Mechanism: when instant redemption is disabled, eETH/weETH sellers must either (a) accept secondary market discounts or (b) move to the queued withdrawal path where the LiquidityPool may need to exit validators and wait for beacon-chain withdrawals before it can satisfy redemptions.

   Who bears it: holders who need ETH liquidity on a deadline, leveraged DeFi users posted in weETH collateral loops, and LPs who are effectively short volatility when the peg breaks.

   Measurable indicators: availability of instant redemption (low watermark condition), the RedemptionManager “canRedeem” checks, growth in queued withdrawal claims (WithdrawRequestNFT issuance), and persistent AMM discounts of eETH/weETH versus ETH.

   Why this dominates: eETH is a claim on staked ETH plus restaking economics, but it trades on marginal liquidity. In normal conditions, the 0.3% exit fee is a tight band that keeps the token economically arbitrageable.

   In stress, time becomes the price. The system shifts from “pay 30 bps and exit now” to “wait in a queue tied to validator exits and beacon-chain withdrawal finality.” ether.fi’s own docs say that if unbonded ETH is insufficient, it will queue full validator exits and process redemptions once ETH is released from the beacon chain.

   That is a solvency-preserving design. It is also a float shock. Tradable supply spikes as impatient holders sell, while immediate redemption capacity compresses. If you are running weETH as collateral, this is the exact setup that turns a small discount into forced selling. The protocol can be “working as designed” while markets still punish it.

   The trade-off is explicit in the docs: holding ETH liquid in the liquidity pool helps quicker withdrawals but marginally reduces returns.

   That’s the right economic choice for a liquid token. Still, it means eETH’s stability is a function of buffer management and demand cyclicality, not just validator performance.

2. Socialized slashing and AVS risk. Trigger: validator slashing or penalties from restaking services (AVSs) that hit the protocol’s pooled position.

   Mechanism: ether.fi states that rewards and slashing penalties from restaking are socialized across depositors, and that slashing penalties from misbehaving validators or restaking services are shared across all depositors with no dedicated bond.

   Who bears it: all eETH/weETH holders through a reduced claim on pooled ETH, expressed via the share accounting and rebases.

   Measurable indicators: oracle reports referencing slashing/penalties, changes in pooled ETH relative to shares, and any disclosed shifts in restaking exposure.

3. Oracle and upgrade control risk. Trigger: delayed or disrupted oracle reporting, or governance/role actions that modify key parameters (fees, redemption settings, upgrade execution) in a way markets interpret as adverse.

   Mechanism: oracle reports feed reward accounting and trigger the eETH rebase; upgrades are governed by timelock and roles. If reporting cadence slips or upgrades become contentious, composability integrations can price in operational risk through wider discounts.

   Who bears it: DeFi integrators and eETH/weETH holders, especially anyone depending on precise accounting (lending markets, vault strategies, bridged weETH users who already face mainnet exit friction).

   Measurable indicators: time between oracle reports, governance proposals touching fee/exit parameters, and RoleRegistry or timelock activity around upgrades.

If you’re integrating eETH/weETH into a vault, lending market, or structured product, the work is mostly applied market design. You model buffer liquidity, redemption gating, and secondary liquidity concentration. That’s where a tokenomics advisor or tokenomics consulting engagement earns its keep, because the “APR headline” is rarely the binding constraint.

This article is part of our Tokenomics Deep Dive series.