Headline: TokenLogic proposes shifting Aave’s reserve factors — estimates $3.5M annual boost, but market reaction could change the math
TokenLogic has submitted a governance proposal that would tweak reserve factors across 54 Aave reserves, raising the protocol’s modeled share of lending income. Using Aave balances and rates from November 9, their model projects about $3.5 million in additional annual revenue for the treasury if the changes are enacted — but governance has not yet approved the updates.
What’s being proposed
- The November 12 submission covers 12 V3 deployments plus Aave V2 on Ethereum. TokenLogic’s blended reserve factor — the share of interest that flows to the treasury — would rise from 12.0% to 12.7% under the modeled changes.
- Examples called out in the proposal: Ethereum Core DAI would move from a 25% reserve factor to 30%, while Avalanche V3 USDC would shift from 10% to 25%.
- In total, the proposal adjusts 54 reserve factors across Aave markets to change how lending income is allocated between the protocol treasury and liquidity suppliers.
What the reserve factor actually controls
- Aave’s reserve factor is the percentage of borrower interest that accrues to the protocol treasury (set per asset via governance). It does not change the absolute interest generated by borrowers immediately — it only reallocates how that interest is split.
- Simple illustration: If borrowers pay $100 of interest and the reserve factor is 20%, $20 goes to the treasury and $80 goes to suppliers. Raising the factor to 25% would make it $25/$75 instead. The total interest in this snapshot hasn’t grown — only the division between treasury and suppliers changes.
Why this matters for suppliers and the protocol
- A higher reserve factor improves short-term treasury receipts but reduces the share of interest suppliers receive in affected markets. That can alter supplier incentives, liquidity depth, and market utilization over time.
- The proposal’s immediate tweaks do not change borrower APRs. However, if suppliers withdraw liquidity in response, utilization and thus rates could shift later — meaning the modeled revenue is a mechanical snapshot, not a guaranteed long-term outcome.
- TokenLogic frames some changes as rebalancing incentives across legacy markets while Aave’s newer infrastructure is adopted.
Context: Aave V4 and internal comparisons
- Aave launched V4 on Ethereum (March) and Avalanche (July), adopting a hubs-and-spokes architecture that isolates liquidity and risk per hub/spoke. That architecture means suppliers can compare not only competing protocols but different Aave deployments with distinct conditions.
- The governance decision is, effectively, about where on-chain activity should be encouraged. A portfolio-wide revenue estimate can obscure very different outcomes for suppliers of individual assets; each market needs scrutiny on its own terms.
Caveats and next steps
- TokenLogic’s $3.5M figure annualizes a November 9 snapshot. Borrowed balances, interest rates, and liquidity can and will change after a parameter update, so realized revenue could be materially different.
- Governance must weigh the benefit of higher treasury income against the risk of reduced liquidity or more fragile markets. An extra dollar to the treasury may be counterproductive if it discourages supply or concentrates risk.
- The proposal will undergo community feedback and (if it clears discussion) an on-chain governance vote. Only after approval and execution would measurable effects start to accumulate.
Why this matters to a broader audience
- Interest in Aave governance and AAVE ownership is growing — including outside investment such as Payward’s recently disclosed stake — so the economic design choices here are of wide relevance to tokenholders, suppliers, and protocol users.
By the News Desk; edited by Samuel Rae.
TokenLogic has submitted a governance proposal that would tweak reserve factors across 54 Aave reserves, raising the protocol’s modeled share of lending income. Using Aave balances and rates from November 9, their model projects about $3.5 million in additional annual revenue for the treasury if the changes are enacted — but governance has not yet approved the updates.
What’s being proposed
- The November 12 submission covers 12 V3 deployments plus Aave V2 on Ethereum. TokenLogic’s blended reserve factor — the share of interest that flows to the treasury — would rise from 12.0% to 12.7% under the modeled changes.
- Examples called out in the proposal: Ethereum Core DAI would move from a 25% reserve factor to 30%, while Avalanche V3 USDC would shift from 10% to 25%.
- In total, the proposal adjusts 54 reserve factors across Aave markets to change how lending income is allocated between the protocol treasury and liquidity suppliers.
What the reserve factor actually controls
- Aave’s reserve factor is the percentage of borrower interest that accrues to the protocol treasury (set per asset via governance). It does not change the absolute interest generated by borrowers immediately — it only reallocates how that interest is split.
- Simple illustration: If borrowers pay $100 of interest and the reserve factor is 20%, $20 goes to the treasury and $80 goes to suppliers. Raising the factor to 25% would make it $25/$75 instead. The total interest in this snapshot hasn’t grown — only the division between treasury and suppliers changes.
Why this matters for suppliers and the protocol
- A higher reserve factor improves short-term treasury receipts but reduces the share of interest suppliers receive in affected markets. That can alter supplier incentives, liquidity depth, and market utilization over time.
- The proposal’s immediate tweaks do not change borrower APRs. However, if suppliers withdraw liquidity in response, utilization and thus rates could shift later — meaning the modeled revenue is a mechanical snapshot, not a guaranteed long-term outcome.
- TokenLogic frames some changes as rebalancing incentives across legacy markets while Aave’s newer infrastructure is adopted.
Context: Aave V4 and internal comparisons
- Aave launched V4 on Ethereum (March) and Avalanche (July), adopting a hubs-and-spokes architecture that isolates liquidity and risk per hub/spoke. That architecture means suppliers can compare not only competing protocols but different Aave deployments with distinct conditions.
- The governance decision is, effectively, about where on-chain activity should be encouraged. A portfolio-wide revenue estimate can obscure very different outcomes for suppliers of individual assets; each market needs scrutiny on its own terms.
Caveats and next steps
- TokenLogic’s $3.5M figure annualizes a November 9 snapshot. Borrowed balances, interest rates, and liquidity can and will change after a parameter update, so realized revenue could be materially different.
- Governance must weigh the benefit of higher treasury income against the risk of reduced liquidity or more fragile markets. An extra dollar to the treasury may be counterproductive if it discourages supply or concentrates risk.
- The proposal will undergo community feedback and (if it clears discussion) an on-chain governance vote. Only after approval and execution would measurable effects start to accumulate.
Why this matters to a broader audience
- Interest in Aave governance and AAVE ownership is growing — including outside investment such as Payward’s recently disclosed stake — so the economic design choices here are of wide relevance to tokenholders, suppliers, and protocol users.
By the News Desk; edited by Samuel Rae.