AprScope

ether.fi Stake · Ethereum

WEETH

Current APY

2.34%

base 2.34% · reward 0.00%

TVL

$6.05B

APY +0.06% 7d

Risk signals

2.34% - single asset

Overview

The ether.fi Stake WEETH pool on Ethereum is a single-asset liquid restaking position where WEETH serves as the underlying asset. The pool generates a base APY of 2.50 percent with an additional 0.05 percent from rewards, totaling 2.56 percent annually. Over the past seven days, APY increased 0.43 percent, though the thirty-day trend shows a 0.59 percent decline from the thirty-day mean of 2.62 percent. The pool holds 3.88 billion dollars in total value locked. As a single-asset position, the pool carries smart-contract risk inherent to the restaking protocol, though it avoids impermanent loss and depeg exposure.

Composed 2026-05-18 from the structured data above. See methodology for the full pipeline.

APY history
TVL history

Risk profile

  • Smart contract risk

    Funds are deposited into a smart contract. A bug or exploit in the contract could lead to total loss. Audits reduce, but do not eliminate, this risk. Check the protocol page for audit history.

  • Yield variability

    Current APY is 2.34%; 30-day mean is 2.33%. Yields can change as TVL and incentive emissions change.

  • DefiLlama yield prediction

    DefiLlama's model classifies this pool's yield as "Stable/Up" with 65% confidence based on historical patterns.

These notes are derived from the pool's structured data, not editorial advice. See our methodology.

Similar pools

FAQ

› What is the current APY for ether.fi Stake WEETH on Ethereum?

The current total APY is 2.34%. Base yield: 2.34%. Reward yield: 0.00%.

› What is the TVL of this pool?

Total value locked is $6.05B as of the last data refresh.

› Is there impermanent loss risk?

No. This pool is single-asset and has no impermanent loss exposure.

› How often is this APY updated?

We refresh APY and TVL hourly from DefiLlama. Daily snapshots are stored to power the historical chart on this page.

Last updated 2026-10-04. See methodology for how we collect and refresh this data.