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

Updated on April 8, 2022

Start Teku

You can run Teku as a beacon node and validator in a single process, or as separate processes.

We recommend you run the beacon node and validator as a single process if they are to run on the same machine.


By default, Teku connects to mainnet. Use the --network command line option to specify an alternate network.

If the genesis state of a network is not yet known, then include the --eth1-endpoint command line option.


Start the clients in a single process

Start the beacon node and validator as a single process by specifying the validator options with the teku command. For example:


teku --network=prater --eth1-endpoints=http://localhost:8545,http://backup-host:8545/ \
--validator-keys=validator/keys/validator_888eef.json:validator/passwords/validator_888eef.txt \
--rest-api-enabled=true --rest-api-docs-enabled=true \

Use the --validator-keys option to specify the directory or file to load the encrypted keystore file(s) and associated password file(s) from.

Run the clients separately

Validators must connect to a beacon node to publish attestations or propose blocks. The beacon node requires internet access, but the connected validators can run on machines without internet access.

Start the beacon node

Run Teku as a beacon node.


teku --network=prater --eth1-endpoint=http://localhost:8545 \
--metrics-enabled --rest-api-enabled

Specify --rest-api-enabled to allow validators to connect to the beacon node.


Don’t pass the validator keys as a command line option to both the beacon node and validator client. This can cause a slashable offense.

By default, validator clients can connect to the beacon node at Use the --rest-api-interface and --rest-api-port options to update the address.

You can specify --rest-api-host-allowlist to allow access to the REST API from specific hostnames.

Start the validator

To run a validator, connect to a running beacon node.

Use the validator-client or vc subcommand to run a Teku as a validator.


teku validator-client --network=prater --beacon-node-api-endpoint= \


Ensure that the validator keys are only provided to the validator. Don’t pass the validator keys as command line options to both the beacon node and validator client. This can a cause a slashable offense.

Specify the beacon node using the --beacon-node-api-endpoint option.

Confirm Teku is running

Use the /liveness endpoint to check whether the node is up.

The endpoint returns the status 200 OK if the node is up or syncing.


curl -I -X GET ""
HTTP/1.1 200 OK
Date: Fri, 05 Feb 2021 03:58:30 GMT
Server: Javalin
Content-Type: application/json
Cache-Control: max-age=0
Content-Length: 0
Questions or feedback? You can discuss issues and obtain free support on Teku Discord channel.
For paid professional support by Consensys, contact us at [email protected].