search

cosmos / cosmos-sdk

:chains: A Framework for Building High Value Public Blockchains :sparkles:
https://cosmos.network/
Apache License 2.0
6.26k stars 3.62k forks source link

Chain ID && token ticker/symbol change due to conflict with another chain #20456

Closed ahmadSaeedGoda closed 4 weeks ago

ahmadSaeedGoda commented 5 months ago

Summary

Kindly point out to some place where I can find instruction for a chain id and token ticker/symbol change, or else add to docs.

Thanks in advance!

Respectfully,

ahmadSaeedGoda commented 5 months ago

Please consider it a live mainnet, what steps/tutorials/instructions can be followed to achieve this?

I have a network up & running whose ID is conflicting with another live network which causes issues with wallets like MetaMask e.g, and also affects Token symbol/denom being suspicious due to duplicate chain id, which affects the deployed dApps in turn.

Please advise!

Thanks,

tac0turtle commented 5 months ago

you will need to perform a chain upgrade in which you modify the chainID either through genesis export or within the migration handler.

For your token, the question is are there tokens already on other chains through IBC?

ahmadSaeedGoda commented 5 months ago

@tac0turtle Thanks for your reply, yeah conducted a chain software upgrade over a local network consists of 4 nodes with equal validator voting power each.. then when halted at the specified height modified the chainID through genesis for all of them but the error I get is: panic: signature verification failed; please verify account number (0) and chain-id (app_123-2): unauthorized where this is the new id. As it seems the old genesis chain-id is tied to the account signature, now since one parameter changed (which is the chain-id) the hash is different and hence it panics.

Kindly advise! :100:

Regarding the tokens, there is no token out there on other chains through IBC. :pray:

Best Regards,

julienrbrt commented 4 weeks ago

Hi, please verify when submitting a transaction that you pass the correct chain-id (--chain-id or the client.toml config). Closing this, if you still encounter this feel free to re-open.