diff --git a/docs/advanced-and-troubleshooting/advanced/alter-withdrawal-addresses.md b/docs/advanced-and-troubleshooting/advanced/alter-withdrawal-addresses.md
index e2fdc79f01..67485bc692 100644
--- a/docs/advanced-and-troubleshooting/advanced/alter-withdrawal-addresses.md
+++ b/docs/advanced-and-troubleshooting/advanced/alter-withdrawal-addresses.md
@@ -27,7 +27,7 @@ A threshold of operators must decide which public keys they are changing the wit
 **Single public key**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
 ```
@@ -41,7 +41,7 @@ Optionally, users can also specify multiple different `deposit-amounts` (default
 **Multiple public keys, multiple withdrawal addresses**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da,0xc9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045,0x1db3439a222c519ab44bb1144fc28167b4fa6ee6"
 ```
@@ -49,7 +49,7 @@ docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon
 **Multiple public keys, single withdrawal address**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da,0xc9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
 ```
@@ -59,7 +59,7 @@ docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon
 After a threshold of operators have submitted partial alternative deposits, a full aggregated deposit message can be fetched from Obol API.
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit fetch \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit fetch \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
 ```
 
diff --git a/docs/advanced-and-troubleshooting/advanced/change-fee-recipient.md b/docs/advanced-and-troubleshooting/advanced/change-fee-recipient.md
index c3ad7bb643..10d354ba16 100644
--- a/docs/advanced-and-troubleshooting/advanced/change-fee-recipient.md
+++ b/docs/advanced-and-troubleshooting/advanced/change-fee-recipient.md
@@ -31,13 +31,13 @@ The workflow involves three steps:
 Before making changes, list the current fee recipient details for your validators:
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient list
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient list
 ```
 
 To check specific validators only:
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient list \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient list \
   --validator-public-keys="0xYOUR_VALIDATOR_PUBKEY"
 ```
 
@@ -50,7 +50,7 @@ A threshold of operators must each run the `feerecipient sign` command with matc
 Each participating operator runs:
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient sign \
   --fee-recipient="0xNEW_FEE_RECIPIENT_ADDRESS" \
   --validator-public-keys="0xVALIDATOR_PUBKEY_1,0xVALIDATOR_PUBKEY_2"
 ```
@@ -72,7 +72,7 @@ Builder registrations are applied by timestamp. If you set `--timestamp` manuall
 Besides the fee recipient address, the `sign` command also allows you to modify the gas limit for builder registrations by passing the `--gas-limit` flag. If not set, the gas limit is taken from whichever source is most recent for the validator: the cluster lock, the local overrides file, or the registration that currently has quorum on the remote API. Consulting the remote API keeps operators with divergent local files signing the same gas limit.
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient sign \
   --fee-recipient="0xNEW_FEE_RECIPIENT_ADDRESS" \
   --gas-limit=36000000 \
   --validator-public-keys="0xVALIDATOR_PUBKEY_1"
@@ -83,7 +83,7 @@ docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon
 Once a threshold of operators have submitted their partial signatures, any operator can fetch the fully aggregated builder registrations:
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient fetch \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient fetch \
   --validator-public-keys="0xVALIDATOR_PUBKEY_1,0xVALIDATOR_PUBKEY_2"
 ```
 
@@ -110,7 +110,7 @@ A corrupt or invalid overrides file does not block fetching: `fetch` logs a warn
 After fetching, confirm the updated fee recipients are in place:
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 feerecipient list
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 feerecipient list
 ```
 
 You should see the new fee recipient address reflected for the updated validators. If a validator still shows the previous fee recipient, check whether enough operators signed the same fee recipient, gas limit, and timestamp, and whether a newer registration already exists for that validator.
diff --git a/docs/advanced-and-troubleshooting/advanced/partial-deposit.md b/docs/advanced-and-troubleshooting/advanced/partial-deposit.md
index 3b1dcd1291..39d11b4c5d 100644
--- a/docs/advanced-and-troubleshooting/advanced/partial-deposit.md
+++ b/docs/advanced-and-troubleshooting/advanced/partial-deposit.md
@@ -22,7 +22,7 @@ Optionally, users can also specify different multiple `deposit-amounts` (default
 **Single public key**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0x0100000000000000000000000d941218c10b055f0907fe1bbe486ccdaa7e332b"
 ```
