Aave V2, V3, and V4 share a name, but not the same architecture, field structure, rate model, or risk logic.
For integrators, they are effectively three separate protocols.
Here is how 1delta maps all three into one unified data model so they can be queried identically across
@Aave deployments.