Chain ID: pylons-mainnet-1 | Current Node Version: v1.1.4
All Live Peers for Pylons
Here is a list of 17 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
d6bf1201b9ee8e9d1704ac43915e21756e7229b4@65.109.70.100:26686,32804e1b2bd86d97257ca688bb77fac1e69c9132@176.9.158.219:41556,3c3dd9b334bcc9b6edaee345ff1b62be65b803e0@148.113.162.234:26656,2fbafcad63eefd2053135061682042e803f8cf0b@65.109.109.225:26656,030e6a01aef8913bcee33b957e9204986203bc81@135.125.4.73:46656,99910196d78d5c6e4b658223109d721edcb9ee6b@138.201.85.176:26686,9b657e9137d07a9dfec36f89cd432eb44efa39c0@185.180.222.190:13656,88842d9e1b2e95cdd95227ae6d952b0fa6290737@84.16.241.18:29656,dcd20401417eabeec46297be26c93e2e0b3f029d@5.161.229.9:26656,62efd4f06d3890f658a622b598426d745fa3af86@5.9.147.22:26606,ec0091eb96865721725a6668f65e1c7782149c35@65.21.45.173:16556,0f606f3fa1290d86e514a22a2b6a96ef4b58c70d@195.201.202.39:26666,19bd42c383fc38920ff6c82a351a8a6284199466@141.94.160.53:11156,252a2a9ddb4f30632e274447b4a37606c340742f@65.109.229.209:26656,dea08fa4f608d954890631468fdf4de3ba1ae103@138.201.225.104:47256,0e83fcc53916d97249f0cd0212c1713914897656@49.12.123.87:56656,93db1f716b4a956fb8627d857500a4c5af876df4@65.109.18.169:16556
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=0f606f3fa1290d86e514a22a2b6a96ef4b58c70d@195.201.202.39:26666,2fbafcad63eefd2053135061682042e803f8cf0b@65.109.109.225:26656,62efd4f06d3890f658a622b598426d745fa3af86@5.9.147.22:26606,93db1f716b4a956fb8627d857500a4c5af876df4@65.109.18.169:16556,dea08fa4f608d954890631468fdf4de3ba1ae103@138.201.225.104:47256
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:23656