@@ -30,7 +30,7 @@ docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon
 **Multiple public keys, multiple withdrawal addresses**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da,0xc9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0x0100000000000000000000000d941218c10b055f0907fe1bbe486ccdaa7e332b,0x0100000000000000000000000e941218c10b055f0907fe1bbe486ccdaa7e332b"
 ```
@@ -38,7 +38,7 @@ docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon
 **Multiple public keys, single withdrawal address**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit sign \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit sign \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da,0xc9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
   --withdrawal-addresses="0x0100000000000000000000000d941218c10b055f0907fe1bbe486ccdaa7e332b"
 ```
@@ -50,7 +50,7 @@ After a threshold of operators have submitted partial deposits, a full deposit c
 `validator-public-keys` are the validator public keys for which the new deposit data should be fetched.
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 deposit fetch \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 deposit fetch \
   --validator-public-keys="0xb9171b84a09da7ff983a36e1c6e873e1537e97ad31aa868185d62c68e255baad8c1cfb83f508460ed96572d2a8e9e9da" \
 ```
 
diff --git a/docs/advanced-and-troubleshooting/advanced/quickstart-combine.md b/docs/advanced-and-troubleshooting/advanced/quickstart-combine.md
index 744aa1434b..bfb935dc13 100644
--- a/docs/advanced-and-troubleshooting/advanced/quickstart-combine.md
+++ b/docs/advanced-and-troubleshooting/advanced/quickstart-combine.md
@@ -83,7 +83,7 @@ Run the following command:
 
 ```shell
 # Combine a clusters private keys
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 combine --cluster-dir /opt/charon/cluster --output-dir /opt/charon/combined
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 combine --cluster-dir /opt/charon/cluster --output-dir /opt/charon/combined
 ```
 
 This command will store the combined keys in the `output-dir`, in this case a folder named `combined`.
diff --git a/docs/advanced-and-troubleshooting/troubleshooting/errors.md b/docs/advanced-and-troubleshooting/troubleshooting/errors.md
index 69e385bfc0..cb93deb696 100644
--- a/docs/advanced-and-troubleshooting/troubleshooting/errors.md
+++ b/docs/advanced-and-troubleshooting/troubleshooting/errors.md
@@ -27,7 +27,7 @@ If your logs show a failed duty with a specific reason code, see [Duty Failure R
 
 `cd` to the directory where your private keys are located (ex: `cd /path/to/charon/enr/private/key`)
 
-Run `docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 enr`. This prints the ENR on your screen.
+Run `docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 enr`. This prints the ENR on your screen.
 
 ### What do I do if lose my `charon-enr-private-key`?
 
diff --git a/docs/advanced-and-troubleshooting/troubleshooting/test_command.mdx b/docs/advanced-and-troubleshooting/troubleshooting/test_command.mdx
index 70c01c5972..308925e176 100644
--- a/docs/advanced-and-troubleshooting/troubleshooting/test_command.mdx
+++ b/docs/advanced-and-troubleshooting/troubleshooting/test_command.mdx
@@ -25,7 +25,7 @@ If you are using the [CDVN](https://github.com/ObolNetwork/charon-distributed-va
 
 ```sh
 # Run from within the charon-distributed-validator-node/ directory
-docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 alpha test peers \
+docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 alpha test peers \
   --lock-file="/opt/charon/.charon/cluster-lock.json" \
   --private-key-file="/opt/charon/.charon/charon-enr-private-key"
   # add any other flags here, e.g. --timeout=1h or --keep-alive=30m
diff --git a/docs/run-a-dv/editing/add-operators.md b/docs/run-a-dv/editing/add-operators.md
index 4476fd1d6d..beab4f6c96 100644
--- a/docs/run-a-dv/editing/add-operators.md
+++ b/docs/run-a-dv/editing/add-operators.md
@@ -31,7 +31,7 @@ charon alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --output-dir=o
 
 # Or, if you prefer running it in Docker
 # (replace 'latest' with the most recent version if needed: https://hub.docker.com/r/obolnetwork/charon/tags)
-docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --output-dir=/opt/charon/output
 ```
 
 ### For New Operators
@@ -43,7 +43,7 @@ New operators being added should run the same command but only need to provide t
 charon alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --output-dir=output --lock-file=cluster-lock.json --private-key-file=charon-enr-private-key
 
 # Or, if you prefer running it in Docker
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --private-key-file=/opt/charon/charon-enr-private-key --lock-file=/opt/charon/cluster-lock.json --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 alpha edit add-operators --new-operator-enrs=enr:-JG4QH... --private-key-file=/opt/charon/charon-enr-private-key --lock-file=/opt/charon/cluster-lock.json --output-dir=/opt/charon/output
 ```
 
 :::info
diff --git a/docs/run-a-dv/editing/add-validators.md b/docs/run-a-dv/editing/add-validators.md
index a9bde47d01..9a7f599800 100644
--- a/docs/run-a-dv/editing/add-validators.md
+++ b/docs/run-a-dv/editing/add-validators.md
@@ -27,7 +27,7 @@ charon alpha edit add-validators --num-validators 10 --withdrawal-addresses=0x<y
 
 # Or, if you prefer running it in Docker
 # (replace 'latest' with the most recent version if needed: https://hub.docker.com/r/obolnetwork/charon/tags)
-docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit add-validators --num-validators 10 --withdrawal-addresses=0x<your_withdrawal_address> --fee-recipient-addresses=0x<your_fee_recipient_address> --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit add-validators --num-validators 10 --withdrawal-addresses=0x<your_withdrawal_address> --fee-recipient-addresses=0x<your_fee_recipient_address> --output-dir=/opt/charon/output
 ```
 
 This command will create a new cluster configuration that includes both existing and new validators. It will also generate the necessary keys for the new validators and deposit data files. The new configuration will be saved in the `output` directory.
diff --git a/docs/run-a-dv/editing/recreate-private-keys.md b/docs/run-a-dv/editing/recreate-private-keys.md
index cc9a9b98a1..18935a2b83 100644
--- a/docs/run-a-dv/editing/recreate-private-keys.md
+++ b/docs/run-a-dv/editing/recreate-private-keys.md
@@ -42,7 +42,7 @@ charon alpha edit recreate-private-keys --output-dir=output
 
 # Or, if you prefer running it in Docker
 # (replace 'latest' with the most recent version if needed: https://hub.docker.com/r/obolnetwork/charon/tags)
-docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit recreate-private-keys --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit recreate-private-keys --output-dir=/opt/charon/output
 ```
 
 This command will:
diff --git a/docs/run-a-dv/editing/remove-operators.md b/docs/run-a-dv/editing/remove-operators.md
index bad8a806e1..e09f60872a 100644
--- a/docs/run-a-dv/editing/remove-operators.md
+++ b/docs/run-a-dv/editing/remove-operators.md
@@ -39,7 +39,7 @@ If you're removing operators within the fault tolerance, all remaining operators
 charon alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH... --output-dir=output
 
 # Docker version
-docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH... --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH... --output-dir=/opt/charon/output
 ```
 
 ### Advanced Removal (Exceeding Fault Tolerance)
@@ -51,7 +51,7 @@ If you're removing more operators than the fault tolerance allows, you must spec
 charon alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH...,enr:-JG4QK... --participating-operator-enrs=enr:-JG4QL...,enr:-JG4QM...,enr:-JG4QN... --output-dir=output
 
 # Docker version
-docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH...,enr:-JG4QK... --participating-operator-enrs=enr:-JG4QL...,enr:-JG4QM...,enr:-JG4QN... --output-dir=/opt/charon/output
+docker run --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit remove-operators --operator-enrs-to-remove=enr:-JG4QH...,enr:-JG4QK... --participating-operator-enrs=enr:-JG4QL...,enr:-JG4QM...,enr:-JG4QN... --output-dir=/opt/charon/output
 ```
 
 :::info
diff --git a/docs/run-a-dv/editing/replace-operator.md b/docs/run-a-dv/editing/replace-operator.md
index 0ffcd5522b..0cc38672fc 100644
--- a/docs/run-a-dv/editing/replace-operator.md
+++ b/docs/run-a-dv/editing/replace-operator.md
@@ -49,7 +49,7 @@ All continuing operators and the new operator must run this command. The old ope
 charon alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK...
 
 # Docker version
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK...
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK...
 ```
 
 #### For the New Operator
@@ -61,7 +61,7 @@ The new operator being added should run the same command but only needs to provi
 charon alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK... --lock-file=cluster-lock.json --private-key-file=charon-enr-private-key
 
 # Docker version
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.10.0 alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK... --lock-file=cluster-lock.json --private-key-file=charon-enr-private-key
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon" -w "/opt/charon" obolnetwork/charon:v1.11.0 alpha edit replace-operator --old-operator-enr=enr:-JG4QH... --new-operator-enr=enr:-JG4QK... --lock-file=cluster-lock.json --private-key-file=charon-enr-private-key
 ```
 
 #### For the Old Operator Being Replaced
