NethermindEth · AntiD2ta · Dec 12, 2023 · Dec 10, 2023 · Dec 10, 2023 · Dec 11, 2023
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -24,7 +24,7 @@ jobs:
 
       - uses: actions/setup-go@v3
         with:
-          go-version: "1.18.3"
+          go-version: "1.19.0"
 
       - run: chmod +x ./scripts/build-go-darwin-binaries.sh && ./scripts/build-go-darwin-binaries.sh
 
@@ -52,7 +52,7 @@ jobs:
 
       - uses: actions/setup-go@v3
         with:
-          go-version: "1.18.3"
+          go-version: "1.21.0"
 
       - run: scripts\build-go-windows-binaries.ps1
 
@@ -74,7 +74,7 @@ jobs:
 
       - uses: actions/setup-go@v3
         with:
-          go-version: "1.18.3"
+          go-version: "1.19.0"
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v2
@@ -189,7 +189,7 @@ jobs:
           path: sedge
       - uses: actions/setup-go@v3
         with:
-          go-version: "1.18.3"
+          go-version: "1.19.0"
       - name: Run publish PPA script
         env:
           GOPATH: /home/runner/go

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,6 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [v1.3.0] - 2023-12-11
 
 ### Added
 
@@ -21,6 +22,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Remove default bootnodes for networks managed by clients.
 - Remove custom configurations for Chiado and instead use the clients configuration.
+- Update client images.
 
 ## [v1.2.3] - 2023-08-16
 

diff --git a/docs/docs/commands/cli.mdx b/docs/docs/commands/cli.mdx
@@ -42,7 +42,7 @@ This is an example of what you can expect:
 ```
 sedge cli
 2023-03-20 21:54:08 -- [INFO] [Logger Init] Log level: info
-2023-03-20 21:54:08 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-03-20 21:54:08 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 ? Select network goerli
 ? Select node type full-node
 ? Generation path /root/sedge-data

diff --git a/docs/docs/commands/clients.mdx b/docs/docs/commands/clients.mdx
@@ -31,7 +31,7 @@ The execution of `sedge clients` will result in an output like this, that will s
 ```
 $ sedge clients
 2023-10-13 14:13:44 -- [INFO] [Logger Init] Log level: info
-2023-10-13 14:13:45 -- [INFO] You are running the latest version of sedge. Version:  v1.2.3
+2023-10-13 14:13:45 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-10-13 14:13:45 -- [INFO] Listing supported clients for network chiado
 
  #   Execution Clients   Consensus Clients   Validator Clients

diff --git a/docs/docs/commands/deps.mdx b/docs/docs/commands/deps.mdx
@@ -75,7 +75,7 @@ The execution of `sedge deps check` will result in an output like this if everyt
 ```
 $ sedge deps check
 2023-03-21 02:56:04 -- [INFO] [Logger Init] Log level: info
-2023-03-21 02:56:05 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-03-21 02:56:05 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-03-21 02:56:05 -- [INFO] docker is installed
 2023-03-21 02:56:06 -- [INFO] All dependencies are installed and running
 ```
diff --git a/docs/docs/commands/down.mdx b/docs/docs/commands/down.mdx
@@ -38,7 +38,7 @@ The execution of `sedge down` will close and remove all the opened containers an
 ```
 $ sedge down
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v0.5.1
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 [sudo] password for maceo:
 [+] Running 7/7
  ⠿ Container execution-client                            Removed                                                                 93.8s

diff --git a/docs/docs/commands/importKey.mdx b/docs/docs/commands/importKey.mdx
@@ -78,7 +78,7 @@ To import the validator keys, and start the validator client after the import, r
 ```shell
 $ sedge import-key --from keystore -n sepolia --start-validator prysm
 2023-01-26 11:59:34 -- [INFO] [Logger Init] Log level: info
-2023-01-26 11:59:34 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-26 11:59:34 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-26 11:59:34 -- [WARN] The keys path is not the default one, copying the keys to the default path /root/sedge/example/sedge-data/keystore
 2023-01-26 11:59:34 -- [INFO] Importing validator keys

diff --git a/docs/docs/commands/networks.mdx b/docs/docs/commands/networks.mdx
@@ -29,7 +29,7 @@ Global Flags:
 ```
 $ sedge networks
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v0.5.1
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2022-00-00 00:00:00 -- [INFO] Listing supported networks
 
  #   Supported Networks

diff --git a/docs/docs/commands/run.mdx b/docs/docs/commands/run.mdx
@@ -58,7 +58,7 @@ the following command to start all services in the default generation path
 $ sedge run
 Using config file: /root/.sedge.yaml
 2022-12-29 19:55:55 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 19:55:55 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2022-12-29 19:55:55 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2022-12-29 20:40:24 -- [INFO] Checking dependencies: docker
 2022-12-29 20:40:24 -- [INFO] All dependencies are installed on host machine
 2022-12-29 19:55:55 -- [INFO] Setting up containers
@@ -109,7 +109,7 @@ start the validator.
 $ sedge run --services execution,consensus
 Using config file: /root/.sedge.yaml
 2022-12-29 21:03:29 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 21:03:29 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2022-12-29 21:03:29 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2022-12-29 21:03:29 -- [INFO] Checking dependencies: docker
 2022-12-29 21:03:29 -- [INFO] All dependencies are installed on host machine
 2022-12-29 21:03:29 -- [INFO] Setting up containers
@@ -154,7 +154,7 @@ Now you can start the validator client like follow:
 $ sedge run --services validator
 Using config file: /root/.sedge.yaml
 2022-12-29 21:24:12 -- [INFO] [Logger Init] Logging configuration: {Level:debug}
-2022-12-29 21:24:12 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2022-12-29 21:24:12 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2022-12-29 21:24:12 -- [INFO] Checking dependencies: docker
 2022-12-29 21:24:12 -- [INFO] All dependencies are installed on host machine
 2022-12-29 21:24:12 -- [INFO] Setting up containers

diff --git a/docs/docs/commands/show.mdx b/docs/docs/commands/show.mdx
@@ -29,7 +29,7 @@ Global Flags:
 ```
 $ sedge show
 2023-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2023-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.1.0
+2023-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-00-00 00:00:00 -- [INFO] Showing existing containers information
 2023-00-00 00:00:00 -- [INFO] containers:
     - name: sedge-execution-client

diff --git a/docs/docs/commands/slashingExport.mdx b/docs/docs/commands/slashingExport.mdx
@@ -59,7 +59,7 @@ This is an example of exporting slashing protection data from a setup using sepo
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json
 2023-01-06 15:47:56 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:47:57 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:47:57 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-01-06 15:47:57 -- [INFO] Exporting slashing data from client lighthouse
 # highlight-next-line
 2023-01-06 15:47:57 -- [INFO] The slashing protection container is starting...
@@ -72,7 +72,7 @@ Notice in this case the validator client remains stopped because it has been sto
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json --start-validator
 2023-01-06 15:51:11 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:51:11 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:51:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-01-06 15:51:11 -- [INFO] Exporting slashing data from client lighthouse
 2023-01-06 15:51:11 -- [INFO] The slashing protection container is starting...
 2023-01-06 15:51:12 -- [INFO] The slashing container ends successfully.
@@ -87,7 +87,7 @@ Another case may be exporting the slashing data protection when the validator is
 ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json                  
 2023-01-06 15:51:46 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:51:46 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:51:46 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-06 15:51:46 -- [INFO] Stopping validator client
 # highlight-next-line
@@ -108,7 +108,7 @@ In this case, the validator client is stopped before the export and started agai
  ```shell
 $ sedge slashing-export lighthouse -n sepolia --out slashing-protection.json --stop-validator
 2023-01-06 15:52:07 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:52:07 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:52:07 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-06 15:52:07 -- [INFO] Stopping validator client
 # highlight-next-line

diff --git a/docs/docs/commands/slashingImport.mdx b/docs/docs/commands/slashingImport.mdx
@@ -58,7 +58,7 @@ This is an example of importing slashing protection data to a setup using sepoli
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia
 2023-01-06 14:59:11 -- [INFO] [Logger Init] Log level: info
-2023-01-06 14:59:11 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 14:59:11 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-06 14:59:11 -- [INFO] Importing slashing data to client prysm from slashing-export.json
 # highlight-next-line
@@ -72,7 +72,7 @@ Notice in this case the validator client remains stopped because it has been sto
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia --start-validator
 2023-01-06 15:08:05 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:08:06 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:08:06 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 2023-01-06 15:08:06 -- [INFO] Importing slashing data to client prysm from slashing-export.json
 2023-01-06 15:08:06 -- [INFO] The slashing protection container is starting...
 2023-01-06 15:08:06 -- [INFO] The slashing container ends successfully.
@@ -87,7 +87,7 @@ Another case may be importing the slashing data protection when the validator is
 ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia 
 2023-01-06 15:10:27 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:10:27 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:10:27 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-06 15:10:27 -- [INFO] Stopping validator client...
 # highlight-next-line
@@ -108,7 +108,7 @@ In this case, the validator client is stopped before the import and started agai
  ```shell
 $ sedge slashing-import prysm -f slashing-export.json -n sepolia --stop-validator
 2023-01-06 15:12:22 -- [INFO] [Logger Init] Log level: info
-2023-01-06 15:12:22 -- [INFO] You are running the latest version of sedge. Version:  v0.6.0
+2023-01-06 15:12:22 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 # highlight-next-line
 2023-01-06 15:12:22 -- [INFO] Stopping validator client...
 # highlight-next-line

diff --git a/docs/docs/commands/version.mdx b/docs/docs/commands/version.mdx
@@ -29,6 +29,6 @@ Global Flags:
 ```
 $ sedge version
 2022-00-00 00:00:00 -- [INFO] [Logger Init] Log level: info
-2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v0.5.1
+2022-00-00 00:00:00 -- [INFO] You are running the latest version of sedge. Version:  v1.3.0
 sedge v0.5.1
 ```
