Chain ID: lava-mainnet-1 | Current Node Version: v5.2.0
All Live Peers for Lava
Here is a list of 10 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
f6a239ae943247ec5f879866b44648b64a85a654@168.119.89.91:41004,ab7a906235396f2a5ddfce73375430c7ac5e0097@23.227.223.1:26656,773769f9d17eae39735dab7789faa7f7a9a31cdc@144.76.29.190:26656,a3c10d83569abf6c58b874e6e99b0f8bffe0c8f6@91.134.37.34:26676,be2c7d4f9b7c81b191ec2fa54adaf69f17eb739d@142.132.199.236:21656,6a9a65d92b4820a5d198dd95743aa3059d0d3d4c@165.154.224.92:26656,159a27880fe8704f44c307b18404061d46b77083@162.19.95.240:15656,a02a0bc247973fdf134fe6799ba799ab055ecb4b@65.108.207.225:60656,c302de174dd0e1891c87a88e760878020164bf5a@69.10.52.2:26656,dca62b1537a2a52a365328b5503b0ab9239f8bd3@95.216.74.45:14456
Here is a script for you to update persistent_peers setting in config.toml. Stale peers can cause node inefficiency over time, so the script below selects a few random live peers.
PEERS=6a9a65d92b4820a5d198dd95743aa3059d0d3d4c@165.154.224.92:26656,be2c7d4f9b7c81b191ec2fa54adaf69f17eb739d@142.132.199.236:21656,c302de174dd0e1891c87a88e760878020164bf5a@69.10.52.2:26656,ab7a906235396f2a5ddfce73375430c7ac5e0097@23.227.223.1:26656,a3c10d83569abf6c58b874e6e99b0f8bffe0c8f6@91.134.37.34:26676
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.lava/config/config.toml
sudo systemctl restart lavad
sudo journalctl -fu lavad --no-hostname -o cat
Our peer for Lava
When you state-sync, you might also consider adding [NODERS]TEAM state-sync peer to your persistent_peers setting in config.toml.
2b0daf7ab2976dc5bf2702c0fd3fffad6f62d5e2@lava-rpc.noders.services:19956