Aave Proposal Seeks $3.5M Added Annual Revenue via Reserve-Factor Shifts

TokenLogic has proposed reserve-factor changes across 54 reserves on Aave that its model estimates would add $3.5 million in annual protocol revenue, using balances and rates from November 9. Governance has not yet approved the changes.

The proposal, submitted on November 12 to Aave's governance forum under the "Direct to AIP" process, covers 12 Aave V3 instances plus Aave V2 on Ethereum. It would raise the modeled blended reserve factor from 12.0% to 12.7%.

What does the reserve factor control?

Aave's official FAQ defines the reserve factor as the percentage of borrowing interest that accrues to the treasury. Governance sets the factor separately for each asset, and Aave Governance — not a conventional corporate treasury function — controls the resulting funds.

The mechanics are simple arithmetic. If borrowers generate $100 of interest under a 20% reserve factor, $20 goes to the treasury and $80 remains for suppliers. Raising the factor to 25% changes the split to $25 and $75. The total interest paid by borrowers does not change when the allocation does.

That split explains the trade-off: higher factors lift treasury receipts while reducing the appeal of supplying the same market. The percentage itself should not be read as an annual return paid to either side.

How would suppliers be affected?

Individual adjustments vary sharply by market. TokenLogic proposes moving Ethereum Core DAI's factor from 25% to 30%, while Avalanche V3 USDC would jump from 10% to 25%. The proposal's stated purpose includes reshaping incentives across legacy markets as Aave's newer infrastructure develops.

The parameter change does not directly alter borrower interest rates. Over time, supplier responses could shift available liquidity and utilization, which is why the $3.5 million figure is a mechanical estimate rather than a forecast of realized revenue.

Why does V4 change the calculation?

Aave's official protocol changelog records the launch of V4 on Ethereum in March and on Avalanche in July. The architecture groups liquidity into hubs and separates lending activity into spokes, changing how markets are organized.

That deployment history makes cross-version comparisons commercially relevant. A supplier weighing a yield change can now compare competing protocols and different Aave deployments side by side, each with distinct assets, liquidity conditions and operational characteristics.

Governance is effectively making an allocation decision about where activity should be encouraged. A portfolio-wide revenue estimate can mask widely different outcomes for suppliers of individual assets, which argues for market-level scrutiny rather than aggregate analysis alone.

What happens next?

The $3.5 million figure annualizes a single snapshot. Borrowed balances, interest rates and liquidity can all move after a parameter update, so the estimate mainly provides a basis for comparison.

Governance must also weigh the cost of retaining liquidity and the resilience of each market. An extra dollar of treasury income carries less value if the new settings trigger an offsetting loss of activity or weaken a market's funding base.

Broader interest in AAVE ownership — including Payward's recently disclosed stake — extends the audience for these economics. Next steps are community feedback and an on-chain proposal, with measurable results to follow if the changes are approved and executed.