AL Development Update | November 2025

Greetings, Aave community!

Aave Labs has continued to make steady progress on multiple protocol endeavors in line with its service provider scope, with Aave V4 development as the primary focus.

The below summary highlights developments in the Aave Protocol and reflects Aave Labs’ transparent and collaborative approach of building in public, welcoming community feedback, and fostering auditability through open-source principles.

November update:

  • Progressed Aave V4: launched the public testnet and opened the codebase, including an early version of Aave Pro.

  • Strengthened V4 security: advanced audit work, scheduled a Sherlock security contest, and continued analyzing additional scenarios for early 2026.

  • Scaled Aave V3 on Aptos: removed “training wheels,” launched USDC and USDT incentives, upgraded to Aave V3.5, raised caps, and completed GHO audits while preparing GHO launch.

  • Expanded the Aave App: launched the early access rollout of the savings‑focused experience at the Aave App.

  • Advanced the Aave Pro interface and SDK: launched the basic version of the Aave Pro and shipped the first Aave V4 SDK and docs to support integrators and power users.

  • CoW integration: rolled out CoW adapters on several chains, improved incentives tooling via Merkl, and introduced a Balancer v3‑based flash loan factory.

Aave V4 Updates

During this month, we made the Aave V4 codebase and testnet available to the wider community, accompanied by a detailed governance post outlining the configuration and testing scope. The release introduced a new evolution of the protocol that brings novel design paradigms intended to help shape the future of DeFi, including an early version of Aave Pro (the new Aave Interface), while giving service providers, integrators, and community contributors a concrete environment to explore the new design, begin integration assessments, and provide feedback. The community is already actively engaging with the release, and we encourage contributors across the ecosystem to explore the testnet, share feedback, and help shape a robust Aave V4.

Security efforts continued to advance on multiple fronts, with public audit engagements moving toward the final fixing phase, and remediations and follow‑up reviews progressing across the codebase. While no critical issues have been identified so far, auditors and security researchers have produced a number of insightful findings that have been incorporated to further harden the protocol. We also continue to collaborate closely with @Certora to review changes, assess their impact, and coordinate on the remaining verification work.

In addition to the ongoing efforts, we organized, together with Sherlock, a security contest inviting additional security experts to audit the protocol, uncover edge cases, and help make it as secure as possible. Looking ahead, we are also considering different audit scenarios for early 2026 to keep strengthening the security posture of Aave V4 ahead of the upcoming mainnet launch.

The next phase of work will focus on converging the various audit and contest results, closing remaining findings, and shifting attention to mainnet launch planning, including license framework, configuration options and rollout paths to be discussed with DAO service providers.

What else are we working on?

Aave V3 on Aptos

Activity on Aave V3 on Aptos accelerated during the month. We removed the remaining “training wheels” on the deployment and launched incentives campaigns on USDC and USDT net supply, which contributed to market growth from around 2.2M to approximately 63M in just over two weeks. In parallel, we upgraded Aave V3 on Aptos to incorporate the Aave V3.5 changes and increased supply and borrow caps to reflect the higher utilization and demand.

On the GHO side, we prepared governance temp checks covering GHO onboarding, new asset listings, and higher caps for existing assets while the current incentives campaigns still have runway. GHO audits for Aptos have been completed, and we are now preparing GHO for launch.

Aave App

We launched the early access version of the Aave App at Devconnect as a simplified entry point for users seeking a savings‑focused experience. The Aave App is accessible at aave.com/app and is designed to abstract protocol complexity while still connecting directly to Aave V3 markets. The product targets end users who are not crypto‑native, combining an innovative funds protection feature with competitive savings rates, and aiming to onboard more people into DeFi. We will continue refining the experience based on feedback from early users, as we gradually expand user access in the weeks to come.

Interface

Aave Pro (Aave V4 Interface)

Aave Pro, the new Aave Interface built specifically for Aave V4, remained a key focus this month. For the testnet release, we shipped an initial, simplified version focused on core user flows such as supplying, borrowing, repaying, withdrawing, configuring collateral, and monitoring positions, while the full interface remains in active development ahead of the planned mainnet launch. This version is intended to give users a representative testing surface for how Hubs and Spokes, credit lines, and collateral configurations will be surfaced in the final product.

Aave Pro is available at pro.aave.com and will continue to evolve as we incorporate feedback and finalize the feature set for Aave V4. We encourage active users, integrators, and other contributors to explore the interface on testnet and share feedback in the Aave V4 testnet governance thread, so we can refine the experience together.

Aave Software Development Kit (SDK)

Developer tooling also progressed, with ongoing work on the Aave SDK and supporting tooling for both Aave V3 and Aave V4. Work progressed on optimizations and design updates across the API surface, SDK abstractions, and documentation to make it easier for integrators to build consistent experiences across versions.

As part of the Aave V4 public testnet release, we also published the first version of the Aave V4 SDK together with updated docs. Additionally, we discussed and began implementing caching improvements aimed at boost performance and resilience for common integration patterns.

CoW Swaps Integration

Rollout of the new CoW adapters kicked off in the Aave Interface, starting with Base and then expanding to Gnosis, Arbitrum, and Avalanche as part of a progressively controlled release, coordinated together with the CoW team. Across the chains already integrated, we are now seeing a broad range of swap flows executing as expected, with no major issues reported so far. Over the coming weeks, we plan to continue activating the remaining networks, working toward full coverage across supported chains and a smoother swap experience for users.

Ongoing Integrations

Integrations work this month focused on strengthening existing deployments and the incentives infrastructure around them. In collaboration with @ACI and @TokenLogic, we shipped a set of bug fixes, minor enhancements, and UX improvements aligned with ongoing growth initiatives. In parallel, we refactored the Merkl incentives code so campaigns and aTokens/vTokens can support multiple reward configurations, improving flexibility when designing incentives. We also implemented a Balancer v3-based flash loan factory to support future integrations and improve capital efficiency across the ecosystem.

What’s coming next?

Our main focus for the coming month will be

  • Advancing Aave V4 toward mainnet: converging audit and contest results, closing remaining findings, and working with DAO service providers on configuration options and rollout planning.

  • Preparing GHO on Aptos for launch: finalizing governance proposals, coordinating with contributors, and aligning timing with the broader Aptos growth trajectory.

  • Expanding the Aave App early access: onboarding more waitlisted users and keep collecting feedback.

  • Iterating on Aave Pro and the Aave V4 SDK: broadening the feature set, polishing testnet flows, and improving documentation and tooling for integrators and power users.

  • Completing CoW swaps rollout and integrations: activating remaining networks, monitoring flows, and iterating on incentives and flash‑loan infrastructure.

Stay tuned for next month’s update.

Aave Labs

2 Likes