Lodestar
Overview
Official Links
Documentation
1. Initial configuration
Create a service user for the consensus service, create data directory and assign ownership.
sudo adduser --system --no-create-home --group consensus
sudo mkdir -p /var/lib/lodestar
sudo chown -R consensus:consensus /var/lib/lodestarInstall dependencies.
sudo apt-get install gcc g++ make git curl ccze -y2. Install Binaries
Building from source code can offer better compatibility and is more aligned with the spirit of FOSS (free open source software).
3. Setup and configure systemd
Create a systemd unit file to define your consensus.service configuration.
Paste the following configuration into the file.
Replace
<0x_CHANGE_THIS_TO_MY_ETH_FEE_RECIPIENT_ADDRESS>with your own Ethereum address that you control. Tips are sent to this address and are immediately spendable.Not staking? If you only want a full node, delete the whole line beginning with
To exit and save, press Ctrl + X, then Y, then Enter.
Run the following to enable auto-start at boot time.
Finally, start your consensus layer client and check it's status.
Press Ctrl + C to exit the status.
4. Helpful consensus client commands
Example of Synced Lodestar Consensus Client Logs
Common reasons to reset the database can include:
To reduce disk space usage
To recover from a corrupted database due to power outage or hardware failure
To upgrade to a new storage format
With checkpoint sync enabled, time to re-sync the consensus client should take only a minute or two.
Now that your consensus client is configured and started, you have a full node.
Proceed to the next step on setting up your validator client, which turns a full node into a staking node.