You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we had to migrate the AgaTech (AGATA) token to a new contract address. All other aspects and information about the project stay the same, we just have a new CA for the token, can we have that updated?
#29466
Hi, we had to migrate the AgaTech (AGATA) token, on BSC, to a new contract address. All other aspects and information about the project stay the same, we just have a new CA for the token, can we have that updated?
Old token contract address: 0xb427e47e8fDD678278d2A91EEaC014ffcDDaF029
New token contract address: 0x18c4AF61DbE6fD55d6470943b4ab8530777d009C
Hi, we had to migrate the AgaTech (AGATA) token, on BSC, to a new contract address. All other aspects and information about the project stay the same, we just have a new CA for the token, can we have that updated?
Old token contract address: 0xb427e47e8fDD678278d2A91EEaC014ffcDDaF029 New token contract address: 0x18c4AF61DbE6fD55d6470943b4ab8530777d009C
Old token contract address: 0xb427e47e8fDD678278d2A91EEaC014ffcDDaF029
New token contract address: 0x18c4AF61DbE6fD55d6470943b4ab8530777d009C
Originally posted by @TheNotoriousMonsi in #28040 (comment)
The text was updated successfully, but these errors were encountered: