Chain ID: seda-1-testnet | Current Node Version: v0.1.7
All Live Peers for Seda
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.
e5af5f5c2650fb13da1c661460e72186face79be@95.217.35.179:25856,1027c297a88a37b67906c85099116b8fe0136b0e@135.181.178.120:17656,8cfdbb242658a42a108b64bbdff73216df9a8e7d@51.195.61.9:25856,1fef9721db7cb37ace237d1a2b1271c319bb1c0c@94.130.164.82:25856,d967e409d7353994e43fd5c13191f4c99673d297@5.9.116.21:25856,d84359abdb55f6f7b1caf59c80855955f44bf32b@94.130.35.35:13656,35d1fec5d70b51e90dfa8b5a2368691ebc78b82a@57.128.202.24:26656,a6a6f924bf8a88e2d2d6ace0031e6844951712a9@93.189.30.113:26656,50d00c212df119eb19ab976b40cf3cd149ad50ab@185.183.35.185:26656,3da2316011d98adc484d1582ccee563edda6fe8f@2a01: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=d84359abdb55f6f7b1caf59c80855955f44bf32b@94.130.35.35:13656,8cfdbb242658a42a108b64bbdff73216df9a8e7d@51.195.61.9:25856,1fef9721db7cb37ace237d1a2b1271c319bb1c0c@94.130.164.82:25856,d967e409d7353994e43fd5c13191f4c99673d297@5.9.116.21:25856,a6a6f924bf8a88e2d2d6ace0031e6844951712a9@93.189.30.113:26656
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.sedad/config/config.toml
sudo systemctl restart sedad
sudo journalctl -fu sedad --no-hostname -o cat
Our peer for Seda
When you state-sync, you might also consider adding [NODERS]TEAM state-sync peer to your persistent_peers setting in config.toml.
d9e79bc821f1fcf7b5924dfc1c2a8ffec91737fe@seda-t-rpc.noders.services:25856