[Direct-to-AIP] stkGHO->sGHO Migration Tool

Summary

We present to the community the stkGHO β†’ GHO migration tool, a helper contract that facilitates migrations of user deposits from the deprecated stkGHO contract into the new 4626-compliant sGHO vault. The flow will be accessible in the Aave UI, supporting the stkGHO deprecation strategy outlined by TokenLogic.

Motivation

Migrating manually requires several steps: triggering the stkGHO cooldown, redeeming GHO, approving GHO, and depositing into sGHO. The helper bundles this into one flow, exiting stkGHO and depositing into sGHO on the user’s behalf.

Specification

To exit stkGHO on behalf of users, the contract requires the CLAIM_HELPER role on stkGHO. Upon execution, the proposal grants the CLAIM_HELPER role to the migrator (0xC836143e39201698e7d543bCf21AfF3415aE4697) on stkGHO (0x1a88Df1cFe15Af22B3c4c783D4e6F7F9e0C1885d).

The migration flow will be made available through the Aave UI.

Disclaimer

This proposal was prepared by Aave Labs in its capacity as a contributor to the Aave ecosystem.

Next Steps

  1. Publish an AIP vote for final confirmation and on-chain enforcement of the proposal.

Copyright

Copyright and related rights waived via CC0.

8 Likes

I support this proposal as a practical improvement for the stkGHO migration process. Providing a dedicated helper contract reduces the number of manual steps required, making the transition to the new sGHO vault more accessible while minimizing the risk of user errors.

I also appreciate that the proposal grants only the specific role required to execute the migration flow, following the principle of least privilege rather than introducing broader permissions.

Smooth migration tools are an important part of protocol upgrades, especially when replacing deprecated components. As always, clear communication and transparency throughout the migration process will help ensure user confidence and successful adoption.