Aave Goes Live on Aptos, Bringing Lending and Stablecoin Liquidity to a New Layer‑1
Aave — the widely used decentralized lending protocol — has launched on the Aptos blockchain, marking a major step in the protocol’s multichain expansion and its first deployment beyond EVM‑compatible chains. The move opens Aave’s lending, borrowing and savings primitives to Aptos users and developers.
At launch, Aave on Aptos supports several native assets including USDC, USDT, APT and Ethena’s staked USDe (sUSDe). The Aptos Foundation is backing the debut with rewards and liquidity incentives intended to accelerate adoption and bootstrap markets on the chain. Chainlink price feeds and other tooling integrations are also in place to secure oracle‑based markets.
The deployment is aimed at deepening stablecoin liquidity and enabling new collateral types such as liquid staking tokens (LSTs) for use in lending and borrowing. Aptos’ on‑chain stablecoin market and overall liquidity have grown substantially in 2025, moving from hundreds of millions to figures above the billion‑dollar mark as the ecosystem attracts more DeFi activity. These trends helped motivate the launch.
Technically, Aave V3 was re‑implemented for the Move programming model used by Aptos, with new front‑end and SDK work, extensive testing, third‑party risk parameter design, multiple audits and a sizable bug bounty to harden the deployment. The teams involved say the rollout is a template for future non‑EVM expansions, subject to governance and iterative risk adjustments.
Aptos currently hosts a smaller set of competing DeFi protocols compared with older L1s, so Aave’s arrival is expected to act as a liquidity engine for the chain and to give builders direct access to familiar lending primitives. Both Aave and Aptos said they plan to broaden supported assets and continue security programs as markets evolve.
In short, Aave’s Aptos launch brings a major lending infrastructure to a high‑performance Layer‑1 and aims to accelerate stablecoin and liquid‑staking activity on the network while serving as a blueprint for further non‑EVM deployments.
