Skip to content
You are reading Pantheon development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.


Bootnodes are used to initially discover peers.

Mainnet and Public Testnets

For mainnet, Rinkeby, Ropsten, and Görli, Pantheon predefines a list of enode URLs.

Private Networks

Start Bootnode

To start a bootnode for a private network, complete the following steps:

  1. Export the public key to a file:


    pantheon --genesis-file=privateNetworkGenesis.json --data-path=nodeDataPath public-key export --to=bootnode
    Where privateNetworkGenesis.json and nodeDataPath are changed to the relevant values for your private network.

    The node public key is exported to the bootnode file.

  2. Start the bootnode, specifying:

    • Genesis file and data directory, as in the previous step.
    • No arguments for the --bootnodes option because this is your bootnode.


    pantheon --genesis-file=privateNetworkGenesis.json --data-path=nodeDataPath --bootnodes

To specify this bootnode for another node, specify the enode URL using the --bootnodes option.


The default host and port for P2P peer discovery is Use the --p2p-host and --p2p-port option to specify a host and port.

Start Node Specifying the Bootnode

To start a node specifying the bootnode for P2P discovery:


pantheon --genesis-file=privateNetworkGenesis.json --data-path=nodeDataPath --p2p-host= --p2p-port=30301 --network-id=123 --bootnodes=enode://c35c3ec90a8a51fd5703594c6303382f3ae6b2ecb99bab2c04b3794f2bc3fc2[email protected]


Questions or feedback? You can discuss issues and obtain free support on Pantheon Gitter channel.
For paid professional support by PegaSys, contact us at [email protected]