Chain ID: lava-testnet-2 | Current Node Version: v4.2.0
All Live Peers for Lava
Here is a list of 46 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
a247ed99ed10cb4ffdd87b66949bb2a53e16a148@65.109.24.208:26656,0ce92e8c09a4636eb153e95df9ef7acbeac3f309@91.237.141.121:26656,0314d53cc790860fb51f36ac656a19789800ce5c@176.103.222.20:26656,2701fea28d683f58ce4a4b863653b05bac831e22@65.21.88.86:56656,d1730b774b7c1d52dd9f6ae874a56de958aa147e@139.45.205.60:23656,f6f689fffc5a17e6ffbe29f6ffa72540e18cf6cd@109.199.112.157:14456,106b0d4b7c7d5ddd62e1f12fcc90e05d1916120f@91.237.141.76:26656,b6d154d1a3321bf6affc6e6a5b908982cfba4eee@213.239.192.18:14456,fb9b0822df6083824d39669cbce7eb6258969c73@37.142.120.101:28656,b74d2d6b000164e722619dc9dfc35d5fed06598a@65.21.224.11:26756,04c9e0bc0614d4b1cc2859251cfdb13b0f97aaed@167.235.4.41:26656,f23540653fbc0612f5f0b4603dbcfeb3465304ed@167.235.14.83:656,d81c127bca11925d4121336d9ce151ebc6e6ac9b@65.108.79.241:36656,75868366ca374c7dfe1ba4e71ea1fbd5652bd294@176.9.9.174:15656,9f70cf5961f9115b199de3b5e7d4301698c65481@185.252.235.73:14456,4edb45861057bc221d2037dbff33699cd76d5dce@217.22.153.181:32520,eed45ce3c41d4c34af4c7e7bff2a956dcc39ca23@49.12.168.49:26656,cb584c66da7bdf364f7b27e47fe442707bd82226@5.9.152.154:26656,51aeaa2c757989f720c904023c2dbedfc720f75e@23.88.5.169:27656,2f7bc05ef20db904d27faa9ae1521a161dfb6b05@65.109.115.104:56656,f3109a03b077fe2e643e464edf97926d50e2b631@91.207.54.33:26656,d5519e378247dfb61dfe90652d1fe3e2b3005a5b@65.109.68.190:14456,6ba3b6ec03839afffa64c83e18ff80a681f4968d@65.108.194.40:21756,23c0b44dc4d506f75d567988456747a3b7e55be8@15.204.198.203:26656,0e0e01f932a124c45f7f8600e38dba445b5f5dc4@65.108.226.183:19956,c1e101e83ad85b8005e2f2682fc6ae244184c264@37.27.103.27:26656,2491565354bd3bdf75e9d80a0f703a17ff65118d@185.119.116.230:26656,d60f8d9f8e5916c3ad7d7dd2d251f274b4efc310@193.122.137.30:26656,cb0f768ad9061b3bd7305f69c6ccae7475d014fc@176.9.84.13:26656,46b231908ca44dccd3f9c7846714ae055d642b04@212.106.124.243:36656,191a95db7d3ac5d7d2cb92038c161fc26d073e28@88.198.5.77:35656,3693ea5a8a9c0590440a7d6c9a98a022ce3b2455@65.109.92.79:20656,13a9209a4d08803a3becac57de8eb02dd51f8f41@65.109.23.114:19956,2902ac98aa0b2767c0542f0c793b3b0e6b4a786f@188.40.116.108:14456,fcee45066f6d309389a76d78b19eb3ebe4516948@27.74.10.215:23656,99327e5cf0f31ac3bb1ca8e39cc9f17c823b7ec1@65.109.25.104:26656,a41df893d263c1300e8b84b07e9f230aeeb42a37@65.108.234.115:20756,80c6fe6d657dda8cc1e0691634bd68361b3b8b4f@94.130.164.82:19956,40046fe63bdaa9efde27707b0d3de0bf84fedf80@86.111.48.158:26656,60a144ffed618f4e99466da8fbe7b799b009b9e7@65.108.70.119:38666,5e72db2072e451d2936c50bee39ff192237479ff@89.149.216.9:26656,111eb709143ec92fdad9d819d4a454e4f0bc79c0@15.235.204.150:21156,eb7832932626c1c636d16e0beb49e0e4498fbd5e@65.108.231.124:20656,e388b6b6f5675b8169fcc37b2d59490050f74565@135.181.2.49:33656,e118df821d2bf2be04cd34f5802c4bb44714a1f3@86.111.48.155:26656,6e6692985ecc151e6af161b733a3a5bfd254c5f1@80.232.244.29:23356
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=46b231908ca44dccd3f9c7846714ae055d642b04@212.106.124.243:36656,cb0f768ad9061b3bd7305f69c6ccae7475d014fc@176.9.84.13:26656,2902ac98aa0b2767c0542f0c793b3b0e6b4a786f@188.40.116.108:14456,2491565354bd3bdf75e9d80a0f703a17ff65118d@185.119.116.230:26656,3693ea5a8a9c0590440a7d6c9a98a022ce3b2455@65.109.92.79:20656
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:19656