7 replies, 1461 views, 2 likes
The discussion focused on the migration from AAVE 2 to AAVE 3, clarifying that there's no automatic migration and users must decide to switch themselves, using a tool provided by Bgdlabs. The tool can only be used for assets listed on both AAVE versions, allowing users to transfer without resolving all lending and borrowing on AAVE 2.
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 migration1. 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 available2.
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 33. Sakulstra explained that the migration tool could only be used for assets listed on both versions of AAVE4. 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 25.
The discussion concluded with EzR3aL advising users to start the tool and read the instructions for all necessary information6. Finally, MarcZeller closed the topic, directing RedDragon to the Aave Discord for further support8. 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.
Posted 10 months ago
Last reply 10 months ago
Summary updated 2 months ago
Last updated 08/12 04:39