Aave Governance Reviews Proposal to Shrink Six Low-Volume Markets

,

. Also keep proper nouns like Aave, LlamaRisk, Sonic, Scroll, etc. in English. - Meta description: Translate. We'll produce a JSON object. Let's translate carefully. Title: "Aave Governance Reviews Proposal to Shrink Six Low-Volume Markets" -> "การกำกับดูแลของ Aave ทบทวนข้อเสนอที่จะลดขนาดตลาดที่มีปริมาณต่ำหกแห่ง" or similar. But we need natural Thai. Maybe "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่มีสภาพคล่องต่ำ 6 แห่ง" but "shrink" could be "ลดขนาด" or "ยุบ" (wind down). Since the article talks about winding down, maybe "ยุบ" is better. But title says "shrink" - we can use "ลดขนาด" or "ยุบ". Let's use "ยุบ" as it's more direct. Also "Governance" -> "การกำกับดูแล" or "ผู้บริหาร" but in crypto context, "การกำกับดูแล" is fine. Or "Aave Governance" could be "คณะกรรมการกำกับดูแลของ Aave" but we'll keep it simple. I'll translate: "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่มีปริมาณต่ำหกแห่ง" but "ปริมาณต่ำ" might be "low-volume" meaning low trading volume. Maybe "ตลาดที่มีปริมาณการซื้อขายต่ำ" but that's long. The article says "low-adoption markets" and "low-volume markets". We can use "ตลาดที่มีสภาพคล่องต่ำ" but that's liquidity. Actually "volume" here means trading volume or usage. Let's use "ตลาดที่ใช้งานน้อย" or "ตลาดที่มียอดใช้งานต่ำ". But to match "low-volume" we can say "ตลาดที่มีปริมาณต่ำ". I'll go with "ตลาดที่มีปริมาณต่ำ" but it might be ambiguous. Alternatively, "ตลาดที่ซบเซา" but that's sluggish. I think "ตลาดที่มีปริมาณการใช้งานต่ำ" is clearer. But the title is short. Let's keep it concise: "Aave ตรวจสอบข้อเสนอที่จะยุบตลาดที่ใช้งานน้อย 6 แห่ง" - that's fine. But we need to preserve the meaning: "Reviews Proposal" - "ตรวจสอบข้อเสนอ" or "พิจารณาข้อเสนอ". "Shrink" - "ยุบ" (wind down) or "ลดขนาด". Since the article says "wind down", I'll use "ยุบ" in the title. Let's craft: "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่มีปริมาณต่ำหกแห่ง" - but "ปริมาณต่ำ" is okay. Better: "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่มีการใช้งานต่ำ 6 แห่ง" - that's clear. I'll go with: "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่ใช้งานน้อย 6 แห่ง" But we need to keep "Governance" - maybe "การกำกับดูแลของ Aave" but that's longer. In the article, it says "Aave's governance" so we can translate as "การกำกับดูแลของ Aave" but for title we can just say "Aave" as subject. I'll use "Aave ตรวจสอบข้อเสนอ..." and omit "Governance" because it's implied. Alternatively, "Aave Governance" is a term, so we could keep "Aave Governance" in English? But requirement says translate naturally. I'll translate. Let's do: "การกำกับดูแลของ Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่มีปริมาณต่ำหกแห่ง" - but that's a bit long. I'll simplify: "Aave ตรวจสอบข้อเสนอเพื่อยุบตลาดที่ใช้งานน้อย 6 แห่ง" But "Governance" is the body, so maybe "คณะกรรมการกำกับดูแลของ Aave" but that's too formal. I'll keep "Aave" as the entity. In the content, we have "Aave's governance" - we'll translate as "การกำกับดูแลของ Aave" or "ผู้บริหารของ Aave". I'll use "การกำกับดูแลของ Aave" for consistency. Now content translation: Original article:

Aave's governance is weighing a proposal to wind down six underperforming V3 markets and offboard dozens of low-use reserves. The move, still in early discussion, targets deployments on Sonic, Scroll, zkSync, Metis, Soneium, and Aptos — chains where activity has failed to cover basic operational costs.

Why the cleanup is needed

The proposal, submitted by risk analysis firm LlamaRisk, argues that maintaining small, low-adoption markets carries operational risk and cost that outweigh any benefit. These six markets collectively hold $98.1 million in deposits and $15.6 million in debt — less than 1% of Aave's total deposits. Yet they generated under $5,000 per quarter, not enough to pay for oracles and monitoring.

LlamaRisk's rationale is straightforward: Aave is one of DeFi's most important lending protocols, and resources should focus on larger, more productive markets. The proposal also includes offboarding 50 low-use reserves and 21 matured Pendle Principal Tokens across the broader Aave ecosystem.

The markets and the numbers

The affected chains are all part of Aave's V3 expansion into layer-2 networks and alternative L1s. Sonic, Scroll, zkSync, Metis, Soneium, and Aptos each host a V3 market that never gained meaningful traction. Combined, they represent a tiny slice of Aave's $15 billion-plus deposit base.

Debt on these markets is just $15.6 million, and the revenue they generate is negligible. LlamaRisk's analysis suggests the cost of maintaining separate oracle feeds, risk monitoring, and governance overhead for each market exceeds the income. The proposal doesn't specify exact cost figures, but the gap is clear: less than $5,000 per quarter in revenue versus ongoing operational expenses.

The proposal is currently at the ARFC stage — Aave's first formal step in governance. That means it's still under discussion, not a done deal. The community can debate, suggest changes, or reject it. If it gains enough support, it will move to a Snapshot vote, then to an on-chain AIP (Aave Improvement Proposal) for final execution.

LlamaRisk has not set a timeline for the next steps. The affected markets remain live for now. Users with positions on those chains can still interact with them, but the proposal signals that Aave's governance is willing to prune underperforming branches to keep the protocol lean. The question now is whether the community agrees that small, quiet markets are more trouble than they're worth.