Chain ID: lava-testnet-2 | Current Node Version: v5.3.0
All Live Peers for Lava
Here is a list of 11 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
fb9b0822df6083824d39669cbce7eb6258969c73@37.142.120.101:28656,6ba3b6ec03839afffa64c83e18ff80a681f4968d@65.108.194.40:21756,13a9209a4d08803a3becac57de8eb02dd51f8f41@65.109.23.114:19956,d1730b774b7c1d52dd9f6ae874a56de958aa147e@139.45.205.60:23656,c19965fe8a1ea3391d61d09cf589bca0781d29fd@162.19.217.52:26656,2491565354bd3bdf75e9d80a0f703a17ff65118d@185.119.116.230:26656,2701fea28d683f58ce4a4b863653b05bac831e22@65.21.88.86:56656,c0165f15a0489f8619e1f7cc0484c5ecab55b48a@65.109.93.124:19956,7ee8434b107b32f764f42bcc82b6fbfc25011d8f@65.108.75.107:28656,436bc22d65a3a189294f5d30d037a6668a0e0ec4@65.109.83.40:19956,98fe8b7cbc376484f0c7f01517f55bc4e206c8d7@65.109.106.6:26656
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=6ba3b6ec03839afffa64c83e18ff80a681f4968d@65.108.194.40:21756,c19965fe8a1ea3391d61d09cf589bca0781d29fd@162.19.217.52:26656,436bc22d65a3a189294f5d30d037a6668a0e0ec4@65.109.83.40:19956,fb9b0822df6083824d39669cbce7eb6258969c73@37.142.120.101:28656,2491565354bd3bdf75e9d80a0f703a17ff65118d@185.119.116.230:26656
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.
47a09710163c64a37b4b0454113ea5b6bb0b80b5@lava-t-rpc.noders.services:19956