replace goerli with holesky

docs/assets/postman/postman_collection.json

@@ -3868,7 +3868,7 @@
               "host": ["{{rpc-http-host}}"],
               "port": "{{rpc-http-port}}"
             },
-            "description": "Returns the [network ID](https://besu.hyperledger.org/en/stable/Concepts/NetworkID-And-ChainID).\n\n#### Parameters\n\nNone\n\n#### Returns\n\n`result` : *string* - Current network ID.\n\n| Network ID | Chain | Network | Description\n|------------|-------|---------|-------------------------------|\n| `1`        | ETH   | Mainnet | Main Ethereum network         |\n| `3`        | ETH   | Ropsten | PoW test network              |\n| `4`        | ETH   | Rinkeby | PoA test network using Clique |\n| `5`        | ETH   | Goerli  | PoA test network using Clique |\n| `2018`     | ETH   | Dev     | PoW development network       |\n| `1`        | ETC   | Classic | Main Ethereum Classic network |\n| `7`        | ETC   | Mordor  | PoW test network              |\n\n> **note**\n>\n> For almost all networks network ID and chain ID are the same.\nThe only networks in the table above with different network and chain IDs are\nClassic with a chain ID of `61` and Mordor with a chain ID of `63`."
+            "description": "Returns the [network ID](https://besu.hyperledger.org/en/stable/Concepts/NetworkID-And-ChainID).\n\n#### Parameters\n\nNone\n\n#### Returns\n\n`result` : *string* - Current network ID.\n\n| Network ID | Chain | Network | Description\n|------------|-------|---------|-------------------------------|\n| `1`        | ETH   | Mainnet | Main Ethereum network         |\n| `2018`     | ETH   | Dev     | PoW development network       |\n| `1`        | ETC   | Classic | Main Ethereum Classic network |\n| `7`        | ETC   | Mordor  | PoW test network              |\n\n> **note**\n>\n> For almost all networks network ID and chain ID are the same.\nThe only networks in the table above with different network and chain IDs are\nClassic with a chain ID of `61` and Mordor with a chain ID of `63`."
           },
           "response": [
             {

docs/private-networks/get-started/install/run-docker-image.md

@@ -67,7 +67,7 @@ When running in a Docker container, [`--nat-method`](../../../public-networks/ho
 You can specify [Besu environment variables](../../../public-networks/reference/cli/options.md#specify-options) with the Docker image instead of the command line options.
 
 ```bash
-docker run -p 30303:30303 -p 8545:8545 -e BESU_RPC_HTTP_ENABLED=true -e BESU_NETWORK=goerli hyperledger/besu:latest
+docker run -p 30303:30303 -p 8545:8545 -e BESU_RPC_HTTP_ENABLED=true -e BESU_NETWORK=holesky hyperledger/besu:latest
 ```
 
 :::caution "Unsupported address type exception"

docs/private-networks/how-to/configure/bootnodes.md

@@ -24,7 +24,7 @@ To find peers, configure one or more bootnodes. To configure a specific set of p
 
 :::note Mainnet and public testnets
 
-For Mainnet and the Sepolia and Goerli testnets, Hyperledger Besu has an internal list of enode URLs and uses this list automatically when you specify the [`--network`](../../../public-networks/reference/cli/options.md#network) option.
+For Mainnet and the Sepolia and Holesky testnets, Hyperledger Besu has an internal list of enode URLs and uses this list automatically when you specify the [`--network`](../../../public-networks/reference/cli/options.md#network) option.
 
 :::
 

docs/private-networks/how-to/monitor/chainlens.md

@@ -64,7 +64,7 @@ This may take 5–10 minutes for the all services to start and the ingestion syn
 After starting Chainlens, you can view information about your network.
 
 :::note
-Screenshots in this section are taken from the [Chainlens Goerli network](https://goerli.chainlens.com/dashboard).
+Screenshots in this section are taken from the [Chainlens Holesky network](https://holesky.chainlens.com/dashboard).
 :::
 
 The **Dashboard** page provides an aggregated view of network activities.

docs/public-networks/concepts/genesis-file.md

@@ -11,7 +11,7 @@ tags:
 
 The genesis file defines the first block in the chain, and the first block defines which chain you want to join.
 
-For Ethereum Mainnet and public testnets (for example, Goerli) the genesis configuration definition is in Besu and used when specifying a public network using the [`--network`](../reference/cli/options.md#network) command line option.
+For Ethereum Mainnet and public testnets (for example, Holesky) the genesis configuration definition is in Besu and used when specifying a public network using the [`--network`](../reference/cli/options.md#network) command line option.
 
 For private networks, [create a JSON genesis file](https://consensys.net/blog/quorum/hyperledger-besu-how-to-create-an-ethereum-genesis-file/), then specify the genesis file using the [`--genesis-file`](../reference/cli/options.md#genesis-file) command line option.
 

docs/public-networks/concepts/network-and-chain-id.md

@@ -37,7 +37,7 @@ Besu sets the chain ID (and by default the network ID) automatically, using eith
 | Network   | Chain | Chain ID | Network ID | Type        |
 | --------- | ----- | -------- | ---------- | ----------- |
 | `mainnet` | ETH   | 1        | 1          | Production  |
-| `goerli`  | ETH   | 5        | 5          | Test        |
+| `holesky` | ETH   | 17000    | 17000      | Test        |
 | `sepolia` | ETH   | 11155111 | 11155111   | Test        |
 | `dev`     | ETH   | 2018     | 2018       | Development |
 | `classic` | ETC   | 61       | 1          | Production  |

docs/public-networks/get-started/connect/sync-node.md

@@ -79,7 +79,7 @@ Enable checkpoint sync using [`--sync-mode=CHECKPOINT`](../../reference/cli/opti
 
 Checkpoint sync behaves like [snap sync](#snap-synchronization), but instead of syncing from the genesis block, it syncs from a specific checkpoint block configured in the [Besu genesis file](../../concepts/genesis-file.md).
 
-Ethereum Mainnet and the Goerli testnet configurations already define default checkpoints, so you don't have to add this yourself.
+Ethereum Mainnet and the Holesky testnet configurations already define default checkpoints, so you don't have to add this yourself.
 
 For other networks, you can configure a checkpoint in the genesis file by specifying the block hash, number, and total difficulty as in the following example.
 

docs/public-networks/get-started/connect/testnet.md

@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 
 # 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.
+Run Besu as an [execution client](../../concepts/the-merge.md#execution-clients) with any consensus client on the [Holesky](https://github.com/eth-clients/holesky) 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).
 
@@ -42,15 +42,15 @@ You will specify `jwtsecret.hex` when starting Besu and the consensus client. Th
 
 If you're running the consensus client as a beacon node only, skip to the [next step](#3-start-besu).
 
-If you're also running the consensus client as 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).
+If you're also running the consensus client as 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 [Holesky faucets](https://github.com/eth-clients/holesky) and [Sepolia faucets](https://github.com/eth-clients/sepolia#meta-data-sepolia).
 
 :::note
 
 If you can't get ETH using the faucet, you can ask for help on the [EthStaker Discord](https://discord.io/ethstaker).
 
 :::
 
-Generate validator keys for one or more validators using the [Goerli Staking Launchpad](https://goerli.launchpad.ethereum.org/) (or [request to become validator on Sepolia](https://notes.ethereum.org/zvkfSmYnT0-uxwwEegbCqg)).
+Generate validator keys for one or more validators using the [Holesky Staking Launchpad](https://holesky.launchpad.ethereum.org/) (or [request to become validator on Sepolia](https://notes.ethereum.org/zvkfSmYnT0-uxwwEegbCqg)).
 
 :::info
 
@@ -64,24 +64,6 @@ Run the following command or specify the options in a [configuration file](../..
 
 <Tabs>
 
-<TabItem value="Goerli" label="Goerli" default>
-
-```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="*" \
-  --engine-rpc-enabled        \
-  --engine-jwt-secret=<path to jwtsecret.hex>
-```
-
-</TabItem>
-
 <TabItem value="Holesky" label="Holesky">
 
 ```bash
@@ -178,6 +160,6 @@ If you're running the consensus client as a beacon node only, you're all set. If
 
 ### 6. Stake ETH
 
-Stake your testnet ETH for one or more validators using the [Goerli Staking Launchpad](https://goerli.launchpad.ethereum.org/).
+Stake your testnet ETH for one or more validators using the [Holesky Staking Launchpad](https://holesky.launchpad.ethereum.org/).
 
-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.
+You can check your validator status by searching your Ethereum address on the [Holesky Beacon Chain explorer](https://holesky.beaconcha.in/). It may take up to multiple days for your validator to be activated and start proposing blocks.

docs/public-networks/get-started/install/run-docker-image.md

@@ -85,7 +85,7 @@ When running in a Docker container, [`--nat-method`](../../how-to/connect/specif
 You can specify [Besu environment variables](../../reference/cli/options.md#specify-options) with the Docker image instead of the command line options.
 
 ```bash title="Example"
-docker run -p 30303:30303 -p 8545:8545 -e BESU_RPC_HTTP_ENABLED=true -e BESU_NETWORK=goerli hyperledger/besu:latest
+docker run -p 30303:30303 -p 8545:8545 -e BESU_RPC_HTTP_ENABLED=true -e BESU_NETWORK=holesky hyperledger/besu:latest
 ```
 
 :::caution Unsupported address type exception
@@ -110,12 +110,12 @@ To run a node that mines blocks at a rate suitable for testing purposes with Web
 docker run -p 8546:8546 --mount type=bind,source=/<myvolume/besu/testnode>,target=/var/lib/besu hyperledger/besu:latest --miner-enabled --miner-coinbase fe3b557e8fb62b89f4916b721be55ceb828dbd73 --rpc-ws-enabled --network=dev --data-path=/var/lib/besu
 ```
 
-### Run a node on Goerli testnet
+### Run a node on Holesky testnet
 
-To run a node on Goerli:
+To run a node on Holesky:
 
 ```bash
-docker run -p 30303:30303 --mount type=bind,source=/<myvolume/besu/goerli>,target=/var/lib/besu hyperledger/besu:latest --network=goerli --data-path=/var/lib/besu
+docker run -p 30303:30303 --mount type=bind,source=/<myvolume/besu/holesky>,target=/var/lib/besu hyperledger/besu:latest --network=holesky --data-path=/var/lib/besu
 ```
 
 ### Run a node on Ethereum Mainnet

docs/public-networks/get-started/start-node.md

@@ -24,7 +24,7 @@ To delete the local block data, delete the `database` directory in the `besu/bui
 
 ## Genesis configuration
 
-Besu specifies the genesis configuration, and sets the network ID and bootnodes when connecting to [Goerli](#run-a-node-on-goerli-testnet), [Sepolia](#run-a-node-on-sepolia-testnet), and [Mainnet](#run-a-node-on-ethereum-mainnet).
+Besu specifies the genesis configuration, and sets the network ID and bootnodes when connecting to [Holesky](#run-a-node-on-holesky-testnet), [Sepolia](#run-a-node-on-sepolia-testnet), and [Mainnet](#run-a-node-on-ethereum-mainnet).
 
 :::info
 
@@ -80,18 +80,6 @@ The following settings are a security risk in production environments:
 
 :::
 
-## Run a node on Goerli testnet
-
-To run a node on [Goerli](https://github.com/goerli/testnet) specifying a data directory:
-
-```bash
-besu --network=goerli --data-path=<path>/<goerlidata-path>
-```
-
-Where `<path>` and `<goerlidata-path>` are the path and directory to save the Goerli chain data to.
-
-See the [guide on connecting to a testnet](connect/testnet.md) for more information.
-
 ## Run a node on Holesky testnet
 
 To run a node on [Holesky](https://github.com/eth-clients/holesky) specifying a data directory:
@@ -106,7 +94,7 @@ See the [guide on connecting to a testnet](connect/testnet.md) for more informat
 
 ## Run a node on Sepolia testnet
 
-To run a node on [Sepolia](https://github.com/goerli/sepolia) specifying a data directory:
+To run a node on [Sepolia](https://github.com/eth-clients/sepolia) specifying a data directory:
 
 ```bash
 besu --network=sepolia --data-path=<path>/<sepoliadata-path>

docs/public-networks/how-to/configure-java/pass-jvm-options.md

@@ -17,5 +17,5 @@ For Bash-based executions, you can set the variable for only the scope of the pr
 
 ```bash
 BESU_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 \
-besu --network=goerli
+besu --network=holesky
 ```

docs/public-networks/how-to/monitor/logging.md

@@ -60,10 +60,10 @@ If you have more specific requirements, you can create your own [log4j2 configur
 
 For Bash-based executions, you can set the variable for only the scope of the program execution by setting it before starting Besu.
 
-To set the debug logging and start Besu connected to the Goerli testnet:
+To set the debug logging and start Besu connected to the Holesky testnet:
 
 ```bash
-LOG4J_CONFIGURATION_FILE=./debug.xml besu --network=goerli
+LOG4J_CONFIGURATION_FILE=./debug.xml besu --network=holesky
 ```
 
 ### Log rotation

docs/public-networks/index.md

@@ -9,7 +9,7 @@ tags:
 
 # Hyperledger Besu for public networks
 
-Besu serves as an [execution client](concepts/the-merge.md#execution-clients) on public proof-of-stake Ethereum networks such as Ethereum Mainnet, Goerli, and Sepolia.
+Besu serves as an [execution client](concepts/the-merge.md#execution-clients) on public proof-of-stake Ethereum networks such as Ethereum Mainnet, Holesky, and Sepolia.
 
 You can also run Besu using proof of work on [Ethereum Classic (ETC)](how-to/use-pow/mining.md).
 

docs/public-networks/reference/api/index.md

@@ -1540,7 +1540,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"debug_standardTraceBlockToFile",
   "jsonrpc": "2.0",
   "id": 1,
   "result": [
-    "/Users/me/mynode/goerli/data/traces/block_0x2dc0b6c4-4-0x4ff04c4a-1612820117332"
+    "/Users/me/mynode/holesky/data/traces/block_0x2dc0b6c4-4-0x4ff04c4a-1612820117332"
   ]
 }
 ```
@@ -1595,7 +1595,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"debug_standardTraceBadBlockToFil
   "jsonrpc": "2.0",
   "id": 1,
   "result": [
-    "/Users/me/mynode/goerli/data/traces/block_0x53741e9e-0-0x407ec43d-1600951088172"
+    "/Users/me/mynode/holesky/data/traces/block_0x53741e9e-0-0x407ec43d-1600951088172"
   ]
 }
 ```
@@ -6751,7 +6751,7 @@ None
 | Network ID | Chain | Network | Description                   |
 | ---------- | ----- | ------- | ----------------------------- |
 | `1`        | ETH   | Mainnet | Main Ethereum network         |
-| `5`        | ETH   | Goerli  | PoS test network              |
+| `17000`    | ETH   | Holesky | PoS test network              |
 | `11155111` | ETH   | Sepolia | PoS test network              |
 | `2018`     | ETH   | Dev     | PoW development network       |
 | `1`        | ETC   | Classic | Main Ethereum Classic network |
@@ -6795,7 +6795,7 @@ curl -X POST --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":53
 
 </TabItem>
 
-<TabItem value="JSON result for Goerli" label="JSON result for Goerli"> 
+<TabItem value="JSON result for Holesky" label="JSON result for Holesky"> 
 
 ```json
 {

docs/public-networks/reference/cli/options.md

@@ -2427,23 +2427,23 @@ You must specify `DOCKER` when using the [Besu Docker image](../../get-started/i
 <TabItem value="Example" label="Example">
 
 ```bash
---network=goerli
+--network=holesky
 ```
 
 </TabItem>
 
 <TabItem value="Environment variable" label="Environment variable">
 
 ```bash
-BESU_NETWORK=goerli
+BESU_NETWORK=holesky
 ```
 
 </TabItem>
 
 <TabItem value="Configuration file" label="Configuration file">
 
 ```bash
-network="goerli"
+network="holesky"
 ```
 
 </TabItem>
@@ -2457,7 +2457,6 @@ Possible values are:
 | Network   | Chain | Type        | Default Sync Mode  | Description                                                    |
 | :-------- | :---- | :-----------| :----------------- | :------------------------------------------------------------- |
 | `mainnet` | ETH   | Production  | [FAST](#sync-mode) | The main network                                               |
-| `goerli`  | ETH   | Test        | [FAST](#sync-mode) | A PoS network                                                  |
 | `holesky` | ETH   | Test        | [FAST](#sync-mode) | A PoS network                                                  |
 | `sepolia` | ETH   | Test        | [FAST](#sync-mode) | A PoS network                                                  |
 | `dev`     | ETH   | Development | [FULL](#sync-mode) | A PoW network with a low difficulty to enable local CPU mining |
@@ -5501,7 +5500,7 @@ Enables or disables performing version compatibility checks when starting Besu.
 If set to `true`, it checks that the version of Besu being started is the same
 or later than the version of Besu that previously started with the same data directory.
 
-The default is `false` for named networks, such as Mainnet or Goerli, and `true`
+The default is `false` for named networks, such as Mainnet or Holesky, and `true`
 for non-named networks.
 
 ### `Xhelp`

docs/public-networks/reference/cli/subcommands.md

@@ -89,7 +89,7 @@ besu blocks export [--start-block=<LONG>] [--end-block=<LONG>] --to=<block-file>
 <TabItem value="Example" label="Example">
 
 ```bash
-besu --network=goerli --data-path=/home/data/ blocks export --start-block=100 --end-block=300 --to=/home/exportblock.bin
+besu --network=holesky --data-path=/home/data/ blocks export --start-block=100 --end-block=300 --to=/home/exportblock.bin
 ```
 
 </TabItem>
@@ -121,7 +121,7 @@ besu operator generate-log-bloom-cache [--start-block=<BLOCK_NUMBER>] [--end-blo
 <TabItem value="Example" label="Example">
 
 ```bash
-besu --network=goerli --data-path=/project/goerli operator generate-log-bloom-cache --start-block=0 --end-block=100000
+besu --network=holesky --data-path=/project/holesky operator generate-log-bloom-cache --start-block=0 --end-block=100000
 ```
 
 </TabItem>

docs/public-networks/reference/evm-tool.md

@@ -328,15 +328,15 @@ The [Besu genesis file](genesis-items.md) to use when evaluating the EVM. Most u
 <TabItem value="Syntax" label="Syntax" default>
 
 ```bash
---chain=<mainnet|goerli|sepolia|dev|classic|mordor|kotti|astor>
+--chain=<mainnet|sepolia|dev|classic|mordor|kotti|astor>
 ```
 
 </TabItem>
 
   <TabItem value="Example" label="Example">
 
 ```bash
---chain=goerli
+--chain=holesky
 ```
 
 </TabItem>