cGHS Name Update

cGHS Name Update

This proposal will update the name of the cGHS token. More information can be found in this forum post

Status

• DRAFT

Proposed Changes

1. Set implementation of cGHS to TempStable

   • Contract: StableTokenGHSProxy
   • Address: 0xfAeA5F3404bbA20D3cc2f8C4B0A888F55a3c7313
   • Function: _setImplementation
   • Data: 0x8F7F590A0DD9D978065B9021006a242a4Dc56e1e
   • Value: 0

2. Set the new name

   • Contract: StableTokenGHSProxy
   • Address: 0xfAeA5F3404bbA20D3cc2f8C4B0A888F55a3c7313
   • Function: setName
   • Data: Celo Ghanaian Cedi
   • Value: 0

3. Set the implementation of cGHS to StableTokenV2

   • Contract: StableTokenGHSProxy
   • Address: 0xfAeA5F3404bbA20D3cc2f8C4B0A888F55a3c7313
   • Function: _setImplementation
   • Data: 0x434563B0604BE100F04B7Ae485BcafE3c9D8850E
   • Value: 0

Verification

For each transaction, the following can be used to help with verification:

TX#0 - Set implementation to TempStable

• Verify the StableTokenGHSProxy address. The correct address can be found here
• Verify the TempStable address. The correct address can be found here

TX#1 - Call setName function

• Verify the StableTokenGHSProxy address. The correct address can be found here

TX#2 - Set implementation to StableTokenV2

• Verify the StableTokenGHSProxy address. The correct address can be found here
• Verify the StableTokenV2 address. The correct address can be found here. This should be the same as the implementation used for all other Mento stables.

Risks

The proposal has three transactions, with the final one reverting the implementation back to the original StableTokenV2. The testing and simulation show that the execution risks are minimal.

• Executed by: 0xj4an-work