Aave V3 Origin

stataToken is an EIP-4626 compliant generic token vault/wrapper designed specifically for use with Aave V3 aTokens. It allows users to wrap their aTokens into a standardized vault format while maintaining eligibility for liquidity mining rewards.

Key Features

• EIP-4626 Compatibility: Standardized interface for token vaults.
• Liquidity Mining Support: Automatically accounts for rewards from the Aave ecosystem or community. Note that while the design supports infinite reward tokens, each new reward must be permissionlessly registered.
• Governance Upgradable: Deployed instances can be upgraded by Aave governance via the Level 1 executor.
• Permissionless Deployment: New stataToken instances for newly listed assets can be deployed by anyone using the StataTokenFactory.

Aave v3.3 is an upgrade to the Aave V3 protocol designed to improve debt management, liquidations, and compatibility with the upcoming Umbrella system.

Key functional improvements include:

• Bad Debt Management: Implementation of bad debt logging and burn functionality to handle unresolvable debts, enabling compatibility with automated bad debt coverage via the Umbrella system.
• Liquidation Optimisations: Refined liquidation algorithms aimed at reducing 'dust' debt positions and improving economic efficiency for liquidators.
• Protocol Optimisations: Various improvements to data reading and protocol configurations.

The solvency property for the repay() function is verified using Certora specifications split into two primary files:

1. main.spec: Contains the primary proof for the main solvency property.
2. lemma.spec: Contains proofs for several assumptions required by main.spec to ensure the verification process is efficient and avoids timeouts.

Key assumptions proven in lemma.spec include:

• Non-zero supply: Proves that if the scaled-total-supply of variable-debt is 0, the call to repay() reverts.
• Index Summarization: To prevent verification timeouts, the functions getNormalizedIncome() and getNormalizedDebt() are summarized as the constant values LIQUIDITY_INDEX and DEBT_INDEX, respectively. This relationship is justified in the repay__index_unchanged() rule within lemma.spec.

The AaveV3ConfigEngine is a helper smart contract designed to abstract best practices for performing 'admin' interactions with the Aave v3 protocol. It acts as an orchestration layer that sits on top of core contracts without modifying them. It provides a simplified interface for developers to create governance proposal payloads for common tasks such as:

• Listing new assets
• Modifying supply and borrow caps
• Changing collateral or borrow-related parameters
• Updating asset price feeds
• Managing eMode (Efficiency Mode) configurations

Aave v3.1 introduced a stateful interest rate strategy to reduce errors when connecting new strategy contracts. Instead of using immutable parameters on separate contracts for each asset, parameters are now stored in a mapping within a single default interest rate contract.

Key Features:

• Single Contract: A single DefaultReserveInterestRateStrategyV2 can be connected to all assets.
• Rate Limits: A strict upper limit is enforced (currently 1000%) to prevent chaotic protocol reactions to extreme rate configurations.
• Configuration: Rate parameters (base variable borrow rate, slope1, slope2) are managed via the PoolConfigurator using setReserveInterestRateData().

In Aave v3.3, deficits are used to manage bad debt. Deficits are tracked via reserve.deficit and accumulate over time.

Key behaviors:

• Creation: A deficit is created during a liquidation if the user's total collateral across all reserves becomes zero in the base currency, while their total debt remains non-zero.
• Reduction: Deficits can only be reduced by burning claims, which reduces the protocol's obligations in reserve.deficit.
• Interest Rates: For interest rate calculations, the deficit is treated as an 'unbacked' parameter, meaning it reduces the utilization rate.
• Constraints: Deficits can only be created or eliminated for active reserves. However, an edge case allows deficit creation/elimination on paused reserves if they are not the main liquidated asset.

Aave handles AToken fees (from liquidations or accrued debt interest) by first "accounting" for them in reserve.accruedToTreasury rather than minting them immediately to the treasury. The actual minting is performed later via the permissionless Pool.mintToTreasury function.

Implications for developers:

• Complexity: When calculating or fetching AToken.totalSupply, you must account for reserve.accruedToTreasury to get the real total supply.
• Gas vs. Predictability: This approach reduces gas costs for the user triggering the state update, but it makes the value of non-minted shares less predictable and introduces potential rounding imprecisions due to multiple asset-to-share conversions.