CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
844 Commits
44 Branches
214 Tags
188 MiB
 
 
Tag: Branch: Tree: b5b4f4e85e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b5b4f4e85e'
${ noResults }
besu/docs/Configuring-Pantheon/NetworkID-And-ChainID.md

1.2 KiB
Raw Blame History

description: Pantheon network ID and chain ID implementation

Network ID and Chain ID

Ethereum networks have a network ID and a chain ID. The network ID defaults to the chain ID specified in the genesis file.

!!! example "Chain ID in Genesis File" json { "config": { "ethash": { }, "chainID": 1981 }, ... }

For most networks including MainNet and the public testnets, the network ID and the chain ID are the same and are specified in the genesis file.

The network ID and chain ID are automatically defined by Pantheon when connecting to networks specified using the --network option:

  • MainNet: chain-id 1, network-id 1
  • Rinkeby: chain-id 4, network-id 4
  • Ropsten: chain-id 3, network-id 3
  • Dev: chain-id 2018, network-id 2018

When using the --network=dev or --genesis-file options, you can override the network ID using the --network-id option.