diff --git a/docs/private-networks/get-started/install/binary-distribution.md b/docs/private-networks/get-started/install/binary-distribution.md index a88d5536d6c..58601fabf29 100644 --- a/docs/private-networks/get-started/install/binary-distribution.md +++ b/docs/private-networks/get-started/install/binary-distribution.md @@ -16,8 +16,7 @@ description: Install or upgrade Hyperledger Besu from binary distribution Hyperledger Besu supports: * MacOS High Sierra 10.13 or later versions. - * Java 11+. - We recommend using at least Java 17 because that will be the minimum requirement in the next Besu version series. + * Java 17+. You can install Java using `brew install openjdk`. Alternatively, you can manually install the [Java JDK](https://www.oracle.com/java/technologies/downloads). diff --git a/docs/public-networks/get-started/install/binary-distribution.md b/docs/public-networks/get-started/install/binary-distribution.md index a88d5536d6c..58601fabf29 100644 --- a/docs/public-networks/get-started/install/binary-distribution.md +++ b/docs/public-networks/get-started/install/binary-distribution.md @@ -16,8 +16,7 @@ description: Install or upgrade Hyperledger Besu from binary distribution Hyperledger Besu supports: * MacOS High Sierra 10.13 or later versions. - * Java 11+. - We recommend using at least Java 17 because that will be the minimum requirement in the next Besu version series. + * Java 17+. You can install Java using `brew install openjdk`. Alternatively, you can manually install the [Java JDK](https://www.oracle.com/java/technologies/downloads). diff --git a/docs/public-networks/tutorials/besu-teku-mainnet.md b/docs/public-networks/tutorials/besu-teku-mainnet.md index 1b41b1b07d1..d6c7f4e2db4 100644 --- a/docs/public-networks/tutorials/besu-teku-mainnet.md +++ b/docs/public-networks/tutorials/besu-teku-mainnet.md @@ -5,16 +5,16 @@ 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/) +[Teku](https://docs.teku.consensys.net/) 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/). +[Teku](https://docs.teku.consensys.net/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. +For example, you must have Java 17+ if using the Besu and Teku binary distributions. Ensure you meet the [system requirements for Besu on public networks](../get-started/system-requirements.md). @@ -106,16 +106,16 @@ teku \ ``` 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) +the [`--ee-jwt-secret-file`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#ee-jwt-secret-file) option. Also, in the command: -- [`--ee-endpoint`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#ee-endpoint) +- [`--ee-endpoint`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#ee-endpoint) is set to the default URL of Besu's Engine API. -- [`--metrics-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#metrics-enabled) +- [`--metrics-enabled`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#metrics-enabled) enables Teku's metrics exporter. -- [`--rest-api-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#rest-api-enabled) +- [`--rest-api-enabled`](https://docs.teku.consensys.net/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. @@ -138,22 +138,22 @@ teku \ 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. + [`--ee-jwt-secret-file`](https://docs.teku.consensys.net/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) + [`--validators-proposer-default-fee-recipient`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#validators-proposer-default-fee-recipient) option. - The paths to the keystore `.json` file and password `.txt` file created in [step 3](#3-generate-validator-keys) for each validator using the - [`--validator-keys`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#validator-keys) option. + [`--validator-keys`](https://docs.teku.consensys.net/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: -- [`--ee-endpoint`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#ee-endpoint) +- [`--ee-endpoint`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#ee-endpoint) is set to the default URL of Besu's Engine API. -- [`--metrics-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#metrics-enabled) +- [`--metrics-enabled`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#metrics-enabled) enables Teku's metrics exporter. -- [`--rest-api-enabled`](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#rest-api-enabled) +- [`--rest-api-enabled`](https://docs.teku.consensys.net/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. @@ -206,5 +206,5 @@ It may take up to multiple days for your validator to be activated and start pro -[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/ +[Teku configuration file]: https://docs.teku.consensys.net/HowTo/Configure/Use-Configuration-File/ +[Teku command line options]: https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/ diff --git a/docs/public-networks/tutorials/besu-teku-testnet.md b/docs/public-networks/tutorials/besu-teku-testnet.md index 9aee5ced077..0957a5783ac 100644 --- a/docs/public-networks/tutorials/besu-teku-testnet.md +++ b/docs/public-networks/tutorials/besu-teku-testnet.md @@ -5,7 +5,7 @@ Description: How to run Besu and Teku on a testnet # Run Besu and Teku on a testnet Run Besu as an [execution client](../concepts/the-merge.md#execution-clients) and -[Teku](https://docs.teku.consensys.net/en/stable/) +[Teku](https://docs.teku.consensys.net/) as a [consensus client](../concepts/the-merge.md#consensus-clients) on the [Goerli](https://github.com/eth-clients/goerli) and [Sepolia](https://github.com/eth-clients/sepolia) Ethereum testnets. @@ -19,10 +19,10 @@ Ethereum testnets. ## 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/). +[Teku](https://docs.teku.consensys.net/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. +For example, you must have Java 17+ if using the Besu and Teku binary distributions. Ensure you meet the [system requirements for Besu on public networks](../get-started/system-requirements.md). @@ -136,7 +136,7 @@ options in the [Teku configuration 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) +the [`--ee-jwt-secret-file`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#ee-jwt-secret-file) option. You can modify the option values and add other [Teku command line options] as needed. @@ -167,14 +167,14 @@ the options in the [Teku configuration 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. + [`--ee-jwt-secret-file`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#ee-jwt-secret-file) option. - The test Ethereum address created in [step 3](#3-generate-validator-keys) 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) + [`--validators-proposer-default-fee-recipient`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#validators-proposer-default-fee-recipient) option. - The paths to the keystore `.json` file and password `.txt` file created in [step 3](#3-generate-validator-keys) for each validator using the - [`--validator-keys`](https://docs.teku.consensys.net/en/stable/Reference/CLI/CLI-Syntax/#validator-keys) option. + [`--validator-keys`](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#validator-keys) option. Separate the `.json` and `.txt` files with a colon, and separate entries for multiple validators with commas. You can modify the option values and add other [Teku command line options] as needed. @@ -228,5 +228,5 @@ It may take up to multiple days for your validator to be activated and start pro -[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/ +[Teku configuration file]: https://docs.teku.consensys.net/HowTo/Configure/Use-Configuration-File/ +[Teku command line options]: https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/