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.



Provides blocks related actions.


pantheon blocks import --from=<block-file>
pantheon blocks import --from=/home/me/me_project/mainnet.blocks

Imports blocks from the specified file into the blockchain database


This command provides node public key related actions.


pantheon public-key export [--to=<key-file>]
pantheon --data-path=<node data path> public-key export
pantheon --data-path=<node data path> public-key export --to=/home/me/me_project/not_precious_pub_key

Outputs the node public key to standard output or writes it to the specified file if --to=<key-file> is specified.


pantheon public-key export-address [--to=<address-file>]
pantheon --data-path=<node data path> public-key export-address
pantheon --data-path=<node data path> public-key export-address --to=/home/me/me_project/me_node_address

Outputs the node public key address to standard output or writes it to the specified file if
--to=<key-file> is specified.


Provides password related actions.


This command generates the hash of a given password. Include the hash in the credentials file for JSON-RPC API authentication.

pantheon password hash --password=<my-password>
pantheon password hash --password=myPassword123


Provides operator actions.


This command generates IBFT 2.0 configuration files.

pantheon operator generate-blockchain-config --config-file=<FILE> --to=<DIRECTORY> [--genesis-file-name=<FILE>] [--private-key-file-name=<FILE>] [--public-key-file-name=<FILE>]
pantheon operator generate-blockchain-config --config-file=config.json --to=myNetworkFiles

The configuration file has 2 subnested JSON nodes. The first is the genesis property defining the IBFT 2.0 genesis file except for the extraData string. The second is the blockchain property defining the number of key pairs to generate.


Provides RLP related actions.


This command encodes a typed JSON value from a file or from the standard input into an RLP hexadecimal string.

pantheon rlp encode [--from=<FILE>] [--to=<FILE>] [--type=<type>]
pantheon rlp encode --from=ibft_extra_data.json --to=extra_data_for_ibft_genesis.txt --type=IBFT_EXTRA_DATA
cat extra_data.json | pantheon rlp encode > rlp.txt

The IBFT_EXTRA_DATA type is the only type supported for RLP encoding. This data is included in the IBFT 2.0 genesis file.

IBFT 2.0 Extra Data

To generate the RLP encoded extraData string, specify a JSON input that is array of validator addresses in ascending order.


The following JSON Schema can be used to validate that your JSON data is well formed. You can use an online validation tool such as to validate your JSON content.

  "$schema": "",
  "$id": "http://tech.pegasys.pantheon/cli_rlp_ibft_extra_data.json",
  "type": "array",
  "definitions": {},
  "title": "IBFT extra data",
  "description":"JSON format used as input to generate an IBFT extra data RLP string",
  "items": {
    "$id": "#/address",
    "type": "string",
    "title": "Validator address",
    "description":"The validator node address",
    "default": "",
    "examples": [

Example IBFT_EXTRA_DATA encoding

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]