diff --git a/docs/run-a-dv/integrations/lido-csm.mdx b/docs/run-a-dv/integrations/lido-csm.mdx
index 6e92e13b6f..1394954d1a 100644
--- a/docs/run-a-dv/integrations/lido-csm.mdx
+++ b/docs/run-a-dv/integrations/lido-csm.mdx
@@ -97,12 +97,12 @@ cd charon-distributed-validator-node
 Use docker to create an ENR
 
 ```sh
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create enr
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 create enr
 ```
 
 ### Back up the private key located in `.charon/charon-enr-private-key`
 
-![Screenshot: docker run --rm -v &quot;$(pwd):/opt/charon&quot; obolnetwork/charon:v1.10.0 create enr.](/img/gitbook/image-35.png)
+![Screenshot: docker run --rm -v &quot;$(pwd):/opt/charon&quot; obolnetwork/charon:v1.11.0 create enr.](/img/gitbook/image-35.png)
 
 :::warning
 What you see in the console starting with `enr:-` is the **public key** for your Charon node (known as an ENR). The **private key** is in the file `.charon/charon-enr-private-key`, be sure to back it up securely.
diff --git a/docs/run-a-dv/prepare/test-a-cluster.mdx b/docs/run-a-dv/prepare/test-a-cluster.mdx
index 06c3783137..14a8095573 100644
--- a/docs/run-a-dv/prepare/test-a-cluster.mdx
+++ b/docs/run-a-dv/prepare/test-a-cluster.mdx
@@ -230,7 +230,7 @@ Regular tests intended for relatively fast run, without putting any major load o
 **Example run**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-enrs="enr:-HW4QMno_MB_ID6GFVxoIQAHHVHZZZjzFctxtX2tm9D95tvaPbHathi8YUP8jh8v2YUAVu2fYWEOB_BT14pt8QgiGg2AgmlkgnY0iXNlY3AyNTZrMaECdpnK83s0dbBwCaEfDIkQ-3nJkkC93STvv6Vmi0bYlzg,enr:-HW4QO2vefLueTBEUGly5hkcpL7NWdMKWx7Nuy9f7z6XZInCbFAc0IZj6bsnmj-Wi4ElS6jNa0Mge5Rkc2WGTVemas2AgmlkgnY0iXNlY3AyNTZrMaECR9SmYQ_1HRgJmNxvh_ER2Sxx78HgKKgKaOkCROYwaDY" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="https://ethereum-hoodi-beacon-api.publicnode.com" \
@@ -255,7 +255,7 @@ https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e
 **Example run**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-definition-file="/opt/charon/test/.charon/cluster-definition.json" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="https://ethereum-hoodi-beacon-api.publicnode.com" \
@@ -280,7 +280,7 @@ https://0xaa58208899c6105603b74396734a6263cc7d947f444f396a90f7b7d3e65d102aec7e5e
 **Example run**
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-lock-file="/opt/charon/test/.charon/cluster-lock.json" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="https://ethereum-hoodi-beacon-api.publicnode.com" \
@@ -313,7 +313,7 @@ Load tests intended for more time consuming run. Beacon nodes are put under heav
 **Example run**
 
 ```sh
-docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-enrs="enr:-HW4QMno_MB_ID6GFVxoIQAHHVHZZZjzFctxtX2tm9D95tvaPbHathi8YUP8jh8v2YUAVu2fYWEOB_BT14pt8QgiGg2AgmlkgnY0iXNlY3AyNTZrMaECdpnK83s0dbBwCaEfDIkQ-3nJkkC93STvv6Vmi0bYlzg,enr:-HW4QO2vefLueTBEUGly5hkcpL7NWdMKWx7Nuy9f7z6XZInCbFAc0IZj6bsnmj-Wi4ElS6jNa0Mge5Rkc2WGTVemas2AgmlkgnY0iXNlY3AyNTZrMaECR9SmYQ_1HRgJmNxvh_ER2Sxx78HgKKgKaOkCROYwaDY" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="http://lighthouse:5052/" \
@@ -347,7 +347,7 @@ https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72d
 **Example run**
 
 ```sh
-docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-definition-file="/opt/charon/test/.charon/cluster-definition.json" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="http://lighthouse:5052/" \
@@ -380,7 +380,7 @@ https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72d
 **Example run**
 
 ```sh
-docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test all \
+docker run --network="charon-distributed-validator-node_dvnode" -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test all \
   --peers-lock-file="/opt/charon/test/.charon/cluster-lock.json" \
   --peers-private-key-file="/opt/charon/test/.charon/charon-enr-private-key" \
   --beacon-endpoints="http://lighthouse:5052/" \
@@ -671,7 +671,7 @@ charon alpha test peers \
 **Example run**
 
 ```sh
-docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 alpha test peers \
+docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 alpha test peers \
   --enrs="enr:-HW4QMno_MB_ID6GFVxoIQAHHVHZZZjzFctxtX2tm9D95tvaPbHathi8YUP8jh8v2YUAVu2fYWEOB_BT14pt8QgiGg2AgmlkgnY0iXNlY3AyNTZrMaECdpnK83s0dbBwCaEfDIkQ-3nJkkC93STvv6Vmi0bYlzg,enr:-HW4QO2vefLueTBEUGly5hkcpL7NWdMKWx7Nuy9f7z6XZInCbFAc0IZj6bsnmj-Wi4ElS6jNa0Mge5Rkc2WGTVemas2AgmlkgnY0iXNlY3AyNTZrMaECR9SmYQ_1HRgJmNxvh_ER2Sxx78HgKKgKaOkCROYwaDY" \
   --private-key-file="/opt/charon/.charon/charon-enr-private-key"
 ```
@@ -685,7 +685,7 @@ docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:
 **Example run**
 
 ```sh
-docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 alpha test peers \
+docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 alpha test peers \
   --definition-file="/opt/charon/.charon/cluster-definition.json" \
   --private-key-file="/opt/charon/.charon/charon-enr-private-key"
 ```
@@ -699,7 +699,7 @@ docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:
 **Example run**
 
 ```sh
-docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 alpha test peers \
+docker run --rm -u $(id -u):$(id -g) -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 alpha test peers \
   --lock-file="/opt/charon/.charon/cluster-lock.json" \
   --private-key-file="/opt/charon/.charon/charon-enr-private-key"
 ```
@@ -806,7 +806,7 @@ charon alpha test beacon \
 **Example run**
 
 ```sh
-docker run --rm obolnetwork/charon:v1.10.0 alpha test beacon \
+docker run --rm obolnetwork/charon:v1.11.0 alpha test beacon \
   --endpoints="https://ethereum-hoodi-beacon-api.publicnode.com"
 ```
 </TabItem>
@@ -819,7 +819,7 @@ docker run --rm obolnetwork/charon:v1.10.0 alpha test beacon \
 **Example run**
 
 ```sh
-docker run --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test beacon \
+docker run --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test beacon \
   --endpoints="http://127.0.0.1:5052/" \
   --load-test \
   --simulation-file-dir="/opt/charon/test"
@@ -887,7 +887,7 @@ charon alpha test validator
 **Example run**
 
 ```sh
-docker run --rm obolnetwork/charon:v1.10.0 alpha test validator \
+docker run --rm obolnetwork/charon:v1.11.0 alpha test validator \
   --validator-api-address="<VALIDATOR_CLIENT_ADDRESS>:3600"
 ```
 </TabItem>
@@ -971,7 +971,7 @@ https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72d
 **Example run**
 
 ```sh
-docker run obolnetwork/charon:v1.10.0 alpha test mev \
+docker run obolnetwork/charon:v1.11.0 alpha test mev \
   --endpoints="\
 https://0xa15b52576bcbf1072f4a011c0f99f9fb6c66f3e1ff321f11f461d15e31b1cb359caa092c71bbded0bae5b5ea401aab7e@aestus.live,\
 https://0xa7ab7a996c8584251c8f925da3170bdfd6ebc75d50f5ddc4050a6fdc77f2a3b5fce2cc750d0865e05d7228af97d69561@agnostic-relay.net,\
@@ -992,7 +992,7 @@ https://0x8c4ed5e24fe5c6ae21018437bde147693f68cda427cd1122cf20819c30eda7ed74f72d
 **Example run**
 
 ```sh
