Aave Governance records recommend adjusting Aave V3 stablecoin interest-rate parameters to rebalance utilisation: raise the baseRate for USDe from 6.00% to 6.30% on Core, Plasma, Monad, Mantle, and Avalanche; lower Slope1 for USDe to 0.25% on Core and Avalanche and to 1.00% on Plasma, Monad, and Mantle; and on Monad set a 5.00% Slope1 for USDC, USDT0, GHO, mUSD, and AUSD, leaving scoped base rates, optimalUtilization, and Slope2 unchanged. The liquidity rationale is to moderate borrowing costs where utilisation is tight and keep a strong backstop past the optimal point. Intent to implement is not execution without on-chain proof.
Operative status and evidence cutoff: As of 12 September 2026 18:14:30 IST, the plan stood as recommended by Aave Governance with analysis from LlamaRisk, and implementation was intended, but no transaction hash, block confirmation, or verified before-and-after on-chain parameter state was presented. Execution therefore remains unverified, and any liquidity or rate effects are unknown at this cutoff.
Recommendation and execution status
According to Aave Governance records, the recommended changes are specific and scoped: increase USDe baseRate to 6.30% on Core, Plasma, Monad, Mantle, and Avalanche; reduce Slope1 for USDe to 0.25% on Core and Avalanche and to 1.00% on Plasma, Monad, and Mantle; and on Monad set Slope1 to 5.00% for USDC, USDT0, GHO, mUSD, and AUSD. The proposal specifies no changes to the scoped base rates for the other assets, leaves optimalUtilization unchanged, and retains the existing Slope2 across scopes.
Execution status is distinct: “recommended” and “intended” are not the same as “executed” or “effective.” In the absence of a governance payload transaction hash, block inclusion, and a confirmed before/after parameter diff on-chain, this remains a pending, unverified state. Readers can review our primer on how code changes become live settings in decentralised finance in our smart-contract operations explainer to understand why intent must be evidenced by state transitions.
USDe changes across five deployments
The plan targets USDe across five deployments (Core, Plasma, Monad, Mantle, Avalanche). The recommended increase of the baseRate from 6.00% to 6.30% modestly lifts the cost floor of borrowing, which can reduce the incentive to borrow at very low utilisation and help maintain a healthier utilisation band. Simultaneously, lowering Slope1 to 0.25% on Core and Avalanche and to 1.00% on Plasma, Monad, and Mantle flattens the gradient up to the optimalUtilization point, aiming to avoid rate spikes that can deter balanced market-making.
Importantly, Slope2 is left unchanged, keeping the steep post-optimal segment intact as a deterrent against sustained over-utilisation. Governance records attribute this configuration to striking a measured balance: a slightly higher floor via the baseRate, with gentler pre-optimal responsiveness via Slope1, and an unchanged strong backstop via Slope2. This is recommended, not verified executed.
Monad stablecoin Slope1 proposal
On Monad, Aave Governance records recommend setting a 5.00% Slope1 for USDC, USDT0, GHO, mUSD, and AUSD, while retaining the scoped base rates, optimalUtilization, and Slope2. The objective is to nudge utilisation toward target bands without materially altering the backstop for periods of stress, keeping the market responsive yet resistant to prolonged max-out conditions.
LlamaRisk’s rationale cites provider-reported observations on Monad: USDC and USDT0 sat above their optimal utilisation roughly one-third of the reviewed month, and USDT0 supply reportedly fell from about 167.3 million to 57.2 million since mid-August. These data points inform the proposed 5.00% Slope1 as a way to adjust marginal borrowing incentives near the optimal area. These are reported figures and not independently verified here.
Utilisation-curve mechanics in plain language
In Aave V3, the borrow rate is typically defined by a piecewise curve: a baseRate at zero utilisation; a gentler slope, Slope1, up to the optimalUtilization; and a steeper Slope2 beyond that point. Raising the baseRate moves the entire curve up slightly, affecting all borrowers at any utilisation. Lowering Slope1 reduces how quickly rates climb as the market approaches optimal, which can support steadier liquidity without suppressing the post-optimal deterrent.
Keeping Slope2 unchanged preserves the sharp rate increase after optimal, helping protect liquidity during crunches. The interplay among these levers shapes utilisation bands rather than targeting any specific yield. For readers seeking a refresher on how market depth, volumes, and utilisation interplay, see our market liquidity explainer. No APY is guaranteed, and outcomes depend on future, unknown market conditions.
Attributed liquidity data and its limits
LlamaRisk reported that aggregate USDe debt was about 199.7 million against roughly 1.18 billion supplied, with debt declining by about 70% since 28 August. On Monad, it reported that USDC and USDT0 were above optimal utilisation for around one-third of the reviewed month, and USDT0 supply declined from about 167.3 million to 57.2 million since mid-August. These figures are provider-reported and are cited as such, without independent replication here.
Attribution clarifies provenance but does not imply execution or confirm causality. Liquidity response, borrower behavior shifts, and liquidation outcomes after any parameter change are unknown at this time. For foundational context on stablecoin structures and constraints that can influence these metrics, see our stablecoin reserve and redemption-risk explainer. Absent verified on-chain execution evidence, any projected effect remains a scenario, not an observed result.
Borrower, depositor and liquidation implications without advice
If executed as recommended, a slightly higher baseRate on USDe would lift borrow APRs marginally at all utilisation levels, while the reduced Slope1 would temper increases as the market nears optimalUtilization. Depositor yields could adjust in line with realised borrowing, but realised returns would still depend on utilisation, fees, and market activity. This is not advice, and no return is assured.
Liquidations hinge on collateral values, oracle behavior, and accrued interest. An unchanged Slope2 suggests the protocol would still escalate rates sharply above optimal, which can compress risk windows during stress and influence the pace at which unhealthy positions become uneconomic. However, without executed changes and observed data, any discussion of borrower, depositor, or liquidation impacts remains conditional and uncertain.
India context and evidence required to confirm execution
Aave is globally accessible, but India-specific usage, routing, or liquidity effects for these assets are unknown based on the cited records. Domestic regulatory treatment and access paths for Indian market participants can vary by platform and service provider, and this article does not assess compliance, taxation, or suitability. No India exposure is inferred beyond the general, open nature of public networks.
For execution to be confirmed, one would look for a governance payload transaction hash, block confirmation, and a verifiable on-chain parameter diff showing the new baseRate, Slope1, and unchanged Slope2/optimalUtilization across the specified deployments. Official attestations from relevant Aave maintainers or risk stewards would further corroborate status. For broader context on pending governance actions and execution checks, see our Aave V4 governance-state explainer.