s no indication that the signature belongs to the owner.

      There is no indication that the signature belongs to the owner.

 

 

Primary key fingerprint: 15E6 6D94 1F69 7E28 F493 81F4 2641 6DC3 F306 74B0

“`

If the checksum is verified, extract the files and move them into (/usr/local/bin) directory.

Then clean up the working directory.

“`

> tar xvf lighthouse-v5.2.1-x86_64-unknown-linux-gnu.tar.gz

> sudo cp lighthouse /usr/local/bin

> rm -r lighthouse lighthouse-v5.2.1-x86_64-unknown-linux-gnu.tar.gz.asc lighthouse-v5.2.1-x86_64-unknown-linux-gnu.tar.gz

“`

Create an account called `lighthouse` without server access for lighthouse(the consensus layer software) to run as a background service. This type of user account will not have root access so it restricts potential attackers to only the lighthouse service in the unlikely event that attackers manage to infiltrate via a compromised client update.

> sudo useradd –no-create-home –shell /bin/false lighthouse

 

 

Create a directory for lighthouse (the consensus layer software) to store the blockchain data of the consensus layer. Then set the owner of this directory to lighthouse (the user account) so that this user can read and write to the directory.

> sudo mkdir -p /var/lib/lighthouse

> sudo chown -R lighthouse:lighthouse /var/lib/lighthouse

 

 

Create a systemd configuration file for the lighthouse service to run in the background.

 

 

> sudo vi /etc/systemd/system/lighthouse.service

 

 

Paste the configuration parameters below into the file:

 

 

“`

[Unit]

Description=Lighthouse Consensus Client (Holesky)

After=network.target

Wants=network.target

 

 

[Service]

User=lighthouse

Group=lighthouse

Type=simple

Restart=always

RestartSec=5

ExecStart=/usr/local/bin/lighthouse

  –chain holesky

  –datadir=/var/lib/lighthouse

  –log.file.directory=/var/lib/lighthouse/logs

  –authrpc.jwtsecret=/var/lib/jwtsecret/jwt.hex

  –full

  –port 30303

  –http

  –http.api eth,web3,net,txpool,debug,trace

  –http.addr

  –http.port 8547

  –ws

  –ws.addr

  –ws.port 8548

  –metrics 127.0.0.1:6060

  

[Install]

WantedBy=default.target

“`

Once you’re done, save with ESC → ENTER → :wq → ENTER

Understand and review your configuration summary and amend if needed.

lighthouse configuration summary:

 

 

Start lighthouse

Reload the systemd daemon to register the changes made, start lighthouse and check its status to make sure its running.

> sudo systemctl daemon-reload

> sudo systemctl start lighthouse.service

> sudo systemctl status lighthouse.service

Expected output: The output should say lighthouse is “active (running)”. Press CTRL+C to exit and lighthouse will continue to run. It should take around 6 hours for lighthouse to sync on the Holesky testnet.

 

 

Use the following command to check the logs of lighthouse’s syncing process. Watch out for any warnings or errors.

> sudo apt install ccze -y

> sudo journalctl -fu lighthouse -o cat | ccze -A

 

 

Expected output

Press CTRL+C to exit.

See here(https://lighthouse-book.sigmaprime.io/advanced-topics/logs.html) for more details on how to interpret and understand lighthouse journalctl logs

 

 

If the lighthouse service is running smoothly, we can now enable it to fire up automatically when rebooting our node.

> sudo systemctl enable lighthouse.service

 

 

Expected output:

> Created symlink /etc/systemd/system/default.target.wants/lighthouse.service → /etc/systemd/system/lighthouse.service.