As an update to the community, some users detected a problem with repayments of MAI on Aave v3 Arbitrum and Optimism.
The issue is caused by the lack of full compatibility on the connection Pool -> aToken in the specific case of MAI, as it was listed just after the 3.0.2 upgrade without using a custom implementation, defaulting to 3.0.0.
The 3.0.2 Pool on Optimism/Arbitrum expects a > 3.0.1 version on the aToken of all assets, and even if all non-MAI were upgraded to 3.0.2, the listing of MAI happening just after still uses a 3.0.0 aToken, and so creating an unexpected revert().
This doesn’t really create a meaningful risk to the Arbitrum and Optimism instances for the following reasons:
- The MAI reserve on those networks is relatively small in terms of users and amounts, with ~100 MAI on Optimism and ~8’000 MAI on Arbitrum supplied.
- The problem is completely isolated to MAI, not affecting any other asset directly.
- MAI is an isolated collateral, with no meaningful debt borrowed against.
Repayment could still work by using the Aave v3 repayment with aTokens feature, but given that liquidations of MAI debt can’t be executed, we have coordinated with the Aave Guardian a targeted pause of the MAI reserve, to reduce the growth of the size of the reserve.
This means all actions on MAI are not allowed, but users can still do all other actions with the rest of the assets, supplying them, refilling collateral, borrowing, and liquidations (not involving MAI), etc.
We will be submitting a governance proposal with a fix in the following hours.