Chain ID: seda-1 | Current Node Version: v0.1.1
All Live Peers for Seda
Here is a list of 47 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
2cb792992a85a590359a6edfdca62bbd555d8585@89.58.41.234:26656,31f54fbcf445a9d9286426be59a17a811dd63f84@18.133.231.208:26656,9eb343010b328fab1f955f5e18f62032a23afa50@152.53.19.64:20656,f9ad00c49bf013e1f36707d87702073a52875c8b@65.109.18.169:25856,50684663fa58a24ed4ffae50d01f4526347abd97@49.13.169.174:26656,61cd71c112c195cae1aba2d30c5164d844b27079@93.159.130.37:36656,490ad5578e440efc926c92954870b7dd75a22843@213.246.39.138:21656,d81b682c58bcff94d142db931046234e99f878ca@162.19.169.74:46656,55b28aabeb24938db6119fa5580159b1b6e5fc80@144.76.114.34:25856,fcd700cc304953f52c90613609adc1d7d3ded768@95.216.117.238:26656,90252c9b8c0946cd68f1aa544fa523569fdb97b3@65.109.115.172:25856,d60b25fe2c523893a739b81dca99b2ecf571c8d8@65.108.101.109:25856,17b84b25216277e3214fd2e8970987fbe6004c49@135.148.103.164:26656,b348ba8e728a3fe123a27b0ee072d59e41f0aef8@37.187.149.56:17356,54ad1b2d8f97897f63238955530aadd3349f0605@185.182.194.239:26656,3b620287baf6fb56342557955ff39a5d71f9fd71@38.146.3.231:25856,32aaa561eb4c2cf54f18b08e14b3c756eee44183@221.148.45.106:28656,08c6fad06270ee717a3c50826bf0fa61f270266d@134.122.69.213:32248,5703dfa831d6829320bd9a7afe0f83ea7ec195cd@51.159.177.53:26656,a8cc0ef1a8b85317b571cc0b265aaeb3b0960081@185.246.87.73:26656,0cf0cd8c66888ebdc5f4f3bde4c31fce9533a473@176.9.157.142:25856,3a9b2d046e57d9e4194a4a2e552651bc8b732ded@46.4.29.231:3000,f482ca37b63e53c06bb267cbb0f594d9560234bb@88.99.68.249:25856,f66b9d59461685d4687e272b03dd0f1b07036421@189.1.170.86:56176,734b08fa75d0a750922bb012afced1ab9e2ffcb4@145.239.254.154:20656,8d887e7007696439a955e839d786532af746f697@94.130.13.186:25856,4a75daf47b56decb10c858ca9524033e1a47e8ff@64.185.227.122:25856,892777ce97dfc69c54dc1540a7ccfbf09ff2ff12@208.91.107.232:25856,02cadb2a0ab4599ce311da557509461e56702e17@95.217.210.43:26656,02ed3aef42c9a6cb32fbea3fe3d117ab3ef8a920@64.185.226.202:25856,1a87a68c8a03ecbf6d6e65d4ce780d72d5498c0f@65.108.71.137:25856,1b022b410d739ada3667388dd5f900f376880a9d@51.159.221.46:26656,f41ceae74c11c1fa2b218f58ad54bfe5db8d882e@65.109.61.79:25856,47a3c94d0bb74476b9befa551a9b4fd67269229a@64.38.176.74:26656,d9bfa29e0cf9c4ce0cc9c26d98e5d97228f93b0b@37.27.61.38:17356,b28a14707a33ab7a069f36473f73e8e8e4436b1f@65.108.204.209:25856,1a00b931ca6ad065ebb59b4047188c35c7247e5e@37.252.186.105:3000,25ac079b642670134b3a2d5f513ffd046b1ed362@37.120.160.252:26656,2e9ecccdeff4dc0e5e26cc9adf7ed6f46cc66833@65.108.234.137:25856,341ddc11a05a5f7368057a4baf69b5b82fc906e5@65.21.65.254:1580,e4959e99d11bf036f8eec6397522a97389dd0b55@162.55.28.185:10156,09ba537d6563018b97c502979c3478df4decf426@152.53.32.140:6656,06610987be86b94fb108a6319c0408c53d4b921e@51.210.223.72:25856,737559f20420bb90c174485ecd76292512746c4a@65.109.108.47:25856,ebc272824924ea1a27ea3183dd0b9ba713494f83@193.34.212.188:26866,bb4d039e33227bc036f686eeb2cd9ce687a4ee4c@64.185.227.242:25856,20e1000e88125698264454a884812746c2eb4807@159.69.1.6: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=d60b25fe2c523893a739b81dca99b2ecf571c8d8@65.108.101.109:25856,31f54fbcf445a9d9286426be59a17a811dd63f84@18.133.231.208:26656,20e1000e88125698264454a884812746c2eb4807@159.69.1.6:25856,0cf0cd8c66888ebdc5f4f3bde4c31fce9533a473@176.9.157.142:25856,341ddc11a05a5f7368057a4baf69b5b82fc906e5@65.21.65.254:1580
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:36656