Post-Merge doc updates (#1173)
* Post-Merge doc updates Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * minor link fixes Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * minor edits Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * add sync warnings Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * update allowlist values Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * minor edits Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * minor edits Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * apply reviewer feedback Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> * address reviewer feedback Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net> Signed-off-by: Alexandra Tran <alexandra.tran@consensys.net>pull/1179/head
Alexandra Tran
2 years ago
committed by
GitHub
parent
8456d56a47
commit
80a58d10f1
@ -0,0 +1,9 @@ |
||||
--- |
||||
title: Connect to a network overview |
||||
hide: |
||||
- feedback |
||||
--- |
||||
|
||||
# Connect to a network |
||||
|
||||
This section provides information on connecting Besu to a public Ethereum network. |
||||
@ -0,0 +1,145 @@ |
||||
--- |
||||
description: How to connect to Mainnet |
||||
--- |
||||
|
||||
# Connect to Mainnet |
||||
|
||||
!!! important |
||||
|
||||
[The Merge](../../concepts/the-merge.md) was executed on **September 15, 2022**. |
||||
Ethereum is now a [proof of stake](../../concepts/proof-of-stake.md) network, and a full Ethereum |
||||
node requires both [an execution client and a consensus client](../../concepts/the-merge.md#execution-and-consensus-clients). |
||||
|
||||
Run Besu as an [execution client](../../concepts/the-merge.md#execution-clients) with any consensus |
||||
client on Ethereum Mainnet. |
||||
|
||||
If you're using [Teku] as a consensus client, you can follow the |
||||
[Besu and Teku Mainnet tutorial](../../tutorials/besu-teku-mainnet.md). |
||||
|
||||
## Prerequisites |
||||
|
||||
- [Besu installed](../install/binary-distribution.md). |
||||
- A consensus client installed. |
||||
For example, [Teku](https://docs.teku.consensys.net/en/latest/). |
||||
|
||||
## Steps |
||||
|
||||
### 1. Generate the shared secret |
||||
|
||||
Run the following command: |
||||
|
||||
```bash |
||||
openssl rand -hex 32 | tr -d "\n" > jwtsecret.hex |
||||
``` |
||||
|
||||
You will specify `jwtsecret.hex` when starting Besu and the consensus client. |
||||
This is a shared JWT secret the clients use to authenticate each other when using the |
||||
[Engine API](../../how-to/use-engine-api.md). |
||||
|
||||
### 2. Start Besu |
||||
|
||||
Run the following command or specify the options in a |
||||
[configuration file](../../how-to/configuration-file.md): |
||||
|
||||
```bash |
||||
besu \ |
||||
--sync-mode=X_SNAP \ |
||||
--data-storage-format=BONSAI \ |
||||
--rpc-http-enabled=true \ |
||||
--rpc-http-host=0.0.0.0 \ |
||||
--rpc-ws-enabled=true \ |
||||
--rpc-ws-host=0.0.0.0 \ |
||||
--host-allowlist=<IP of Besu node>,127.0.0.1,localhost \ |
||||
--engine-host-allowlist=<IP of Besu node>,127.0.0.1,localhost \ |
||||
--Xmerge-support=true \ |
||||
--engine-jwt-secret=<path to jwtsecret.hex> |
||||
``` |
||||
|
||||
Specify: |
||||
|
||||
- The path to the `jwtsecret.hex` file generated in [step 1](#1-generate-the-shared-secret) |
||||
using the [`--engine-jwt-secret`](../../reference/cli/options.md#engine-jwt-secret) option. |
||||
- The IP address of your Besu node using the [`--host-allowlist`](../../reference/cli/options.md#host-allowlist) |
||||
and [`--engine-host-allowlist`](../../reference/cli/options.md#engine-host-allowlist) options. |
||||
|
||||
Also, in the command: |
||||
|
||||
- [`--sync-mode`](../../reference/cli/options.md#sync-mode) specifies using [snap sync](sync-node.md#snap-synchronization). |
||||
- [`--data-storage-format`](../../reference/cli/options.md#data-storage-format) specifies using |
||||
[Bonsai Tries](../../concepts/data-storage-formats.md#bonsai-tries). |
||||
- [`--rpc-http-enabled`](../../reference/cli/options.md#rpc-http-enabled) enables the HTTP JSON-RPC |
||||
service. |
||||
- [`--rpc-http-host`](../../reference/cli/options.md#rpc-http-host) is set to `0.0.0.0` to allow |
||||
remote RPC connections. |
||||
- [`--rpc-ws-enabled`](../../reference/cli/options.md#rpc-ws-enabled) enables the WebSocket JSON-RPC |
||||
service. |
||||
- [`--rpc-ws-host`](../../reference/cli/options.md#rpc-ws-host) is set to `0.0.0.0` to allow remote |
||||
RPC connections. |
||||
- `--Xmerge-support` enables Merge support. |
||||
|
||||
You can modify the option values and add other [command line options](../../reference/cli/options.md) |
||||
as needed. |
||||
|
||||
### 3. Generate validator keys and stake ETH |
||||
|
||||
If you're running a beacon node only, skip to the next step. |
||||
|
||||
If you're also running a validator client, have a funded Ethereum address ready (32 ETH and gas fees |
||||
for each validator). |
||||
|
||||
Generate validator keys and stake your ETH for one or more validators using the |
||||
[Staking Launchpad](https://launchpad.ethereum.org/en/). |
||||
|
||||
!!! important |
||||
|
||||
Save the password you use to generate each key pair in a `.txt` file. |
||||
You should also have a `.json` file for each validator key pair. |
||||
|
||||
Ensure your Besu node is fully synced before submitting your staking deposit. |
||||
This can take several days. |
||||
|
||||
### 4. Start the consensus client |
||||
|
||||
Refer to your consensus client documentation to configure and start the consensus client. |
||||
|
||||
!!! important |
||||
|
||||
If you're running a validator client, make sure you set a fee recipient address. |
||||
|
||||
If you're using Teku, follow the [Besu and Teku Mainnet tutorial](../../tutorials/besu-teku-mainnet.md#5-start-teku). |
||||
|
||||
### 5. After starting the clients |
||||
|
||||
After starting Besu and the consensus client, your node starts syncing and connecting to peers. |
||||
|
||||
!!! example |
||||
|
||||
=== "Besu logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:42:09.295-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.298-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.848-07:00 | nioEventLoopGroup-3-8 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 4 |
||||
2022-03-21 20:42:18.452-07:00 | nioEventLoopGroup-3-8 | INFO | SyncTargetManager | Found common ancestor with peer Peer 0xab3a286b181721c794... at block 55127 |
||||
2022-03-21 20:42:18.454-07:00 | nioEventLoopGroup-3-8 | INFO | PipelineChainDownloader | PipelineChain download complete |
||||
``` |
||||
|
||||
=== "Teku logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:43:24.355 INFO - Syncing *** Target slot: 76092, Head slot: 2680, Remaining slots: 73412, Connected peers: 8 |
||||
2022-03-21 20:43:36.363 INFO - Syncing *** Target slot: 76093, Head slot: 2879, Remaining slots: 73214, Connected peers: 10 |
||||
2022-03-21 20:43:48.327 INFO - Syncing *** Target slot: 76094, Head slot: 3080, Remaining slots: 73014, Connected peers: 8 |
||||
2022-03-21 20:44:00.339 INFO - Syncing *** Target slot: 76095, Head slot: 3317, Remaining slots: 72778, Connected peers: 6 |
||||
2022-03-21 20:44:12.353 INFO - Syncing *** Target slot: 76096, Head slot: 3519, Remaining slots: 72577, Connected peers: 9 |
||||
``` |
||||
|
||||
You can check your validator status by searching your Ethereum address on the [Beacon Chain explorer](https://beaconcha.in/). |
||||
It may take up to multiple days for your validator to be activated and start proposing blocks. |
||||
|
||||
!!! caution |
||||
|
||||
If you restart your node before snap or checkpoint sync completes, syncing restarts from scratch. |
||||
|
||||
<!-- links --> |
||||
[Teku]: https://docs.teku.consensys.net/en/stable/ |
||||
@ -0,0 +1,151 @@ |
||||
--- |
||||
Description: How to connect to a testnet |
||||
--- |
||||
|
||||
# Connect to a testnet |
||||
|
||||
Run Besu as an [execution client](../../concepts/the-merge.md#execution-clients) with any consensus |
||||
client on the [Goerli](https://github.com/eth-clients/goerli) and |
||||
[Sepolia](https://github.com/eth-clients/sepolia) testnets. |
||||
|
||||
If you're using [Teku](https://docs.teku.consensys.net/en/latest/) as a consensus client, you can |
||||
follow the [Besu and Teku testnet tutorial](../../tutorials/besu-teku-testnet.md). |
||||
|
||||
!!! note |
||||
|
||||
Sepolia is a permissioned network and you can't run a validator client on it without |
||||
[requesting to become a validator](https://notes.ethereum.org/zvkfSmYnT0-uxwwEegbCqg) first. |
||||
You can connect your consensus client using the beacon node only, without any validator duties. |
||||
|
||||
## Prerequisites |
||||
|
||||
- [Besu installed](../install/binary-distribution.md). |
||||
- A consensus client installed. |
||||
For example, [Teku](https://docs.teku.consensys.net/en/latest/). |
||||
|
||||
## Steps |
||||
|
||||
### 1. Generate the shared secret |
||||
|
||||
Run the following command: |
||||
|
||||
```bash |
||||
openssl rand -hex 32 | tr -d "\n" > jwtsecret.hex |
||||
``` |
||||
|
||||
You will specify `jwtsecret.hex` when starting Besu and the consensus client. |
||||
This is a shared JWT secret the clients use to authenticate each other when using the |
||||
[Engine API](../../how-to/use-engine-api.md). |
||||
|
||||
### 2. Start Besu |
||||
|
||||
Run the following command or specify the options in a |
||||
[configuration file](../../how-to/configuration-file.md): |
||||
|
||||
=== "Goerli" |
||||
|
||||
```bash |
||||
besu \ |
||||
--network=goerli \ |
||||
--rpc-http-enabled=true \ |
||||
--rpc-http-host=0.0.0.0 \ |
||||
--rpc-http-cors-origins="*" \ |
||||
--rpc-ws-enabled=true \ |
||||
--rpc-ws-host=0.0.0.0 \ |
||||
--host-allowlist="*" \ |
||||
--engine-host-allowlist="*" \ |
||||
--Xmerge-support=true \ |
||||
--engine-jwt-secret=<path to jwtsecret.hex> |
||||
``` |
||||
|
||||
=== "Sepolia" |
||||
|
||||
```bash |
||||
besu \ |
||||
--network=sepolia \ |
||||
--rpc-http-enabled=true \ |
||||
--rpc-http-host=0.0.0.0 \ |
||||
--rpc-http-cors-origins="*" \ |
||||
--rpc-ws-enabled=true \ |
||||
--rpc-ws-host=0.0.0.0 \ |
||||
--host-allowlist="*" \ |
||||
--engine-host-allowlist="*" \ |
||||
--Xmerge-support=true \ |
||||
--engine-jwt-secret=<path to jwtsecret.hex> |
||||
``` |
||||
|
||||
Specify the path to the `jwtsecret.hex` file generated in [step 1](#1-generate-the-shared-secret) |
||||
using the [`--engine-jwt-secret`](../../reference/cli/options.md#engine-jwt-secret) option. |
||||
|
||||
You can modify the option values and add other [command line options](../../reference/cli/options.md) |
||||
as needed. |
||||
|
||||
### 3. Generate validator keys and stake ETH |
||||
|
||||
If you're running a beacon node only, skip to the next step. |
||||
|
||||
If you're running a validator client, create a test Ethereum address (you can do this in |
||||
[MetaMask](https://metamask.zendesk.com/hc/en-us/articles/360015289452-How-to-create-an-additional-account-in-your-wallet)). |
||||
Fund this address with testnet ETH (32 ETH and gas fees for each validator) using a faucet. |
||||
See the list of [Goerli faucets](https://github.com/eth-clients/goerli#meta-data-g%C3%B6rli) and |
||||
[Sepolia faucets](https://github.com/eth-clients/sepolia#meta-data-sepolia). |
||||
|
||||
!!! note |
||||
|
||||
If you're unable to get ETH using the faucet, you can ask for help on the |
||||
[EthStaker Discord](https://discord.io/ethstaker). |
||||
|
||||
Generate validator keys and stake your testnet ETH for one or more validators using the |
||||
[Goerli Staking Launchpad](https://goerli.launchpad.ethereum.org/). |
||||
|
||||
!!! important |
||||
|
||||
Save the password you use to generate each key pair in a `.txt` file. |
||||
You should also have a `.json` file for each validator key pair. |
||||
|
||||
Ensure your Besu node is fully synced before submitting your staking deposit. |
||||
This can take several days. |
||||
|
||||
### 4. Start the consensus client |
||||
|
||||
Refer to your consensus client documentation to configure and start the consensus client. |
||||
|
||||
!!! important |
||||
|
||||
If you're running a validator client, make sure you set a fee recipient address. |
||||
|
||||
If you're using Teku, follow the [Besu and Teku testnet tutorial](../../tutorials/besu-teku-testnet.md#5-start-teku). |
||||
|
||||
### 5. After starting the clients |
||||
|
||||
After starting Besu and the consensus client, your node starts syncing and connecting to peers. |
||||
|
||||
!!! example |
||||
|
||||
=== "Besu logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:42:09.295-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.298-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.848-07:00 | nioEventLoopGroup-3-8 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 4 |
||||
2022-03-21 20:42:18.452-07:00 | nioEventLoopGroup-3-8 | INFO | SyncTargetManager | Found common ancestor with peer Peer 0xab3a286b181721c794... at block 55127 |
||||
2022-03-21 20:42:18.454-07:00 | nioEventLoopGroup-3-8 | INFO | PipelineChainDownloader | PipelineChain download complete |
||||
``` |
||||
|
||||
=== "Teku logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:43:24.355 INFO - Syncing *** Target slot: 76092, Head slot: 2680, Remaining slots: 73412, Connected peers: 8 |
||||
2022-03-21 20:43:36.363 INFO - Syncing *** Target slot: 76093, Head slot: 2879, Remaining slots: 73214, Connected peers: 10 |
||||
2022-03-21 20:43:48.327 INFO - Syncing *** Target slot: 76094, Head slot: 3080, Remaining slots: 73014, Connected peers: 8 |
||||
2022-03-21 20:44:00.339 INFO - Syncing *** Target slot: 76095, Head slot: 3317, Remaining slots: 72778, Connected peers: 6 |
||||
2022-03-21 20:44:12.353 INFO - Syncing *** Target slot: 76096, Head slot: 3519, Remaining slots: 72577, Connected peers: 9 |
||||
``` |
||||
|
||||
!!! caution |
||||
|
||||
If you restart your node before snap or checkpoint sync completes, syncing restarts from scratch. |
||||
|
||||
You can check your validator status by searching your Ethereum address on the |
||||
[Goerli Beacon Chain explorer](https://goerli.beaconcha.in/). |
||||
It may take up to multiple days for your validator to be activated and start proposing blocks. |
||||
@ -0,0 +1,205 @@ |
||||
--- |
||||
Description: How to run Besu and Teku on Mainnet |
||||
--- |
||||
|
||||
# Run Besu and Teku on Mainnet |
||||
|
||||
Run Besu as an [execution client](../concepts/the-merge.md#execution-clients) and |
||||
[Teku](https://docs.teku.consensys.net/en/stable/) |
||||
as a [consensus client](../concepts/the-merge.md#consensus-clients) on Ethereum Mainnet. |
||||
|
||||
## 1. Install Besu and Teku |
||||
|
||||
Install [Besu](../get-started/install/binary-distribution.md) and |
||||
[Teku](https://docs.teku.consensys.net/en/stable/HowTo/Get-Started/Installation-Options/Install-Binaries/). |
||||
|
||||
Ensure you meet the prerequisites for the installation option you use. |
||||
For example, you must have Java 11+ if using the Besu and Teku binary distributions. |
||||
|
||||
Ensure you meet the [system requirements for Besu on public networks](../get-started/system-requirements.md). |
||||
|
||||
## 2. Generate the shared secret |
||||
|
||||
Run the following command: |
||||
|
||||
```bash |
||||
openssl rand -hex 32 | tr -d "\n" > jwtsecret.hex |
||||
``` |
||||
|
||||
You will specify `jwtsecret.hex` when starting both Besu and Teku. |
||||
This is a shared JWT secret the clients use to authenticate each other when using the |
||||
[Engine API](../how-to/use-engine-api.md). |
||||
|
||||
## 3. Start Besu |
||||
|
||||
Run the following command or specify the options in a [configuration file](../how-to/configuration-file.md): |
||||
|
||||
```bash |
||||
besu \ |
||||
--sync-mode=X_SNAP \ |
||||
--data-storage-format=BONSAI \ |
||||
--rpc-http-enabled=true \ |
||||
--rpc-http-host="0.0.0.0" \ |
||||
--rpc-ws-enabled=true \ |
||||
--rpc-ws-host="0.0.0.0" \ |
||||
--host-allowlist=<IP of Besu node>,127.0.0.1,localhost \ |
||||
--engine-host-allowlist=<IP of Besu node>,127.0.0.1,localhost \ |
||||
--Xmerge-support=true \ |
||||
--engine-jwt-secret=<path to jwtsecret.hex> |
||||
``` |
||||
|
||||
Specify: |
||||
|
||||
- The path to the `jwtsecret.hex` file generated in [step 2](#2-generate-the-shared-secret) using |
||||
the [`--engine-jwt-secret`](../reference/cli/options.md#engine-jwt-secret) option. |
||||
- The IP address of your Besu node using the [`--host-allowlist`](../reference/cli/options.md#host-allowlist) |
||||
and [`--engine-host-allowlist`](../reference/cli/options.md#engine-host-allowlist) options. |
||||
|
||||
Also, in the command: |
||||
|
||||
- [`--sync-mode`](../reference/cli/options.md#sync-mode) specifies using [snap sync](../get-started/connect/sync-node.md#snap-synchronization). |
||||
- [`--data-storage-format`](../reference/cli/options.md#data-storage-format) specifies using [Bonsai Tries](../concepts/data-storage-formats.md#bonsai-tries). |
||||
- [`--rpc-http-enabled`](../reference/cli/options.md#rpc-http-enabled) enables the HTTP JSON-RPC |
||||
service. |
||||
- [`--rpc-http-host`](../reference/cli/options.md#rpc-http-host) is set to `0.0.0.0` to allow remote |
||||
RPC connections. |
||||
- [`--rpc-ws-enabled`](../reference/cli/options.md#rpc-ws-enabled) enables the WebSocket JSON-RPC |
||||
service. |
||||
- [`--rpc-ws-host`](../reference/cli/options.md#rpc-ws-host) is set to `0.0.0.0` to allow remote RPC |
||||
connections. |
||||
- `--Xmerge-support` enables Merge support. |
||||
|
||||
You can modify the option values and add other [command line options](../reference/cli/options.md) |
||||
as needed. |
||||
|
||||
## 4. Generate validator keys and stake ETH |
||||
|
||||
If you're running a [beacon node only](#beacon-node-only), skip to the next step. |
||||
|
||||
If you're also running a [validator client](#beacon-node-and-validator-client), have a funded |
||||
Ethereum address ready (32 ETH and gas fees for each validator). |
||||
|
||||
Generate validator keys and stake your ETH for one or more validators using the |
||||
[Staking Launchpad](https://launchpad.ethereum.org/en/). |
||||
|
||||
!!! important |
||||
|
||||
Save the password you use to generate each key pair in a `.txt` file. |
||||
You should also have a `.json` file for each validator key pair. |
||||
|
||||
Ensure your Besu node is fully synced before submitting your staking deposit. |
||||
This can take several days. |
||||
|
||||
## 5. Start Teku |
||||
|
||||
Open a new terminal window. |
||||
|
||||
### Beacon node only |
||||
|
||||
To run Teku as a beacon node only (without validator duties), run the following command or specify the |
||||
options in the [Teku configuration file]: |
||||
|
||||
```bash |
||||
teku \ |
||||
--data-path "datadir-teku" \ |
||||
--ee-endpoint http://localhost:8551 \ |
||||
--ee-jwt-secret-file <path to jwtsecret.hex> \ |
||||
--log-destination console \ |
||||
--rest-api-enabled=true \ |
||||
``` |
||||
|
||||
Specify the path to the `jwtsecret.hex` file generated in [step 2](#2-generate-the-shared-secret) using |
||||
the [`--ee-jwt-secret-file`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#ee-jwt-secret-file) |
||||
option. |
||||
|
||||
Also, in the command: |
||||
|
||||
- [`--data-path`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#data-base-path-data-path) |
||||
is set to the path to the Teku data directory. |
||||
- [`ee-endpoint`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#ee-endpoint) |
||||
is set to the default URL of Besu's Engine API. |
||||
- [`log-destination`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#log-destination) |
||||
specifies outputting log information to the console. |
||||
- [`rest-api-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#rest-api-enabled) |
||||
enables Teku's REST API service. |
||||
|
||||
You can modify the option values and add other [Teku command line options] as needed. |
||||
|
||||
### Beacon node and validator client |
||||
|
||||
To run Teku as a beacon node and validator in a single process, run the following command or specify |
||||
the options in the [Teku configuration file]: |
||||
|
||||
```bash |
||||
teku \ |
||||
--data-path "datadir-teku" \ |
||||
--ee-endpoint http://localhost:8551 \ |
||||
--ee-jwt-secret-file <path to jwtsecret.hex> \ |
||||
--log-destination console \ |
||||
--rest-api-enabled=true \ |
||||
--validators-proposer-default-fee-recipient=<ETH address> \ |
||||
--validator-keys=<path to key file>:<path to mnemonic file>[,<path to key file>:<path to mnemonic file>,...] \ |
||||
``` |
||||
|
||||
Specify: |
||||
|
||||
- The path to the `jwtsecret.hex` file generated in [step 2](#2-generate-the-shared-secret) using the |
||||
[`--ee-jwt-secret-file`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#ee-jwt-secret-file) option. |
||||
- An Ethereum address you own as the default fee recipient using the |
||||
[`--validators-proposer-default-fee-recipient`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#validators-proposer-default-fee-recipient) |
||||
option. |
||||
- The paths to the keystore `.json` file and password `.txt` file created in |
||||
[step 4](#4-generate-validator-keys-and-stake-eth) for each validator using the |
||||
[`--validator-keys`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#validator-keys) option. |
||||
Separate the `.json` and `.txt` files with a colon, and separate entries for multiple validators with commas. |
||||
|
||||
Also, in the command: |
||||
|
||||
- [`--data-path`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#data-base-path-data-path) |
||||
is set to the path to the Teku data directory. |
||||
- [`ee-endpoint`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#ee-endpoint) |
||||
is set to the default URL of Besu's Engine API. |
||||
- [`log-destination`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#log-destination) |
||||
specifies outputting log information to the console. |
||||
- [`rest-api-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#rest-api-enabled) |
||||
enables Teku's REST API service. |
||||
|
||||
You can modify the option values and add other [Teku command line options] as needed. |
||||
|
||||
## After starting Besu and Teku |
||||
|
||||
After starting Besu and Teku, your node starts syncing and connecting to peers. |
||||
|
||||
!!! example |
||||
|
||||
=== "Besu logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:42:09.295-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.298-07:00 | EthScheduler-Timer-0 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0 |
||||
2022-03-21 20:42:14.848-07:00 | nioEventLoopGroup-3-8 | INFO | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 4 |
||||
2022-03-21 20:42:18.452-07:00 | nioEventLoopGroup-3-8 | INFO | SyncTargetManager | Found common ancestor with peer Peer 0xab3a286b181721c794... at block 55127 |
||||
2022-03-21 20:42:18.454-07:00 | nioEventLoopGroup-3-8 | INFO | PipelineChainDownloader | PipelineChain download complete |
||||
``` |
||||
|
||||
=== "Teku logs" |
||||
|
||||
```bash |
||||
2022-03-21 20:43:24.355 INFO - Syncing *** Target slot: 76092, Head slot: 2680, Remaining slots: 73412, Connected peers: 8 |
||||
2022-03-21 20:43:36.363 INFO - Syncing *** Target slot: 76093, Head slot: 2879, Remaining slots: 73214, Connected peers: 10 |
||||
2022-03-21 20:43:48.327 INFO - Syncing *** Target slot: 76094, Head slot: 3080, Remaining slots: 73014, Connected peers: 8 |
||||
2022-03-21 20:44:00.339 INFO - Syncing *** Target slot: 76095, Head slot: 3317, Remaining slots: 72778, Connected peers: 6 |
||||
2022-03-21 20:44:12.353 INFO - Syncing *** Target slot: 76096, Head slot: 3519, Remaining slots: 72577, Connected peers: 9 |
||||
``` |
||||
|
||||
You can check your validator status by searching your Ethereum address on the [Beacon Chain explorer](https://beaconcha.in/). |
||||
It may take up to multiple days for your validator to be activated and start proposing blocks. |
||||
|
||||
!!! caution |
||||
|
||||
If you restart your node before snap or checkpoint sync completes, syncing restarts from scratch. |
||||
|
||||
<!--links--> |
||||
|
||||
[Teku configuration file]: https://docs.teku.consensys.net/en/latest/HowTo/Configure/Use-Configuration-File/ |
||||
[Teku command line options]: https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/ |
||||
Loading…
Reference in new issue