The Ethena Foundation has submitted a governance proposal to allocate a portion of the synthetic dollar USDe’s backing assets to a dedicated credit line on the upcoming Aave V4. The official proposal outlines a Core Hub credit line configuration designed to integrate Ethena’s liquidity with Aave’s next-generation lending infrastructure.
If approved, the proposal would expand the ways in which USDe’s backing assets can be deployed within DeFi money markets. Rather than limiting their role to the assets supporting Ethena’s existing structure, the proposed allocation would place a portion of them within Aave V4 under parameters designed for USDe. The proposal remains subject to governance approval, so its eventual scale and impact have not yet been established.
Integration with Aave V4 Core Hub
The technical focus of the proposal centers on the “Core Hub,” a central component of Aave V4 intended to coordinate liquidity and risk management across supported networks. Ethena’s proposed credit line would connect its allocated backing assets to this infrastructure, with the configuration designed around the specific characteristics and risk parameters of USDe.
The proposal does not establish that the arrangement would immediately generate a particular return or materially change USDe’s backing structure. Those outcomes would depend on the final configuration, governance approval and subsequent implementation.
The move comes as Ethena continues to expand the venues where USDe and its yield-bearing counterpart sUSDe are used. The protocol previously recorded a 5.6% decline in sUSDe TVL during a period of compressed yields, while its expansion to Solana through Kamino and Jupiter Lend brought USDe supply on those platforms above $50 million.
The governance discussion remains open for community feedback. If approved, the allocation would give Ethena a defined position within Aave V4’s lending infrastructure and add another venue through which USDe-related liquidity can interact with DeFi credit markets.
No activation date has been specified. Implementation remains dependent on the governance outcome and the broader rollout of Aave V4.