Chain ID: seda-1 | Current Node Version: v0.1.8-hotfix.3
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.
b348ba8e728a3fe123a27b0ee072d59e41f0aef8@37.187.149.56:17356,1b022b410d739ada3667388dd5f900f376880a9d@51.159.221.46:26656,b28a14707a33ab7a069f36473f73e8e8e4436b1f@65.108.204.209:25856,71620b329b80632f1b6d996c53d08c26fe8863f9@217.170.204.54:16656,58c919e7b89b8c5b5a3024f5e7cec07d2e3b28d3@78.47.163.48:26656,cc7413feb11a1c92838a27836d421cd6c0f2c87c@144.76.74.73:25856,02cadb2a0ab4599ce311da557509461e56702e17@95.217.210.43:26656,55b28aabeb24938db6119fa5580159b1b6e5fc80@144.76.114.34:25856,fa4806e7a75a24a9c7c65cca3293798de36b7ca7@135.125.188.14:26656,0cf0cd8c66888ebdc5f4f3bde4c31fce9533a473@176.9.157.142:25856
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=b28a14707a33ab7a069f36473f73e8e8e4436b1f@65.108.204.209:25856,0cf0cd8c66888ebdc5f4f3bde4c31fce9533a473@176.9.157.142:25856,58c919e7b89b8c5b5a3024f5e7cec07d2e3b28d3@78.47.163.48:26656,b348ba8e728a3fe123a27b0ee072d59e41f0aef8@37.187.149.56:17356,71620b329b80632f1b6d996c53d08c26fe8863f9@217.170.204.54:16656
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.
c9100af84ba8c9dbeb0c1c49837620bf447bf55c@seda-rpc.noders.services:25856