Ethena Pay adds Earn+ via Aave V4 on Avalanche with 24-hour withdrawals
TL;DR: Ethena Pay’s optional Earn+ connects a consumer dollar balance to an Upshift vault curated by Steakhouse and using Aave V4 on Avalanche. The layered setup defines how rewards are generated and how withdrawals are processed.
Ethena Pay links a familiar app balance to an onchain lending strategy. Separate firms run the app, vault infrastructure, strategy, and lending markets. A simple interface does not remove the risks and dependencies beneath it.
Several firms perform different functions
Per Aave’s integration note: Earn+ deposits route to an Upshift vault curated by Steakhouse, with the strategy using Aave V4 on Avalanche. Aave does not operate, curate, or manage the vault. The strategy supplies USDe and borrows USDT. Users choose allocation size, and withdrawals are processed within 24 hours under the product terms. This is a third-party strategy using multiple components, not a dollar balance earning interest directly from Aave.
Borrowing costs are part of the rewards calculation
A borrow-against-supply strategy must account for asset returns, borrowing costs, fees, and any losses from changing positions. Rising borrow costs can compress rewards even without price moves in collateral. Advertised rates depend on assumptions and terms, and are not fixed indefinite returns.
The lending network and the app have separate liquidity needs
Aave V4 on Avalanche, recorded in the protocol changelog, provides lending infrastructure that Earn+ uses as one component. Liquidity can be constrained at the strategy level when unwinding or retrieving assets and at the app level when converting results into spendable balances. No contractual lock-up does not make each underlying step instant. A stated processing window sets expectations while execution conditions still drive outcomes.
The meaningful comparison is net rewards against the full risk
Users should assess the risks taken to earn additional return and whether those risks are understood: collateral valuation, liquidation parameters, smart-contract behavior, strategy discretion, and the terms of assets used. Divided responsibilities determine who can act if a layer encounters a problem. Packaging the workflow reduces transactions and dashboards, but providers must explain investment exposure as clearly as the deposit action. Performance should be judged by dependable operation and clear net outcomes, not by the presence of a well-known protocol.
Written by the News Desk and edited by Samuel Rae.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.
