Nimbus BN
Last updated
Last updated
the latest version of Nimbus, extract the zipped file, and then run the checksum verification process to ensure that the "nimbus_beacon_node" and "nimbus_validator_client" files have not been tampered with during download.
Expected output: Verify output of the checksum verification.
If checksum is verified, extract the consensus client and validator client binaries into the (/usr/local/bin)
directory (as a best practice). Then, clean up the duplicated copies.
Create an account (nimbus
) without server access for the Nimbus Beacon Node & Validator Client to run as a background service. This type of user account will not have root access so it restricts potential attackers to only the Nimbus Beacon Node & Validator Client services in the unlikely event that they manage to infiltrate via a compromised client update.
Create a directory for Nimbus to store the blockchain and validator data of the Consensus layer. Move the validator_keys
directory into this folder. Then set the owner of this directory to the Nimbus so that this user can read and write to the directory.
If there are no errors, create a systemd configuration file for the Nimbus Beacon Node service to run in the background.
Paste the configuration parameters below into the file:
Once you're done, save with Ctrl+O
and Enter
, then exit with Ctrl+X
. Understand and review your configuration summary below, and amend if needed.
Nimbus Beacon Node configuration summary:
--network
: Run the beacon node service on the ETH Holesky testnet
--data-path
: Specify the directory for Nimbus to store data related to the consensus client
--web3-url
: URL to connect to the execution layer client
--jwt-secret
: File path to locate the JWT secret we generated earlier
--payload-builder
: Enable external payload builder
--payload-builder-url
: URL to connect to external payload builder (MEV-boost)
--tcp-port / --udp-port:
Sets the port for peer-to-peer communication. Defaults to 9000.
--rest
: Enable the REST API endpoint for validator and DVT clients to connect to this consensus client
--rest-address
: Sets the IP address to connect to the REST API of the consensus client that will be used by the DVT clients. Use the internal IP address of your device here (check by running ip a
) - e.g. 192.168.x.x
. Defaults to 127.0.0.1
otherwise
--rest-port
: Port to connect to the REST API endpoint
--metrics
: Enable monitoring of consensus client metrics
--metrics-port
: Port to connect to the metrics endpoint
--local-block-value-boost
: How much more (in %) must the value of externally-built blocks be in order to outsource block building vs building blocks locally. Set to 0
to be indifferent. Default =10
For Nimbus, you have to first run the checkpoint sync process separately before firing up the consensus client with the above configurations.
Verify the Block Root
and State Root
with your output
Expected output:
First we have to change the owner of the nimbus beacon data directory to the nimbus
user.
Reload systemd to register the changes made, start the Nimbus Consensus Client service, and check its status to make sure its running.
Expected output: The output should say Nimbus Beacon Node is “active (running)”. Press CTRL-C to exit and Nimbus Beacon Node will continue to run. It should take just a few minutes for Nimbus to sync on the Holesky.
Use the following command to check the logs of Nimbus Consensus Client’s syncing process. Watch out for any warnings or errors.
Expected output:
Press Ctrl+C
to exit monitoring.
Note: You will see some warnings around "Block failed to load unexpectedly"
if your execution client has yet to fully sync. The following output is expected initially and should go away after a few hours.
If the Nimbus Consensus Client service is running smoothly, we can now enable it to fire up automatically when rebooting the system.
Checkpoint sync URL list:
Go to on your browser and search for the slot number (slot
)
Releases:
Documentation:
Discord: