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

Suggestion of list of known Ethereum network ids #110

Closed
fjrojasgarcia opened this issue Jan 21, 2018 · 6 comments
Closed

Suggestion of list of known Ethereum network ids #110

fjrojasgarcia opened this issue Jan 21, 2018 · 6 comments
Assignees

Comments

@fjrojasgarcia
Copy link
Contributor

@fjrojasgarcia fjrojasgarcia commented Jan 21, 2018

In order to offer to new programmers information grouped of currenty used Ethereum networks ids, I suggest the following list. Please add your corrections.

0: Olympic; Ethereum public pre-release testnet
1: Frontier; Homestead, Metropolis, the Ethereum public main network
1: Classic; The (un)forked public Ethereum Classic main network, chain ID 61
1: Expanse; An alternative Ethereum implementation, chain ID 2
2: Morden; The public Ethereum testnet, now Ethereum Classic testnet
3: Ropsten; The public cross-client Ethereum testnet
4: Rinkeby: The public Geth Ethereum testnet
42: Kovan; The public Parity Ethereum testnet
77: Sokol; The public POA testnet
99: POA; The public Proof of Authority Ethereum network
7762959: Musicoin; The music blockchain

@aantonop
Copy link
Member

@aantonop aantonop commented Jan 21, 2018

I agree this is useful

Where is the "network ID"? In the API? In a network message header?

Where would you add this information in the current sections?

@wbnns wbnns assigned wbnns and aantonop and unassigned wbnns Jan 24, 2018
@ChristopherGondek
Copy link
Contributor

@ChristopherGondek ChristopherGondek commented Jan 24, 2018

I suggest mentioning that Ropsten is PoW, Rinkeby and Kovan are PoA.
The network ID you have to specify when starting a node. E.g. option --networkid for Geth.

@fjrojasgarcia
Copy link
Contributor Author

@fjrojasgarcia fjrojasgarcia commented Jan 24, 2018

I think Andreas is refering at a protocol level.
There is a especial message called "Status" which send that data (network ID) between others.

I'm working deeper in this point and I hope to offer something more accurate and explanatory, surely in the form of PR.

@nicksavers
Copy link

@nicksavers nicksavers commented Jan 24, 2018

The networkId is communicated during the initial Status-message in the ETH Wire protocol.

Also see EIP-155.

@aantonop
Copy link
Member

@aantonop aantonop commented Feb 1, 2018

Incorporated into the DevP2P section

@aantonop aantonop closed this Feb 1, 2018
@H34D
Copy link

@H34D H34D commented Sep 12, 2019

i have started a structured list incl. access layer to support auto detection:

https://github.com/ethereum-navigator/atlas/blob/master/atlas.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants