Aave V3 Origin v3.7.0 removes legacy mechanisms from core contracts

Aave V3 Origin v3.7.0 removes dropReserve, priceOracleSentinel from execution parameters and the legacy isolationModeTotalDebt path. The release simplifies core contracts and changes several internal liquidation and borrowing assumptions.

Aave V3 Origin v3.7.0 removes legacy mechanisms from core contracts

Aave DAO released Aave V3 Origin v3.7.0 with a substantial cleanup of core-contract behavior. `dropReserve()` is no longer supported at the Pool level, removing reserve deletion from the current pool interface. The release also removes `priceOracleSentinel` from execution parameters used by borrowing and liquidation flows and drops the legacy `resetIsolationModeTotalDebt()` path.

The `isolationModeTotalDebt` field in `ReserveData` is now deprecated and returns zero in view functions. `liquidationCall` no longer updates isolation-mode debt, reflecting the protocol’s move away from that older accounting mechanism. Integrators should therefore avoid treating the deprecated field as a live source of state.

The release shows a broader simplification direction for Aave V3 Origin: transitional or defensive mechanisms are being removed from execution paths when they no longer fit the current architecture. That reduces the number of special cases carried by contracts, downstream tooling and security reviews.

For operators and integrators, v3.7.0 is primarily a contract-interface and internal-behavior update rather than a user-facing release. Downstream systems should check for calls to removed functions, refresh ABIs and confirm that indexing or automation does not rely on fields that are now deprecated.

Trust 90 Importance 66 Noise 0% Related symbol Informational material, not financial advice.