-docker run obolnetwork/charon:v1.10.0 alpha test mev \
+docker run obolnetwork/charon:v1.11.0 alpha test mev \
   --endpoints="\
 https://0xa15b52576bcbf1072f4a011c0f99f9fb6c66f3e1ff321f11f461d15e31b1cb359caa092c71bbded0bae5b5ea401aab7e@aestus.live,\
 https://0xa7ab7a996c8584251c8f925da3170bdfd6ebc75d50f5ddc4050a6fdc77f2a3b5fce2cc750d0865e05d7228af97d69561@agnostic-relay.net,\
@@ -1083,7 +1083,7 @@ charon alpha test infra
 #### Example run
 
 ```sh
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.10.0 alpha test infra \
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd):/opt/charon/test" obolnetwork/charon:v1.11.0 alpha test infra \
         --disk-io-test-file-dir=/opt/charon/test
 ```
 
diff --git a/docs/run-a-dv/start/create-a-dv-alone.mdx b/docs/run-a-dv/start/create-a-dv-alone.mdx
index 06e1ec718d..9181975323 100644
--- a/docs/run-a-dv/start/create-a-dv-alone.mdx
+++ b/docs/run-a-dv/start/create-a-dv-alone.mdx
@@ -34,7 +34,7 @@ git clone https://github.com/ObolNetwork/charon-distributed-validator-cluster.gi
 cd charon-distributed-validator-cluster/
 
 # Run the command provided in the DV Launchpad "Create a cluster alone" flow
-docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.10.0 create cluster --definition-file=...
+docker run -u $(id -u):$(id -g) --rm -v "$(pwd)/:/opt/charon" obolnetwork/charon:v1.11.0 create cluster --definition-file=...
 
 ```
 
@@ -63,7 +63,7 @@ cd charon-distributed-validator-cluster/
 Run the below command to create the validator private key shares and cluster artifacts locally, replacing the example values for `nodes`, `network`, `num-validators`, `fee-recipient-addresses`, and `withdrawal-addresses`. Check the [Charon CLI reference](../../learn/charon/charon-cli-reference.md#create-a-full-cluster-locally) for additional, optional flags to set.
 
 ```sh
-  docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create cluster \
+  docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 create cluster \
     --nodes=6 \
     --network=hoodi \
     --num-validators=1 \
diff --git a/docs/run-a-dv/start/create-a-dv-with-a-group.mdx b/docs/run-a-dv/start/create-a-dv-with-a-group.mdx
index dee014adf0..659a3c6431 100644
--- a/docs/run-a-dv/start/create-a-dv-with-a-group.mdx
+++ b/docs/run-a-dv/start/create-a-dv-with-a-group.mdx
@@ -34,7 +34,7 @@ git clone https://github.com/ObolNetwork/charon-distributed-validator-node.git
 # Change directory
 cd charon-distributed-validator-node/
 # Use docker to create an ENR. Backup the file `.charon/charon-enr-private-key`.
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create enr
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 create enr
 ```
 
 You should expect to see a console output like this:
@@ -155,7 +155,7 @@ Create an ENR using charon:
 
 ```sh
 # Use docker to create an ENR. Backup the file `.charon/charon-enr-private-key`.
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create enr
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 create enr
 ```
 
 For Step 2 of the quickstart:
@@ -273,7 +273,7 @@ You will use the CLI to create the cluster definition file, which you will distr
 3.  Run the `charon create dkg` command that generates DKG cluster-definition.json file.
 
     ```sh
-    docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create dkg 
+    docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 create dkg 
 
     --name="Quickstart" 
 
@@ -384,7 +384,7 @@ For the [DKG](../../learn/charon/dkg.md) to complete, all operators need to be r
 Once the creator gives you the `cluster-definition.json` file and you place it in a `.charon` subdirectory, run:
 
 ```sh
-docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 dkg --publish
+docker run --rm -v "$(pwd):/opt/charon" obolnetwork/charon:v1.11.0 dkg --publish
 ```
 
 and the DKG process should begin.