Particle.news

Aave Labs Proposes Technical Asset Listing Framework for V3, V4 and Horizon

The proposal seeks to make technical reviews consistent so price feeds, token behavior, and contract privileges are checked before governance decides.

Overview

  • Aave Labs published an Aave Request for Comment on Friday that lays out a unified Technical Asset Listing Framework to guide listings and parameter changes across Aave V3, V4 and Horizon.
  • The framework defines eight technical review areas and requires a Chainlink price feed on the target chain with Capped Asset Price Oracle (CAPO) adapters for yield-bearing assets where needed.
  • Token rules make strict ERC20-compliant behavior a baseline by banning fee-on-transfer, rebasing, ERC777 hooks, and other transfer logic that breaks predictable accounting.
  • A new five-level access-control model forces documentation and classification of every privileged role such as owners, minters, pausers, blacklisters and bridge operators to measure role concentration and failure modes.
  • The proposal sets pre-screening gates, separates factual findings from risk recommendations, mandates annual and event-triggered refreshes, and leaves final onboarding and parameters to the Aave DAO after a comment and coordination period.