Bump to latest stack for v1.11.0

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,15 +41,15 @@ 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"
 ```
 
 **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" \
 ```
 

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.

docs/advanced-and-troubleshooting/advanced/partial-deposit.md

@@ -22,23 +22,23 @@ 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"
 ```
 
 **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"
 ```
 
 **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" \
 ```
 

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`.

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`?
 

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

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

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.

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:

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

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

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 "$(pwd):/opt/charon" obolnetwork/charon:v1.10.0 create enr.](/img/gitbook/image-35.png)
+![Screenshot: docker run --rm -v "$(pwd):/opt/charon" 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.