This ARFC proposes renewing and expanding the Aave Chan Initiative’s (ACI) mandate as the Aave DAO’s Growth and Governance Coordination service provider. Focusing on sustained protocol growth, strategic alignment, and governance operational excellence.
Since its inception, ACI has served as the growth engine and governance orchestrator for the Aave DAO. Through managing incentive programs, launching key protocol initiatives, building strategic partnerships, and contributing to governance frameworks, ACI has delivered consistent, high-impact results. During 2024, Aave’s share of the active loan market increased from below 50% to 71.2%, significantly outperforming competitors across the DeFi landscape.
To keep this proposal concise, a retrospective of ACI’s past mandate has been published separately
Our core KPI: reach 80% of total active DeFi loans across all tracked platforms by expanding Aave’s competitive edge through product innovation, liquidity programs, and strategic onboarding and business development.
Extend the Merit-as-a-Service Incentive Vault model as the standard growth and incentives engine for partners using Aave and DeFi in general. Building on early adoption from Circle, Tether, Ava Labs, Stader and others, Phase IV will onboard new MASIv clients and create synergistic feedback loops for the Aave ecosystem.
Deliver a CeDeFi partnership with a top-tier centralized exchange providing CeFi access to DeFi-native yield.
Continue developing Frontier, our Aave-native node infrastructure, on a larger scale. Ensure DAO readiness for Ethereum’s Pectra upgrade and expand node partnerships with Lido, EtherFi, and others.
Establish ACI’s readiness to operate across non-EVM chains, beginning with Aptos, in preparation for a multi-VM DeFi future.
Expand the ACI core team (currently 8 members) with new hires in technical, governance, and ecosystem roles.
ACI deliverables are executed on a best-effort basis, with transparency and proactive communication regarding any limitations or delays, while aiming to exceed expectations whenever possible.
ACI is not a core developer or maintainer of the Aave protocol codebase. We rely on technical service providers’ tooling and infrastructure. While we have provided support in the past, ACI will not develop protocol infrastructure tools during this mandate.
For non-EVM ecosystems and Aave V4 (whose codebase is currently unknown to ACI), we will fully depend on technical service providers like @aavelabs to provide the necessary tooling and documentation to fulfill our responsibilities.
The ACI clearly defines the following activities as out of scope, based on either our internal capabilities or to respect the roles of other Aave DAO service providers:
Copyright and related rights waived via CC0.
https://app.aave.com/governance/v3/proposal/?proposalId=301