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

support for testnets / other chains ? #194

Open
sulliwane opened this issue Nov 14, 2018 · 3 comments
Open

support for testnets / other chains ? #194

sulliwane opened this issue Nov 14, 2018 · 3 comments

Comments

@sulliwane
Copy link
Contributor

RLC token has "official" ERC20 deployed on Kovan/Rinkeby/Ropsten, is it possible to add them to Metamask (to make the "add token" working for testnet as well) ?

I can see the RLC ERC20 Mainnet contract address in this file: https://github.com/MetaMask/eth-contract-metadata/blob/master/contract-map.json, is it possible to add address for other chains ?

Many thanks

@sulliwane sulliwane changed the title support for testnets ? support for testnets / other chains ? Nov 14, 2018
@1blockologist
Copy link
Contributor

1blockologist commented Dec 21, 2018

I like this idea, maybe we can just have other branches here that just have the contract-map.json in the .gitignore file

a ropsten branch for example, with its own contract-map.json

metamask upgrades would have to contain all the maps though

@waterdrop01
Copy link

waterdrop01 commented Feb 22, 2019

Here is how MyEtherWallet supports multiple chains (one chain is one folder) => https://github.com/MyEtherWallet/ethereum-lists/tree/master/src/tokens

Would be super useful to have something similar for Metamask.

Or even best, if all wallet teams could agree on one common repo...

@1blockologist
Copy link
Contributor

1blockologist commented Feb 22, 2019

A common repo should probably use the networkID designation

As that is a ratified improvement protocol

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

No branches or pull requests

3 participants