The pool-wide reentrancy lock is live. Fifteen chains, and zero votes against in the governance vote.
Version V3.8 for $AAVE was deployed early this morning. There’s only one core change: the reentrancy lock has been moved from individual markets to the entire liquidity pool. Previously, each asset had its own guard. An attacker could route to another asset within the same transaction, then call back in—the guards were separate, but the path between them was open. Now the lock is at the pool level, so cross-asset calls have to queue behind the same lock.
The zero votes against are worth noting, too. When lending protocols change their security boundaries, there’s usually debate over whether legitimate liquidation paths might be affected. There was no disagreement this time.
The gates in the code were never meant for those who play by the rules.
#AAVE #DeFi #Security
Version V3.8 for $AAVE was deployed early this morning. There’s only one core change: the reentrancy lock has been moved from individual markets to the entire liquidity pool. Previously, each asset had its own guard. An attacker could route to another asset within the same transaction, then call back in—the guards were separate, but the path between them was open. Now the lock is at the pool level, so cross-asset calls have to queue behind the same lock.
The zero votes against are worth noting, too. When lending protocols change their security boundaries, there’s usually debate over whether legitimate liquidation paths might be affected. There was no disagreement this time.
The gates in the code were never meant for those who play by the rules.
#AAVE #DeFi #Security
