search

ethereum-lists / chains

provides metadata for chains
https://chainid.network
MIT License
8.43k stars 6.06k forks source link

Add mainnet boolean #2351

Closed kopeboy closed 1 year ago

kopeboy commented 1 year ago

Can't find a way to distinguish mainnets from testnets, which is VERY usefull.

ligi commented 1 year ago

what's the use-case? Usually a good indicator is if there is a faucet

kopeboy commented 1 year ago

The usecase is not showing testnets in any user facing app that fetches networks from this list. I can filter on "test" or "dev" in the name field but it's not well defined and prone to errors. Faucet field is not good either, you can have mainnets with faucets and testnets without it. I think adding a specific field that distinguishes the items in the list is usefull for the purpose of this repo.

kopeboy commented 1 year ago

Where can we see what's planned and is planning a collaborative effort? 🤔

ligi commented 1 year ago

this is what is planned: https://github.com/ethereum-lists/chains/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement

planning is a semi-collaborate effort - things can be suggested - but only core contributors decide

I think this is not worth doing - even though it would be easy. What is even a testnet - how do you define it? Why would you want to filter testnets?

kopeboy commented 1 year ago

I already said: for real users (not developers) is very important to distinguish a network with real economic value from a testnet. I'm developing a sort of decentralized multi-chain index fund so I don't want to track balances, prices and KPIs of test or dev environments. Check the new Glacier (Ethereum & Avalanche) API endpoint https://glacier-api.avax.network/v1/chains They have the "isTestnet" boolean.

ligi commented 1 year ago

I still do not think this is a good idea to have a isTestNet or isMainNet option. What I could imagine to add:

{ "priceTracker": { "name": "", "standards: [], "address" } }

If something is a testnet is just simply not a boolean value.