Aave Labs Proposes New Asset Listing Rules to Improve Protocol Safety

Highlights:

• Aave Labs wants to make asset reviews clearer before tokens gain more protocol exposure.
• The framework checks token design, oracle quality, bridge risks, and important admin powers.
• Aave governance may use these reviews to set limits, monitoring needs, or listing timelines.

Aave Labs proposed a new Technical Asset Listing Framework on Thursday to make asset reviews clearer and more consistent across the Aave ecosystem. The proposal was published on the Aave governance forum and applies to assets seeking new listings, continued listings, or major parameter expansions on Aave V3, Aave V4, and Horizon.

Advertisement

The framework aims to provide Aave governance with a standard way to assess the technical safety of assets before they receive greater exposure within the protocol. Aave Labs said the process should make listing requirements more transparent and repeatable across governance proposals.

Aave Plans Major Overhaul For Token Listings

Aave Labs (@aave) $AAVE has proposed a standardized framework for reviewing assets across Aave V3, V4 and Horizon.

The proposal aims to make token listings and parameter expansions more transparent and consistent.

The framework… pic.twitter.com/o2JiykLQG0

— BSCN (@BSCNews) May 29, 2026

Aave is a decentralized finance lending protocol where users can supply crypto assets, borrow funds, and use assets as collateral. Because of this, every listed asset can affect liquidations, collateral settings, oracle design, and protocol solvency. A poorly designed token, weak bridge setup, or unreliable oracle can create risks that are not visible from market data alone.

The proposed framework does not replace market-risk analysis, liquidity checks, legal review, or final DAO decisions. Instead, it adds a technical baseline for assets. Governance members and risk providers can then use the findings to decide on supply caps, borrow caps, loan-to-value ratios, collateral use, and other risk settings.

Aave Labs said the framework would apply to new assets, existing assets with major changes, and listed assets that need regular technical refreshes. It would also apply separately to each chain. If an asset exists on more than one blockchain, its contracts, oracle path, bridge design, access controls, and dependencies must be reviewed for each relevant chain.

New Framework Covers Token, Oracle, and Bridge Risks

The framework also links each asset to Aave’s Asset Classification Framework. Assets in non-approved or sanctioned categories should not move forward in the review process.

The proposal focuses on several key technical areas. Assets must follow expected ERC20 behavior, including clear token details, predictable transfers, and safe smart contract compatibility. Aave Labs said assets with fee-on-transfer behavior, rebasing features, unsupported decimals, or unsafe token hooks may need fixes before listing.

Aave also wants every listed asset to have a reliable price feed. The proposal says Chainlink should remain the main option unless another price source has a strong reason. For yield-bearing assets, Aave Labs said extra checks may be needed because their value can change through exchange rates or price growth over time.

The framework also looks closely at who controls the token contracts. Issuers would need to share details about any roles that can mint, burn, pause, blacklist, upgrade, or manage the token. If these powers are too broad or unclear, Aave may limit the asset’s listing or reduce the asset’s exposure within the protocol.

Bridge risk is another key area. For bridged assets, reviewers would need to check where the token comes from, how it moves to another chain, which bridge supports it, and what limits or controls are in place. Aave Labs said a weak bridge on the original chain can create risks for the full cross-chain supply.

Aave Governance to Keep Final Control

The proposal also asks for clear technical reports during governance discussions. These reports may explain the main findings, potential risks, required fixes, remaining concerns, and any applicable limits. Based on these findings, Aave governance may decide to set lower supply caps, lower borrow caps, lower collateral values, implement additional monitoring, or adopt a slower listing process.

Aave Labs also wants listed assets to be reviewed regularly. Active assets should go through an annual technical refresh. A review may also be needed sooner if there is a contract upgrade, a new chain deployment, a bridge change, a role-holder change, a mint-cap update, a dependency change, or a security incident.

The proposal says the framework should not slow down simple assets that already have strong controls. Its main goal is to make listing rules more predictable and to help the DAO identify technical problems before they become real risks to the protocol.

Advertisement