Aave v3 (Ethereum)

Aave v3 DefaultReserveInterestRateStrategy per reserve — a two-slope function of utilisation with a kink at the optimal ratio: algorithmic_utilisation per v1 §8.2.

Aave v3 Pool 0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2 — borrow()/repay() carry no maturity; a position persists until repaid or liquidated.

Aave v3 Pool 0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2 — the variable rate is recomputed from utilisation on every ReserveDataUpdated. Aave v3 did ship a STABLE borrow mode that was fixed at origination (though rebalanceable by the protocol); it was frozen and then removed across deployments, so no current borrowing is fixed at origination. Our ledger keeps its stable_* columns because historical positions used it.

Aave v3 PoolAddressesProvider 0x2f39d218133AFaB8F2B819B1066c7E434Ad94E9e → getPriceOracle(). AaveOracle holds one source per asset (setAssetSources) across every reserve, plus a fallback oracle, and governance can replace any of them. A pooled venue's solvency depends on all of the feeds backing the reserves an account touches, not on one.

Aave v3 Pool 0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2 — liquidationCall() is permitted once an account's health factor falls below 1e18, computed from per-reserve liquidation thresholds across the account's whole collateral basket.

Aave v3 Pool 0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2 — supply() transfers the underlying to the reserve's aToken contract under the Pool's control; the depositor holds an aToken claim rather than the asset.

Aave v3 Pool 0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2 — liability is bounded by the account's collateral. Aave v3.3's DeficitCreated writes off the residual debt of a borrower with nothing left to seize: the protocol absorbs the shortfall rather than pursuing the borrower. (That same event is why this venue's composition axis is still unvalidated — see the readiness matrix, hole #3.)

credit_aave_reserves, resolved on-chain in R1 from the Pool's reserve list and flagged is_btc by address. NOTE: Aave is POOLED and multi-collateral, so a BTC reserve's presence does not mean a given borrow is secured by it — attributing a borrow to Bitcoin specifically is a modelling decision (v1 §6.4), which is why this venue's composition coverage reads `partial` rather than `full`.