Chain ID: mantra-dukong-1 | Current Node Version: v4.0.0
All Live Peers for Mantra
Here is a list of 12 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
4fb0ff78585d8d4692eddce458714b6cf40eeb66@45.14.135.200:26656,7d01a4c350d8b0bc57fd85584ff8689b767878be@152.53.110.139:27656,593824b79d719e764832efca9e5137f29d1c49ca@88.218.226.175:26656,9c23fe95a222f437ca80fe2192328fa9e812e6b8@34.18.92.69:26656,da54ab1be9e88bdfa2845269ef24f975bb1c90c1@34.130.170.97:26656,e726816f42831689eab9378d5d577f1d06d25716@169.155.171.102:36656,1f402acf2e4ad59aca187e84c64ef973b2b3c8bb@35.220.173.152:26656,0bfc4c0e18f09c50f26a7ac38b1541c3024edb87@34.96.208.200:26656,d93d460d030779b93cb2cf874f64af37a263e4e0@34.96.191.10:26656,0b9d7d7daefacc1903cecef392c6f10528839fa6@34.92.64.233:26656,e1b058e5cfa2b836ddaa496b10911da62dcf182e@134.65.192.193:36656,7e061edecef73a700b699c785f61a44ca981ff7f@34.150.103.79: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=e726816f42831689eab9378d5d577f1d06d25716@169.155.171.102:36656,9c23fe95a222f437ca80fe2192328fa9e812e6b8@34.18.92.69:26656,d93d460d030779b93cb2cf874f64af37a263e4e0@34.96.191.10:26656,1f402acf2e4ad59aca187e84c64ef973b2b3c8bb@35.220.173.152:26656,da54ab1be9e88bdfa2845269ef24f975bb1c90c1@34.130.170.97:26656
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.mantrachaind/config/config.toml
sudo systemctl restart mantrachaind
sudo journalctl -fu mantrachaind --no-hostname -o cat
Our peer for Mantra
When you state-sync, you might also consider adding [NODERS]TEAM state-sync peer to your persistent_peers setting in config.toml.
8ac264aa8af65b4363f98fcab3fbc58c81b2ca90@mantra-t-rpc.noders.services:25156