Aave
Arquitectura del Protocolo
Context
This figure opens Section 2 'Protocol Architecture' and provides a structural overview of the smart contract system that implements the Aave Protocol. It shows how the main contracts — LendingPoolCore, LendingPoolDataProvider, LendingPool, LendingPoolConfigurator, and InterestRateStrategy — relate to each other. The diagram also indicates proxy contracts and admin interfaces used for governance and upgradeability.
What This Figure Shows
The Protocol Architecture figure reveals a layered contract design: LendingPoolCore sits at the center, holding all reserve state and asset balances while executing low-level index and rate calculations. LendingPoolDataProvider sits above it as an aggregation and computation layer, translating raw reserve state into higher-level metrics like health factor and weighted-average LTV. LendingPool is the user-facing entry point that orchestrates all actions (deposit, redeem, borrow, repay, swap rate, liquidation, flash loan) by calling into both Core and DataProvider. LendingPoolConfigurator provides privileged configuration functions for initializing and tuning reserves, and will eventually be controlled by on-chain governance. Each reserve has its own InterestRateStrategy contract that encodes the specific slope parameters for that asset.
Significance
The layered architecture separates concerns cleanly: state management, computation, user interaction, configuration, and rate strategy each live in distinct contracts. This separation enables upgradeability — the Configurator and governance layer can update strategy contracts without touching the Core — and limits the blast radius of bugs in any one component. The architecture diagram is essential for developers integrating with or auditing the protocol, and it explains why the whitepaper dedicates separate subsections to each contract component.
