Refactor .env clients

Author: KaloyanTanev

.env.sample.holesky

@@ -4,18 +4,20 @@
 # Overrides network for all the relevant services.
 NETWORK=holesky
 
-# Execution layer client to be used in a DV setup.
-# Available options: nethermind.
+# Execution layer client to be used in a DV setup. Uncomment only the desired client.
 EL=el-nethermind
-# Consensus layer client to be used in a DV setup.
-# Available options: lighthouse, grandine.
+
+# Consensus layer client to be used in a DV setup. Uncomment only the desired client.
 CL=cl-lighthouse
-# Validator client to be used in a DV setup.
-# Available options: lodestar, nimbus.
+#CL=cl-grandine
+
+# Validator client to be used in a DV setup. Uncomment only the desired client.
 VC=vc-lodestar
-# MEV client to be used in a DV setup.
-# Available options: mevboost, commitboost.
+#VC=vc-nimbus
+
+# MEV client to be used in a DV setup. Uncomment only the desired client.
 MEV=mev-mevboost
+#MEV=mev-commitboost
 
 # Do not edit. These profiles and files dictate Docker which client types and from where to start for execution, consensus, validator and MEV.
 # The actual adjustable values are specified above

.env.sample.hoodi

@@ -4,18 +4,20 @@
 # Overrides network for all the relevant services.
 NETWORK=hoodi
 
-# Execution layer client to be used in a DV setup.
-# Available options: nethermind.
+# Execution layer client to be used in a DV setup. Uncomment only the desired client.
 EL=el-nethermind
-# Consensus layer client to be used in a DV setup.
-# Available options: lighthouse, grandine.
+
+# Consensus layer client to be used in a DV setup. Uncomment only the desired client.
 CL=cl-lighthouse
-# Validator client to be used in a DV setup.
-# Available options: lodestar, nimbus.
+#CL=cl-grandine
+
+# Validator client to be used in a DV setup. Uncomment only the desired client.
 VC=vc-lodestar
-# MEV client to be used in a DV setup.
-# Available options: mevboost, commitboost.
+#VC=vc-nimbus
+
+# MEV client to be used in a DV setup. Uncomment only the desired client.
 MEV=mev-mevboost
+#MEV=mev-commitboost
 
 # Do not edit. These profiles and files dictate Docker which client types and from where to start for execution, consensus, validator and MEV.
 # The actual adjustable values are specified above

.env.sample.mainnet

@@ -4,18 +4,20 @@
 # Overrides network for all the relevant services.
 NETWORK=mainnet
 
-# Execution layer client to be used in a DV setup.
-# Available options: nethermind.
+# Execution layer client to be used in a DV setup. Uncomment only the desired client.
 EL=el-nethermind
-# Consensus layer client to be used in a DV setup.
-# Available options: lighthouse, grandine.
+
+# Consensus layer client to be used in a DV setup. Uncomment only the desired client.
 CL=cl-lighthouse
-# Validator client to be used in a DV setup.
-# Available options: lodestar, nimbus.
+#CL=cl-grandine
+
+# Validator client to be used in a DV setup. Uncomment only the desired client.
 VC=vc-lodestar
-# MEV client to be used in a DV setup.
-# Available options: mevboost, commitboost.
+#VC=vc-nimbus
+
+# MEV client to be used in a DV setup. Uncomment only the desired client.
 MEV=mev-mevboost
+#MEV=mev-commitboost
 
 # Do not edit. These profiles and files dictate Docker which client types and from where to start for execution, consensus, validator and MEV.
 # The actual adjustable values are specified above