Aave Labs Unveils Asset Listing Framework for Token Listings

• Aave Labs published a technical framework covering eight checks for asset listing on V3, V4, and Horizon.
• Assets failing checks face reduced caps, lower LTV ratios, or delayed onboarding, not automatic rejection.
• Framework covers Oracle quality, access control, bridge risk audit history, and ERC20 compliance checks.

Not every token deserves a spot on one of DeFi’s biggest lending protocols. Aave Labs is now putting that principle in writing.

The protocol’s development arm has published a proposal introducing a standardized Technical Asset Listing Framework for Aave V3, V4, and Horizon. The goal is to make it harder for low-quality or risky assets to get listed, and make the requirements clear enough that everyone can see exactly what the standard is before submitting a proposal.

Почему это важно

Aave is one of the largest lending protocols in crypto. When an asset gets listed as collateral, users can borrow against it.

If that asset has a hidden flaw, an unbounded minting function, a weak upgrade controller, a stale oracle, or a bridge that can be drained, the entire protocol absorbs that risk. The new framework is essentially Aave, drawing a clear line between assets that meet a technical baseline and those that do not.

What Gets Checked

The framework covers eight core areas that every asset must pass through before listing or material expansion:

• ERC20 compliance — does the token behave predictably without hidden fees, rebasing, or problematic hooks
• Oracle quality — is there a live Chainlink feed with proper heartbeat and deviation thresholds
• Access control — who can mint, burn, pause, or upgrade the token, and how secure are those roles
• Exchange rate integrity — for yield-bearing assets, can the rate be manipulated in a single transaction
• Token architecture — are there duplicate supply entry points or hidden transfer restrictions
• Bridge and cross-chain risk — for multi-chain assets, is the bridge verified, and are mint limits in place
• Audit history — is the deployed code covered by recent reputable audit work with no unresolved critical findings
• External dependencies — are staking protocols, custodians, and redemption infrastructure assessed for their own risks

What Happens If An Asset Fails

A weak finding does not automatically block listing, but it has consequences. Reduced supply caps, lower loan-to-value ratios, no collateral usage, or delayed onboarding are all on the table. Governance retains final discretion but must publicly state any residual risk it is choosing to accept.

The framework also introduces annual refresh reviews for all actively listed assets, meaning the bar does not just apply at the door; it applies throughout the asset’s life on the protocol.

Связано: AAVE приземлилась на Solana, а Фонд Solana принимает инициативу в поддержку восстановления DeFi