Aave is considering a technical update to its stkGhoMigrator setup, with Aave Labs proposing that the current contract be replaced by a new version designed to make migrations more resilient.
According to the governance post, the change is framed as a maintenance and security-focused upgrade rather than a user-facing product change. Aave Labs said the replacement would not alter user funds, affect the underlying contracts the migrator interacts with, or change the contract interface and function signatures.
What the proposal changes
The proposal calls for three onchain actions. First, permissions currently assigned to the existing stkGhoMigrator contract would be revoked. Second, those same permissions would be granted to the new stkGhoMigrator contract. Third, the current contract would be paused.
Aave Labs identified the existing migrator at 0xC836143e39201698e7d543bCf21AfF3415aE4697 and the updated migrator at 0x4C728397b9d5C8071d46229DF8823Ea2782124fb. The change is presented as a straight contract replacement rather than a redesign of how the migration process works.
Why Aave Labs says the swap is needed
In the proposal, Aave Labs said it developed the new contract to improve the resilience of migrations. It described the update as part of its ongoing work around the security of the Aave Protocol and the broader ecosystem.
The post does not describe changes to external behavior for end users. Instead, it emphasizes that the new implementation is an enhancement of the existing stkGhoMigrator, with no modifications to the public interface or to the function signatures exposed by the contract.
Expected impact on users and integrators
Aave Labs said the replacement should not have a direct impact on users or user funds. The underlying contracts that the migrator interacts with are also not expected to change under the proposal.
After execution, however, front ends, interfaces, and other tools are expected to send migration activity through the new contract rather than the old one. Aave Labs said it plans to coordinate with third-party integrators to support the transition to the updated address.
Next step in the governance process
The proposal was published on Aave's governance forum as a technical maintenance item. If carried forward and executed, the old stkGhoMigrator would remain paused while the new contract assumes the same permissions previously held by the original deployment.
Aave Labs said it is presenting the update in its capacity as a service provider to the Aave DAO and within its approved scope of work for DAO operations. The next confirmed step from the proposal itself is the migration of integrations and interfaces to the new contract if the replacement is approved and implemented.
Source: governance.aave.com