Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

evm-contact-map.json doesn't allow for the same contract address on multiple networks #84

Open
nvonpentz opened this issue Aug 31, 2023 · 0 comments · May be fixed by #86
Open

evm-contact-map.json doesn't allow for the same contract address on multiple networks #84

nvonpentz opened this issue Aug 31, 2023 · 0 comments · May be fixed by #86
Assignees

Comments

@nvonpentz
Copy link
Member

I noticed that the keys in evm-contract-map.json are contract addresses, with the chain ID being part of the value, e.g.

{
  "0xc2132D05D31c914a87C6611C10748AEb04B58e8F": {
    "name": "Tether USD (PoS)",
    "logo": "usdt.png",
    "erc20": true,
    "symbol": "USDT",
    "decimals": 6,
    "coingeckoId": "tether",
    "chainId": "0x89"
  },
...
}

So I don't think it's possible to use the same contract address across multiple networks.

@nvonpentz nvonpentz self-assigned this Aug 31, 2023
@nvonpentz nvonpentz linked a pull request Sep 8, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant