Aave Labs has published an ARFC on its governance forum that would create a standardized technical framework for assets seeking listing, continued listing, or major parameter expansion across V3, V4, and Horizon. The proposal was posted on May 29, 2026, and announced through Aave’s official X account the same day. It is still a governance proposal, not an approved protocol change.
One checklist for listings, expansions, and post-list reviews
The proposal is aimed at replacing uneven technical standards with a single framework. Under the ARFC, the same rule set would apply to three situations: adding a new asset, expanding the parameters of an asset that is already listed, and carrying out ongoing monitoring after listing. That means requests for higher supply caps, higher borrow caps, or collateral-related changes would be evaluated against the same baseline used for fresh listings.
Aave Labs says the purpose is to make technical requirements consistent across the protocol’s different environments. In practice, that would give governance a clearer reference point when market conditions shift and an existing asset needs review. It would also formalize the checks performed after listing, with the goal of identifying emerging risks before they become protocol-level issues.
The proposal spans Aave’s three active protocol environments
The scope is unusually broad. Aave V4 went live on mainnet on March 30, 2026, bringing a modular hub-and-spoke design intended to improve capital efficiency and support a wider range of assets. Its first deployment was intentionally conservative, with three hub types — Core, Plus, and Prime — and eleven spokes. Supply and borrow caps were limited at launch to prioritize security. According to the source material, V4 followed nearly two years of development and a year-long security effort involving multiple audit firms and a public bug bounty, with no critical vulnerabilities found.
Horizon adds another layer to the listing question. The product allows institutions to borrow stablecoins against tokenized real-world assets, including US Treasuries, and has passed $580 million in net deposits. As Aave expands into institutional lending and RWA-backed markets, the range of assets entering its ecosystem becomes more complex. A common listing framework would reduce the chance of different standards emerging across parallel products.
Governance process is still underway
The ARFC is currently in the community feedback phase. Aave governance usually moves from an ARFC to a Snapshot vote and then to an on-chain vote, a process that often takes two to four weeks depending on feedback volume and community participation. AAVE holders take part in these discussions and votes, while the token also serves a protocol-wide risk function through the Safety Module. That ties asset quality directly to governance, rather than leaving it as a purely technical matter.
Why Aave is formalizing listing standards now
The proposal addresses a problem DeFi has seen before: weak listings can expose protocols to oracle manipulation, thin-liquidity markets, and other avoidable risks. A published technical checklist makes it harder for lower-quality assets to pass through governance without meeting a defined threshold. The timing also aligns with Aave’s push into institutional products. In his 2026 roadmap post, Stani Kulechov said Aave would host new markets, new assets, and new integrations not previously seen in DeFi. For institutional participants, a documented and auditable process matters before capital is committed.
The ARFC is now live on governance.aave.com, where community members can review the full text and submit feedback before Snapshot voting begins. Whether the framework becomes policy will depend on the next stages of governance.

