color: var(color-red-500)

by

Aave Proposes New Framework to Tighten Crypto Asset Listings

Aave Labs is pushing for more defined and transparent standards when it comes to adding crypto assets to its platform. This new technical approach could significantly impact how decisions are made within the decentralized finance (DeFi) space.

Aave Labs is suggesting a new plan to create a consistent process for adding crypto assets to its platform.

This proposal, currently under review, focuses on Aave V3, V4, and Aave Horizon. It details a clear process for adding new assets, managing current ones, and making significant changes to their settings.

We also want to standardize the process, making it clearer and easier to follow each time. This will also give us a starting point for regularly checking the performance of assets that are already listed.

Read also: 

Aave DAO Doubles Down on Growth, Approves $25M Aave Labs Grant

Aave’s New Asset Listing Rules Target Technical Safety

The framework focuses on technical eligibility. 

This doesn’t replace the usual checks for market risk, sufficient funds, or responsible decision-making. It’s designed to be used with, not instead of, the risk assessments already in place.

As a researcher, I’ve been looking into the technical framework Aave Labs has developed, and it focuses on a few key areas. These include making sure it works with standard ERC20 tokens, ensuring the data feeds (oracles) are trustworthy, controlling who has access to the system, allowing for future upgrades, and managing how it connects to other blockchains (bridge topology). Each of these areas has its own specific set of tests and standards we’re using to evaluate it.

The proposal emphasizes that any asset relying on information or processes outside of the blockchain needs to be carefully reviewed. This includes things like tokenized real-world assets and assets held by custodians. Any off-chain arrangements that could impact the asset’s supply or ability to be redeemed must be clearly explained and evaluated.

Assets are expected to go through a pre-screening stage before a full technical review begins. 

Next, we need to verify how the asset is categorized according to Aave’s rules. Any asset falling into a prohibited or sanctioned category will not be moved forward.

Aave Labs has introduced a proposal for a consistent way to add new digital assets to Aave V3, V4, and Aave Horizon. This framework aims to standardize the technical listing process for these platforms.

This system sets clear technical standards for how items are listed, how details are added, and how everything is continuously checked to ensure it’s working properly.

— Aave (@aave) May 28, 2026

Key Technical Requirements Under the Proposed Framework

This system organizes project needs into eight key areas: compatibility with the ERC20 standard, how external data is handled, who can access what, how token values are determined, the token’s overall structure, potential risks when connecting to other systems, the record of security reviews, and any outside tools or services it relies on.

On the oracle side, a Chainlink price feed must exist on the target chain. 

Any changes to the usual settings need a clear explanation. Investments that earn returns should use a CAPO adapter when necessary.

It’s crucial to carefully manage who has access to important functions. We need a clear record of which roles have special permissions on both the main token contract and any related contracts.

This system uses a five-level security ranking for people with different job roles. Roles protected by only one private key, or a simple multi-signature setup, receive the lowest security ratings.

We also have strict audit requirements. Any asset you want to list must have a recent, trustworthy audit that specifically covers the version currently in use. Any serious or high-priority issues identified in the audit must be fixed before we can approve your listing.

How the Framework Fits Into Aave Governance

As a researcher, I’ve been following Aave Labs’ new governance process closely. They’ve laid out a pretty straightforward system for implementing their framework. It begins with an initial screening phase, then progresses through technical reviews, coordination with risk providers, and finally, official publication through governance channels.

Each stage feeds into the next.

The process includes continuous monitoring, and all assets currently in use must be assessed each year.

Contract upgrades, new chain deployments, or security incidents trigger immediate reviews.

Technical reviews directly impact our rules and policies. This could mean things like limiting how much of an asset can be supplied, lowering how much someone can borrow against it, or delaying when new users can join the platform.

If a decision is made even though some issues haven’t been fully addressed, the proposal needs to clearly explain any remaining risks.

Aave Labs explained that this framework isn’t designed to hinder assets that already have good security measures. Instead, it aims to identify and address technical problems early on, before they can cause bigger issues for the protocol.

Read More

2026-05-29 10:16