Improving Validator Attestation Effectiveness

Learn about attestation effectiveness from Attestant.io

👨‍👩‍👧‍👧 Strategy: Increase beacon chain peer count

This change will result in increased bandwidth and memory usage. Tweak and tailor appropriately for your hardware.

Kudos to Rémy Roy for this strat.

Edit your beacon-chain.service unit file (except for Teku).

sudo nano /etc/systemd/system/beacon-chain.service

Add the following flag to increase peers on the ExecStart line.

Lighthouse

--target-peers 100
# Example
# lighthouse bn --target-peers 100 --staking --metrics --network mainnet

Nimbus

--max-peers=100
# Example
# /usr/bin/nimbus_beacon_node --network=mainnet --max-peers=100

Teku

# Edit teku.yaml
sudo nano /etc/teku/teku.yaml

# add the following line to teku.yaml and save the file
p2p-peer-upper-bound: 100

Prysm

--p2p-max-peers=100
# Example
# prysm.sh beacon-chain --mainnet --p2p-max-peers=100 --http-web3provider=http://127.0.0.1:8545 --accept-terms-of-use 

Lodestar

--network.maxPeers 100
# Example
# ./lodestar beacon --network.maxPeers 100 --network mainnet

Reload the updated unit file and restart the beacon-chain process to complete this change.

sudo systemctl daemon-reload
sudo systemctl restart beacon-chain

⚙️ Strategy: Perform updates or reboots during the longest attestation gap

Learn how to at this quick guide.