diff --git a/docs/docs/guidelines/new-network.mdx b/docs/docs/guidelines/new-network.mdx
@@ -31,15 +31,15 @@ RELAY_URL={{if .RelayURL}}{{.RelayURL}}{{else}}https://0xafa4c6985aa049fb79dd370
 4. Create an entry on `configs/init.go`, in the method `InitNetworksConfigs()` with the network information, for example:
 ```
 {
-	Name:               NetworkSepolia,
-	RequireJWT:         true,
-	NetworkService:     "merge",
-	GenesisForkVersion: "0x90000069",
-	DefaultECBootnodes: []string{
-		"enode://9246d00bc8fd1742e5ad2428b80fc4dc45d786283e05ef6edbd9002cbc335d40998444732fbe921cb88e1d2c73d1b1de53bae6a2237996e9bfe14f871baf7066@18.168.182.86:30303", "enode://ec66ddcf1a974950bd4c782789a7e04f8aa7110a72569b6e65fcd51e937e74eed303b1ea734e4d19cfaec9fbff9b6ee65bf31dcb50ba79acce9dd63a6aca61c7@52.14.151.177:30303",
-	},
-	DefaultCCBootnodes: []string{
-		"enr:-Iq4QMCTfIMXnow27baRUb35Q8iiFHSIDBJh6hQM5Axohhf4b6Kr_cOCu0htQ5WvVqKvFgY28893DHAg8gnBAXsAVqmGAX53x8JggmlkgnY0gmlwhLKAlv6Jc2VjcDI1NmsxoQK6S-Cii_KmfFdUJL2TANL3ksaKUnNXvTCv1tLwXs0QgIN1ZHCCIyk", "enr:-Ly4QFoZTWR8ulxGVsWydTNGdwEESueIdj-wB6UmmjUcm-AOPxnQi7wprzwcdo7-1jBW_JxELlUKJdJES8TDsbl1EdNlh2F0dG5ldHOI__78_v2bsV-EZXRoMpA2-lATkAAAcf__________gmlkgnY0gmlwhBLYJjGJc2VjcDI1NmsxoQI0gujXac9rMAb48NtMqtSTyHIeNYlpjkbYpWJw46PmYYhzeW5jbmV0cw-DdGNwgiMog3VkcIIjKA", "enr:-KG4QE5OIg5ThTjkzrlVF32WT_-XT14WeJtIz2zoTqLLjQhYAmJlnk4ItSoH41_2x0RX0wTFIe5GgjRzU2u7Q1fN4vADhGV0aDKQqP7o7pAAAHAyAAAAAAAAAIJpZIJ2NIJpcISlFsStiXNlY3AyNTZrMaEC-Rrd_bBZwhKpXzFCrStKp1q_HmGOewxY3KwM8ofAj_ODdGNwgiMog3VkcIIjKA", "enr:-L64QC9Hhov4DhQ7mRukTOz4_jHm4DHlGL726NWH4ojH1wFgEwSin_6H95Gs6nW2fktTWbPachHJ6rUFu0iJNgA0SB2CARqHYXR0bmV0c4j__________4RldGgykDb6UBOQAABx__________-CaWSCdjSCaXCEA-2vzolzZWNwMjU2azGhA17lsUg60R776rauYMdrAz383UUgESoaHEzMkvm4K6k6iHN5bmNuZXRzD4N0Y3CCIyiDdWRwgiMo",
+	NetworkSepolia: {
+		Name:               NetworkSepolia,
+		NetworkService:     "merge",
+		GenesisForkVersion: "0x90000069",
+		SupportsMEVBoost:   true,
+		CheckpointSyncURL:  "https://sepolia.checkpoint-sync.ethpandaops.io",
+		RelayURLs: []string{
+			"https://0x845bd072b7cd566f02faeb0a4033ce9399e42839ced64e8b2adcfc859ed1e8e1a5a293336a49feac6d9a5edb779be53a@builder-relay-sepolia.flashbots.net",
+		},
 	},
 },
 ```

diff --git a/docs/docs/networks/chiado.mdx b/docs/docs/networks/chiado.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 id: chiado
 ---
 

diff --git a/docs/docs/networks/gnosis.mdx b/docs/docs/networks/gnosis.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 id: gnosis
 ---
 

diff --git a/docs/docs/networks/holesky.mdx b/docs/docs/networks/holesky.mdx
@@ -0,0 +1,59 @@
+---
+sidebar_position: 4
+id: holesky
+---
+
+# Holesky
+
+Holesky is Ethereum's public testnet that serves as a technical experimentation platform for Ethereum's infrastructure, staking designs, and protocol-level developments. This testing environment brings its own set of validators, a dedicated block explorer, and an ecosystem of faucets.
+
+## Supported Execution Clients
+- [Nethermind](https://docs.nethermind.io/)
+- [Geth](https://geth.ethereum.org/docs/)
+- [Erigon](https://github.com/ledgerwatch/erigon)
+- [Besu](https://besu.hyperledger.org/en/stable/)
+
+## Supported Consensus Clients
+- [Lighthouse](https://lighthouse-book.sigmaprime.io/)
+- [Lodestar](https://chainsafe.github.io/lodestar/)
+- [Prysm](https://docs.prylabs.network/docs/getting-started/)
+- [Teku](https://docs.teku.consensys.net/en/latest/)
+
+## Supported Validator Clients
+- [Lighthouse](https://lighthouse-book.sigmaprime.io/)
+- [Lodestar](https://chainsafe.github.io/lodestar/)
+- [Prysm](https://docs.prylabs.network/docs/getting-started/)
+- [Teku](https://docs.teku.consensys.net/en/latest/)
+
+
+## Generating a Full Node
+
+To generate a setup of a full node (without a validator node) with random clients, you only need to add the `--no-validator` to `sedge generate full-node`. For example:
+
+```bash
+sedge generate full-node --no-validator --network=holesky
+```
+
+## Generating a Full Node with a Validator
+
+To generate a setup of a validator with random clients, you need to omit the `--no-validator` flag. For example:
+
+```bash
+sedge generate full-node --network=holesky
+```
+
+## Create keystore for validator
+
+To create a keystore for a validator, you need to run the following command:
+
+```bash
+sedge keys --network holesky
+```
+
+## Running your setup
+
+Once you have generated your setup, you can run it with the following command:
+
+```
+sedge run
+```
diff --git a/docs/docs/quickstart/complete-guide.mdx b/docs/docs/quickstart/complete-guide.mdx
@@ -41,14 +41,14 @@ want to use another installation method:
   <TabItem value="curl" label="curl">
 
   ```
-  curl -L https://github.com/NethermindEth/sedge/releases/download/v1.2.3/sedge-v1.2.3-linux-amd64 --output sedge
+  curl -L https://github.com/NethermindEth/sedge/releases/download/v1.3.0/sedge-v1.3.0-linux-amd64 --output sedge
   ```
 
   </TabItem>
   <TabItem value="wget" label="wget">
 
   ```
-  wget https://github.com/NethermindEth/sedge/releases/download/v1.2.3/sedge-v1.2.3-linux-amd64 -O sedge
+  wget https://github.com/NethermindEth/sedge/releases/download/v1.3.0/sedge-v1.3.0-linux-amd64 -O sedge
   ```
 
   </TabItem>
@@ -149,6 +149,10 @@ more, you can check [here in our documentation](/docs/commands/generate).
 
 The `--latest` flag can be used for the `full-node`, `execution`, `consensus` and `validator` commands.
 
+:::
+
+:::info
+
 You can update your client's versions using the following commands if the clients release any version:
 1. Run `docker compose -f /path/to/docker-compose.yml pull` to update the images.
 2. Run `docker compose -f /path/to/docker-compose.yml up -d` to restart the containers.

diff --git a/docs/docs/quickstart/index.md b/docs/docs/quickstart/index.md
@@ -4,8 +4,12 @@ keywords:
   - sedge
   - installation
   - validator
-  - goerli
   - mainnet
+  - goerli
+  - sepolia
+  - holesky
+  - chiado
+  - gnosis
   - Ethereum
   - mev-boost
 ---

diff --git a/docs/docs/quickstart/install-guide.mdx b/docs/docs/quickstart/install-guide.mdx
@@ -37,7 +37,7 @@ Downloading any binary from the internet risks downloading files that malicious,
   </TabItem>
 </Tabs>
 
-  > Replace `<VERSION>` with the desired version number, e.g 1.2.2; `<OS>` with your OS, e.g linux; and `<ARCH>` with your architecture, e.g amd64.
+  > Replace `<VERSION>` with the desired version number, e.g 1.3.0; `<OS>` with your OS, e.g linux; and `<ARCH>` with your architecture, e.g amd64.
 
 2. Open a console or terminal instance on the directory you downloaded the binary.
 3. Set binary as executable executing `chmod +x <binary>` in the Terminal. Replace `<binary>` with the name of the downloaded binary.

diff --git a/docs/src/components/HomepageFeatures/index.js b/docs/src/components/HomepageFeatures/index.js
@@ -8,7 +8,7 @@ const FeatureList = [
         Svg: require('@site/static/img/ethereum.svg').default,
         description: (
             <>
-                We fully support Mainnet, Goerli(testnet), Sepolia(testnet) and Holesky(testnet).
+                We fully support Mainnet, and Testnets (Goerli, Sepolia, and Holesky).
 
             </>
         ),