bootnode

Run Teku in bootnode-only mode.

network

Syntax

teku bootnode --network=<NETWORK>

Example

teku bootnode --network=mainnet

Environment variable

TEKU_NETWORK=mainnet

Configuration file

network: "mainnet"

Predefined network configuration. The default is mainnet.

Possible values are:

Network	Chain	Type	Description
mainnet	Consensus layer	Production	Main network
holesky	Consensus layer	Test	Multi-client testnet
hoodi	Consensus layer	Test	Multi-client testnet
ephemery	Consensus layer	Test	Multi-client testnet
sepolia	Consensus layer	Test	Multi-client testnet
minimal	Consensus layer	Test	Used for local testing and development networks
gnosis	Consensus layer	Production	Network for the Gnosis chain
chiado	Consensus layer	Test	Gnosis testnet
lukso	Consensus layer	Production	Network for the Lukso chain

p2p-port

Syntax

teku bootnode --p2p-port=<PORT>[,<PORT>...]...

Example

teku bootnode --p2p-port=9000

Environment variable

TEKU_P2P_PORT=9000

Configuration file

p2p-port: 9000

The P2P listening ports (UDP and TCP). The default is 9000.

p2p-advertised-ip

Syntax

teku bootnode --p2p-advertised-ip=<IP_ADDRESS>

Example

teku bootnode --p2p-advertised-ip=192.168.1.132

Environment variable

TEKU_P2P_ADVERTISED_IP=192.168.1.132

Configuration file

p2p-advertised-ip: "192.168.1.132"

The peer-to-peer IP address(es) to advertise. The default address is 127.0.0.1.

p2p-private-key-file

Syntax

teku bootnode --p2p-private-key-file=<PATH_TO_FILE>

Example

teku bootnode --p2p-private-key-file=/home/me/me_node/key

Environment variable

TEKU_P2P_PRIVATE_KEY_FILE=/home/me/me_node/key

Configuration file

p2p-private-key-file: "/home/me/me_node/key"

The file containing the node's private key.

If a file doesn't exist at the specified path, Teku creates a new file and P2P private key to store inside.

important

Ensure you specify the complete file path, including the file name, and not only the directory location.

config-file

Syntax

teku bootnode --config-file=<FILE>

Example

teku bootnode --config-file=/home/me/me_node/config.yaml

Environment variable

TEKU_CONFIG_FILE=/home/me/me_node/config.yaml

Path to the YAML configuration file. The default is none.

data-base-path, data-path

Syntax

teku bootnode --data-base-path=<PATH>

Example

teku bootnode --data-base-path=/home/me/me_node

Environment variable

TEKU_DATA_BASE_PATH=/home/me/me_node

Configuration file

data-base-path: "/home/me/me_node"

Path to the Teku base directory for storage. The default directory is OS-dependent:

• macOS: ~/Library/teku
• Unix/Linux: $XDG_DATA_HOME/teku if $XDG_DATA_HOME is set; otherwise ~/.local/share/teku
• Windows: %localappdata%\teku.

The default Docker image location is /root/.local/share/teku.

log-color-enabled

Syntax

teku bootnode --log-color-enabled[=<BOOLEAN>]

Example

teku bootnode --log-color-enabled=false

Environment variable

TEKU_LOG_COLOR_ENABLED=false

Configuration file

log-color-enabled: false

Specify whether status and event log messages include a console color display code. The default is true.

log-destination

Syntax

teku bootnode --log-destination=<LOG_DESTINATION>

Example

teku bootnode --log-destination=CONSOLE

Environment variable

TEKU_LOG_DESTINATION=CONSOLE

Configuration file

log-destination: "CONSOLE"

Specify where to output log information. Valid options are:

• BOTH
• CONSOLE
• DEFAULT_BOTH
• FILE

The default is DEFAULT_BOTH. When using BOTH or DEFAULT_BOTH, system updates such as blockchain events are displayed on the console, and errors and other information are logged to a file. Specify the log file with the --log-file command-line option.

For production systems we recommend using the CONSOLE or FILE options to ensure all log information is available in one place.

note

Use DEFAULT_BOTH when using a custom Log4J2 configuration file. Any other option applies the custom logging changes on top of its default settings.