From 315f478498738fbce5f0de568dae7ecc732bb9fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ois=C3=ADn=20Kyne?= Date: Thu, 8 Aug 2024 13:26:18 +0100 Subject: [PATCH] Changes from PR review --- docs/start/quickstart-exit.mdx | 101 +-------------------------------- 1 file changed, 2 insertions(+), 99 deletions(-) diff --git a/docs/start/quickstart-exit.mdx b/docs/start/quickstart-exit.mdx index 26c147d4e5..9b7c5a228d 100644 --- a/docs/start/quickstart-exit.mdx +++ b/docs/start/quickstart-exit.mdx @@ -126,10 +126,9 @@ It needs to be the validator client that is connected to your Charon client taki

Exit a distributed validator using DappNode

- Below steps provide steps to exit a validator using DappNode.
  1. - Navigate to the config tab of your obol DappNode package. Click 'Packages', then click 'My Packages', and enter the obol package. Go to the config tab. At the bottom right corner of the page, click on 'Show Advanced Editor'. + Navigate to the config tab of your Obol DappNode package. Click 'Packages', then click 'My Packages', and enter the Obol package. Go to the config tab. At the bottom right corner of the page, click on 'Show Advanced Editor'. Config Tab
  2. @@ -147,102 +146,6 @@ It needs to be the validator client that is connected to your Charon client taki - - - - 
    -          
-            {String.raw`docker exec -it charon-distributed-validator-node-teku-1 /opt/teku/bin/teku voluntary-exit \
-            --beacon-node-api-endpoint="http://charon:3600/" \
-            --confirmation-enabled=false \
-            --validator-keys="/opt/charon/validator_keys:/opt/charon/validator_keys" \
-            --epoch=162304`}
-          
-
    -     - - The following executes an interactive command inside the Nimbus VC container. It copies all files and directories from the Keystore path /home/user/data/charon to the newly created /home/user/data/wd directory. -

    - 
    -          
-            {String.raw`docker exec -it charon-distributed-validator-node-nimbus-1 /bin/bash -c ' \
-        
-            mkdir /home/user/data/wd
-            cp -r /home/user/data/charon/ /home/user/data/wd
-                
-            /home/user/nimbus_beacon_node deposits exit --all --epoch=162304 --rest-url=http://charon:3600/ --data-dir=/home/user/data/wd/'`}
-          
-
    -     - - The following executes an interactive command inside the Lodestar VC container to exit all validators. - 
    -          
-            {String.raw`docker exec -it charon-distributed-validator-node-lodestar-1 node /usr/app/packages/cli/bin/lodestar validator voluntary-exit \
-            --beaconNodes="http://charon:3600" \
-            --dataDir=/opt/data \
-            --exitEpoch=162304 \
-            --network=goerli \
-            --yes`}
-          
-
    -     - - The following executes an interactive command inside the Lighthouse VC container to exit all validators. The exit is submitted for the current epoch. - 
    -          
-            {String.raw`docker exec -it charon-distributed-validator-node-lighthouse-1 /bin/bash -c '\
-                for file in /opt/charon/keys/*; do \
-                  filename=$(basename $file);
-                  if [[ $filename == *".json"* ]]; then
-                  `}
-                    {String.raw`  keystore=$`}
-                    {String.raw`{filename%.*};
-                    `}
-                    {String.raw`lighthouse account validator exit \
-                      --beacon-node http://charon:3600 \
-                      --keystore /opt/charon/keys/$keystore.json \
-                      --network goerli \
-                      --password-file /opt/charon/keys/$keystore.txt \
-                      --no-confirmation \
-                      --no-wait;
-                  fi;
-                done;'`}
-          
-
    -     - - Currently voluntary exits through Prysm are not supported. This is because Prysm support voluntary exits only if both the validator client and the beacon node are running on Prysm. Note that this is incompatible with Charon, as the Charon client intercepts the communication between the validator client and the consensus layer. - - - Voluntary exit can be submitted directly through Charon as well. The partially signed exit messages are stored (centrally) on Obol's infrastructure. Exits through Charon are submitted per validator. All active validators public keys for a given cluster lock can be listed with: - 
    -          
-        {String.raw`docker exec -it charon-distributed-validator-node-charon-1 /bin/sh -c 'charon exit active-validator-list \
-    --beacon-node-endpoints="http://lighthouse:5052"'`}
-          
-
    - Then a signed partial exit for validator can be submitted by: - 
    -          
-        {String.raw`docker exec -it charon-distributed-validator-node-charon-1 /bin/sh -c 'charon exit sign \
-    --beacon-node-endpoints="http://lighthouse:5052" \
-    --validator-public-key="" \
-    --publish-timeout="5m"'`}
-          
-
    - After a sufficient amount of signed partial exits from node operators in the cluster is cumulated, a full (complete) exit is created. The threshold is the same as the one submitted during the cluster creation. After a full exit message is created, any operator from the cluster can broadcast it to the beacon chain with: - 
    -          
-        {String.raw`docker exec -it charon-distributed-validator-node-charon-1 /bin/sh -c 'charon exit broadcast \
-    --beacon-node-endpoints="http://lighthouse:5052" \
-    --validator-public-key="" \
-    --publish-timeout="5m"'`}
-          
-
    -     -     -     @@ -342,7 +245,7 @@ It needs to be the validator client that is connected to your Charon client taki Below steps provide steps to exit a validator using DappNode.
    1. - Navigate to the config tab of your obol DappNode package. Click 'Packages', then click 'My Packages', and enter the obol package. Go to the config tab. At the bottom right corner of the page, click on 'Show Advanced Editor'. + Navigate to the config tab of your Obol DappNode package. Click 'Packages', then click 'My Packages', and enter the Obol package. Go to the config tab. At the bottom right corner of the page, click on 'Show Advanced Editor'. Config Tab