Chain ID: pylons-mainnet-1 | Current Node Version: v1.1.4
All Live Peers for Pylons
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.
2fbafcad63eefd2053135061682042e803f8cf0b@65.109.109.225:26656,71b2ccc335a2ed88854444d23c2f2e2fd343c7e9@65.109.52.156:9656,af4cc3ce89e51b9d99c46496daec60e2cdf2143b@65.108.126.49:27656,ec0091eb96865721725a6668f65e1c7782149c35@65.21.45.173:16556,dea08fa4f608d954890631468fdf4de3ba1ae103@138.201.225.104:47256,738ce404cc42b7640b3d2b4a5f587d5e7ab63634@65.109.88.251:38656,62efd4f06d3890f658a622b598426d745fa3af86@5.9.147.22:26606,ac927f72c6fd74268202650d123f718ddf4a499c@142.132.158.9:19456,f11c7596800a52b9585e54d7fc372c5b5f367c49@65.109.93.152:29656,5eb57ba49c53dd6269e5afa9062265b0227886e5@144.76.45.59:26156
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=af4cc3ce89e51b9d99c46496daec60e2cdf2143b@65.108.126.49:27656,f11c7596800a52b9585e54d7fc372c5b5f367c49@65.109.93.152:29656,dea08fa4f608d954890631468fdf4de3ba1ae103@138.201.225.104:47256,738ce404cc42b7640b3d2b4a5f587d5e7ab63634@65.109.88.251:38656,5eb57ba49c53dd6269e5afa9062265b0227886e5@144.76.45.59:26156
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.pylonsd/config/config.toml
sudo systemctl restart pylonsd
sudo journalctl -fu pylonsd --no-hostname -o cat
Our peer for Pylons
When you state-sync, you might also consider adding [NODERS]TEAM state-sync peer to your persistent_peers setting in config.toml.
ae94eb20e73c0ad93dbb980338eb313320c56194@pylons-rpc.noders.services:16556