Updated on December 6, 2020
You can run Teku as a beacon chain client and validator in a single process, or as separate processes.
We recommend you run the beacon chain client and validator as a single process if they are to run on the same machine.
By default, Teku connects to
mainnet. Use the
command line option to specify an alternate network.
If the genesis state of a network is not yet known, then
--eth1-endpoint command line
Start the clients in a single process
Start the beacon chain client and validator as a single process by specifying the validator options
teku --network=pyrmont --eth1-endpoint=http://localhost:8545 \ --validator-keys=validator/keys/validator_888eef.json:validator/passwords/validator_888eef.txt \ --rest-api-enabled=true --rest-api-docs-enabled=true \ --metrics-enabled
--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 need to connect to a beacon chain client 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 chain client
Run Teku as a beacon chain client.
teku --network=pyrmont --eth1-endpoint=http://localhost:8545 \ --metrics-enabled --rest-api-enabled
--rest-api-enabled to allow
validators to connect to the beacon node.
Do not pass the validator keys as a command line option to both the beacon chain client and validator client. This can cause a slashable offence.
You can specify
allow access to the REST API from specific hostnames.
Start the validator
To run a validator, connect to a running beacon node.
teku validator-client --network=pyrmont --beacon-node-api-endpoint=http://188.8.131.52:5051 \ --validator-keys=validator/keys:validator/passwords
Ensure that the validator keys are only provided to the validator. Do not pass the validator keys as command line options to both the beacon chain client and validator client. This can a cause a slashable offence.
Specify the beacon chain client using the