DeFi
Aave V3.8 brings market-by-market compatibility checks back into focus
In a November 20 note, Zealynx describes the scope of the lock added in Aave V3.8. Teams connecting a vault or router to the protocol still need to verify each market’s version and the assumptions in their own software.

Aave’s lock protects Pool operations
Aave V3.8 went live on November 11 on Ethereum Core, the protocol’s principal Ethereum market, according to the timeline documented by Zealynx. On November 20, the team posted an analysis for integrators on the governance forum. It separates two questions that arise during a migration. The first is which operations are protected by the Pool, the contract that manages loans and deposits. The second is what guarantees external software needs when it uses data from that contract.
In its October proposal, Aave Labs described the reentrancy lock as a measure to preserve the Pool’s accounting consistency. It addresses nested operations, when one action attempts to start another while the Pool is still processing the first. Common operations that change the Pool’s state, including deposits, withdrawals, and repayments, were within the scope examined by Zealynx. Teams maintaining an integration need to check that the operations their product is designed to perform are compatible with the rules of the deployed version.
Sixteen active markets were found running revision 12
The rollout targeted active markets named in the governance proposal. Instances where all assets were frozen and caps were being reduced to zero were outside its scope. In its November 20 review, Zealynx reported finding revision 12 on all sixteen targeted instances. These include Ethereum Core and Ethereum Lido, as well as markets on Base, Arbitrum, and Polygon. The review also reported earlier revisions on several other instances, including Scroll, Sonic, and Horizon.
The difference matters for applications that connect to several markets through a single adapter. Tests passed on Ethereum Core only cover part of what those applications support. To establish the product’s coverage, teams can inventory the markets they connect to, record each revision, and define compatibility checks for each combination. This also provides a reference for future upgrades, when market versions will change at different times.
Vaults and routers still need their own checks
The purpose of the Pool lock is to protect Pool operations. A vault, which manages funds under the rules of its strategy, or a router, which decides how to route an operation, applies rules of its own. If the software uses a liquidity reading to display an amount or make a decision, the team needs to define when that reading is reliable for the purpose and how the product responds if the data changes before execution.
The Zealynx review therefore draws attention to the decisions the integration itself makes. Before deployment, a team can separate market-specific compatibility checks from tests of its own decision logic, using simulated data for the latter. That work helps document which operations the product accepts and what users see when execution conditions change.
