The discussion primarily revolved around the migration from AAVE 2 to AAVE 3. RedDragon initiated the conversation, expressing concerns about the potential for coding errors and loss of funds during an automatic migration¹. However, EzR3aL clarified that there would be no automatic migration. Instead, users would need to decide to switch themselves. To assist in this process, a tool provided by Bgdlabs is available².

Further into the discussion, RedDragon sought confirmation on whether users needed to resolve their lending and borrowing on AAVE 2 before using the tool to transfer to AAVE 3³. Sakulstra explained that the migration tool could only be used for assets listed on both versions of AAVE⁴. This led RedDragon to understand that for assets listed on both AAVE 2 and AAVE 3, users could use the tool to transfer without having to resolve all the lending and borrowing on AAVE 2⁵.

The discussion concluded with EzR3aL advising users to start the tool and read the instructions for all necessary information⁶. Finally, MarcZeller closed the topic, directing RedDragon to the Aave Discord for further support⁸. This discussion provided valuable insights into the migration process from AAVE 2 to AAVE 3, highlighting the importance of user discretion and the availability of tools to facilitate the process.