The Metamask client allows access to three test networks:
- Ropsten
- Kovan
- Rinkeby
I'm curious:
- What are the similarities / differences between them?
- Which use cases are best for each network
- Are there more than these listed above?
-
Ropsten To Kovan To Rinkeby: Ethereum’s Testnet Troubles – Tom Hale Sep 29 '17 at 11:06
-
EIP-225 has the story of Modern up to Rinkeby – 0xcaff Jul 9 at 6:07
- PoW
- Supported by geth and parity
- Best reproduces the current production environment
- Chaindata size 15 GB - Apr 2018
- PoA (Immune to spam attacks)
- Supported by parity only
- Chaindata size 13 GB - Apr 2018
- PoA (Immune to spam attacks)
- Supported by geth only
- Chaindata size 6 GB - Apr 2018
- PoA (Immune to spam attacks)
- Supported by parity only
- Chaindata size 5gb - Jun 2018
If you need support on both geth and parity go wtih Ropsten. Otherwise choose Kovan, Sokol or Rinkeby as they are more stable.
Detailed version below:
Ropsten
- PoW testnet
- History:
- Started in November 2016. Named after a subway station in Stockholm.
- Was DoS attacked in February 2017 which made synching slow and made clients consume a lot of disk space.
- Was revived in March 2017 and became usable again.
- Pros:
- Best reproduces the current production environment, i.e. system and network conditions on the live Ethereum mainnet, because it's PoW net.
- Can be used with both geth and parity.
- Ether can be mined. Or requested from a faucet:
- Cons:
- Not immune to spam attacks. Because of this it's less stable.
- Network id:
3 - Block time:
sub-30 seconds - Commands:
geth --testnetorgeth --networkid 3parity --chain ropsten
- Explorer https://ropsten.etherscan.io/
- Github https://github.com/ethereum/ropsten
Kovan
- PoA testnet started by the Parity team
- History:
- Started in March 2017. Named after a subway station in Singapore.
- Pros:
- Immune to spam attacks (as Ether supply is controlled by trusted parties)
- Cons:
- Not supported in geth.
- Doesn't fully reproduce the current production environment as it uses PoA.
- Ether can't be mined. It has to be requested from the faucet.
- Network id:
42 - Block time:
4 seconds - Command:
parity --chain kovan - Explorer https://kovan.etherscan.io/
- Github https://github.com/kovan-testnet/proposal
Rinkeby
- PoA testnet started by the Ethereum team. Uses Clique PoA consensus protocol.
- History:
- Started in April 2017. Named after a metro station in Stockholm.
- Pros:
- Immune to spam attacks (as Ether supply is controlled by trusted parties)
- Cons:
- Supported by geth only
- Doesn't fully reproduce the current production environment as it uses PoA.
- Ether can't be mined. It has to be requested from a faucet:
- Network id:
4 - Block time:
15 seconds - Command:
geth --rinkebyorgeth --networkid 4 - Explorer https://rinkeby.etherscan.io/
- Github https://github.com/ethereum/EIPs/issues/225
- Website https://www.rinkeby.io
Sokol
- PoA testnet started by the POA.network team
- History:
- Started in December 2017. Named after a subway station in Moscow.
- Pros:
- Immune to spam attacks (as Ether supply is controlled by trusted parties)
- Cons:
- Not supported in geth.
- Doesn't fully reproduce the current production environment as it uses PoA.
- Ether can't be mined. It has to be requested from the faucet.
- Network id:
77 - Block time:
5 seconds - Explorer https://sokol-explorer.poa.network/
- Public faucet: https://faucet-sokol.herokuapp.com/
- RPC endpoint: https://sokol.poa.network
- Wiki: https://github.com/poanetwork/wiki/wiki/POA-Network-Resources
- Github https://github.com/poanetwork/poa-chain-spec/tree/sokol
Görli
- Clique PoA testnet started by the Parity team
- History:
- Started in November 2018 after a proposal by Afri. It's a testnet that has the goal of being both widely usable across all client implementations supporting Clique PoA engine (EIP-225), and robust enough to guarantee consistent availability and high reliability.
- Pros:
- Supported by multiple clients (including Geth, Pantheon, Nethermind and soon Parity as work is in progress)
- Cons:
- It's still fresh and unstable.
- Not all clients support it for the moment.
- Chain id:
6284 - Network id:
6284 - Block time:
15 seconds on average - Status Dashboard: https://stats.goerli.net/ or http://ethstats.goerli.ethberl.in:3000/
- Explorer https://blockscout.com/eth/goerli/ or https://explorer.goerli.net/
- Github https://github.com/goerli/testnet
answered Nov 7 '17 at 10:23
-
3Great answer. Could you also tell us about the approximate size (in gigs) of each as of today ,please? It s v. important for people with a small hd :). – hartmut Dec 17 '17 at 21:53
-
-
-
@NicolasMassart feel free to edit the answer or send me what you want to add. – medvedev1088 Nov 28 '18 at 8:21
-
1@medvedev1088 done. Note the distinct informations for chain id and network id even if values are similar, this is mostly for educational purpose as we'll have to explain why we have those two values one day and that they ca be different... – Nicolas Massart Nov 29 '18 at 10:53
There are other networks as well, as described in this SO answer, copied here with their network id numbers:
0: Olympic, Ethereum public pre-release testnet1: Frontier, Homestead, Metropolis, the Ethereum public main network1: Classic, the (un)forked public Ethereum Classic main network, chain ID611: Expanse, an alternative Ethereum implementation, chain ID22: Morden, the public Ethereum testnet, now Ethereum Classic testnet3: Ropsten, the public cross-client Ethereum testnet4: Rinkeby, the public Geth Ethereum testnet42: Kovan, the public Parity Ethereum testnet77: Sokol, the public POA testnet99: POA, the public Proof of Authority Ethereum network7762959: Musicoin, the music blockchain
