Reth
Last updated
Last updated
We first need to create a JSON Web Token (JWT) that will allow the execution layer software (Reth) and the consensus layer software to talk to each other.
Run the following commands one line at a time to create a folder on the server to store the JWT file and generate the JWT file:
We will be pointing the configuration files of the execution and consensus clients to this JWT file later.
the latest version of Reth and it's digital signature (.asc) file. for verifying the checksum to ensure that the downloaded file has not been tampered with.
Run the checksum verification process.
Verify the release signing key (--recv-keys
) in the first command above .
Expected output: Verify output of the checksum verification
If checksum is verified, extract the files and move them into the (/usr/local/bin)
directory for neatness and best practice. Then, clean up the duplicated copies.
Create an account (reth
) without server access for Reth to run as a background service. This type of user account will not have root access so it restricts potential attackers to only the Reth service in the unlikely event that they manage to infiltrate via a compromised client update.
Create a directory for Reth to store the blockchain data of the execution layer. Then set the owner of this directory to reth
so that this user can read and write to the directory.
Create a systemd configuration file for the Reth 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.
Reth configuration summary:
--chain
: Run the on the Holesky testnet
--datadir
: The directory for Reth to store the blockchain data of the execution layer
--log.file.directory
: The path to put log files in
--authrpc.jwtsecret
: The directory pointing to the JWT secret we generated earlier
--full:
Run full node.
--port
: Sets the port used for peer-to-peer communication. Defaults to 30303.
--http
: Enables the HTTP-RPC service on http and websocket. This is so that DVT clients such as the Diva service can connect to your execution client
--http.api
: Rpc modules to be configured for the HTTP server.
--http.addr
: Sets the IP address to connect to the JSON RPC service. 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
--http.port
: Sets the port to connect to the HTTP-RPC service that will be used by the DVT services. You may choose any unused port number but remember to allow incoming connections into your chosen port in your firewall (ufw
) rules. Defaults to 8545.
--ws
: ws=Websocket. Enable the WS-RPC server. This is so that DVT clients can connect to your execution client.
--ws.addr
: Websocket server address to listen on. Used by DVT clients.
--ws.port
: Websocket server port to listen on. Used by DVT clients.
--metrics
: Enable monitoring metrics on the Reth service.
Reload the systemd daemon to register the changes made, start Reth, and check its status to make sure its running.
Expected output: The output should say Reth is “active (running)”. Press CTRL-C to exit and Reth will continue to run. It should take around 6 hours for Reth to sync on the Holesky testnet.
Use the following command to check the logs of Reth’s syncing process. Watch out for any warnings or errors.
Expected output:
Press CTRL-C
to exit.
If the Reth service is running smoothly, we can now enable it to fire up automatically when rebooting the system.
Expected output:
For more details on interpreting the Reth journalctl logs, head .
Releases:
Documentation:
Telegram: