Your Execution Client is not configured to store log receipts.
++ Please either enable log receipt storage on your current client or + switch to an Execution Client that supports this feature by default. +
+ Switch your Execution client{' '} +
+ This UI requires an execution client synced to function properly.{' '}
+
+ Please select and Execution client and wait until it's synced
+ before continuing.
+
To retrieve data, this UI scans blockchain events.
++ The first login may take a few minutes, depending on your execution + client. +
+
+ If you want to reduce the waiting time, use a central RPC node (e.g.,
+ Infura).
+ Learn more in our{' '}
+ Documentation.
+
+ This UI requires an execution client synced to function properly.{' '}
+
+ Please, Wait until it's synced before continuing.
+
+ It is crucial that the keys you are about to use are not active or + running on any other machine. Running the same keys in multiple + locations can lead to conflicts, loss of funds, or security + vulnerabilities. +
+Please confirm your understanding by checking the box below:
+{label}
+{file.name}
+ +{telegramId ? telegramId : '-'}
++ {botToken + ? showCurrentBotToken + ? botToken + : '*******************************' + : '-'} +
++ {pendingReports} {pendingReports === 1 ? 'report' : 'reports'} +
+ )} +
+ Frames to Display
2
+ +{thresholdsByEpoch.length}
+
+ Bond is a security collateral submitted by Node Operators
+ before uploading validator keys, covering potential losses from
+ inappropriate actions.
+
+ It can be claimed or reused once the validator exits and any losses + are covered. +
++ {publicRuntimeConfig.defaultChain === 17000 ? '2 Holesky' : '2.4'}{' '} + ETH (stETH / wstETH equivalent) is required for the first validator{' '} +
++ In order to be a Node Operator you must have a synced{' '} + {CHAINS[publicRuntimeConfig.defaultChain as CHAINS]} Node and run MEV + Boost. +
+Execution Client
+{'->'}
+
+ {isECLoading ? (
+
Consensus Client
+{'->'}
+ +
+ {isCCLoading ? (
+
Web3signer
+{'->'}
+
+ {brainLoading ? (
+
MEV Boost
+{'->'}
+
+ {relaysLoading ? (
+
+ Dappnode's Notification system allows you to receive alerts + regardidng your node and validators directly to your telegram. +
+Both inputs are needed to set up alerts ensuring your privacy.
+ {!isTgGetLoading && (!telegramId || !botToken) && ( ++ We highly recommend setting up these notifications to quickly detect + underperformance and avoid penalties. +
++ In order to run a validator, you need to generate the necessary + keystores and deposit data. +
+ ++ Set {withdrawalByAddres} as the withdrawal address while + generating the keystores. This is the Lido Withdrawal Vault on{' '} + {CHAINS[publicRuntimeConfig.defaultChain as CHAINS]} +
++ Prepare your deposit data (.json file) for submitting your keys in the + next step. +
++ Just generate the keys, do NOT execute the deposits. +
++ It is crucial that the keys you are about to use are not active or + running on any other machine. Running the same keys in multiple + locations can lead to conflicts, loss of funds, or security + vulnerabilities. +
+Please confirm your understanding by checking the box below:
+Please, select and sync a client from the Stakers tab.
+ Set Execution Client +Please, select and sync a client from the Stakers tab.
+ Set Consensus Client +Please, if Web3Signer is already installed, re-install it
+ Set Web3Signer +{val.index}
+Install or restart your MEV Boost Package
+ Set MEV Boost ++ Select at least one of the mandatory MEV relays requested by + Lido +
+ {mandatoryRelays?.map((relay, i) => ( +{'- ' + relay.Operator}
+ ))} + Set up Relays +The following selected relays are blacklisted by Lido:
+ {usedBlacklistedRelays.map((relay, i) => ( +Please, remove the Relays above from your MEV config
+ Remove blacklisted relays +
- Make sure you’ve completed all the basic steps before joining the{' '}
-
+ Make sure you've completed all the basic steps before joining the
Community Staking Module
- CSM in Dappnode starter pack
+
+ You can follow a guide in{' '} + + {' '} + Dappnode's Documentation + +
+ + ++ This update affects only CSM on Holesky testnet — CSM on Mainnet + remains fully operational. +
+