Chain ID: devnet-1 | Current Node Version: v1.1.0
All Live Peers for Story
Here is a list of 8 active peers as observed by [NODERS]TEAM in real-time. Add them to your config.toml if you have trouble finding peers.
1851180d526f7a4cfc5e391263869ba9d24bb8e7@35.207.39.228:26656,1db54c7d607e1445800ef3028a74acbff7dba00b@57.128.184.4:26656,36ca8b119bf5851cd1e37060af914cb07dec24f9@34.79.40.193:26656,59201fade719c1e4ded98b2304e555377d2b4cef@116.202.217.20:28656,87b71521e7d611db9dd590a0f114a05c7b408ee3@34.79.244.160:26656,521f141a1ea0e9f23029428b41d3d3cc41862feb@34.76.242.140:26656,9d34ab3819aa8baa75589f99138318acfa0045f5@95.217.119.251:30900,761536d68d7222c46091283ff8f4485b23161a2c@49.12.122.53:27656
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=521f141a1ea0e9f23029428b41d3d3cc41862feb@34.76.242.140:26656,59201fade719c1e4ded98b2304e555377d2b4cef@116.202.217.20:28656,1db54c7d607e1445800ef3028a74acbff7dba00b@57.128.184.4:26656,36ca8b119bf5851cd1e37060af914cb07dec24f9@34.79.40.193:26656,1851180d526f7a4cfc5e391263869ba9d24bb8e7@35.207.39.228:26656
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.story/config/config.toml
sudo systemctl restart story
sudo journalctl -fu story --no-hostname -o cat
Our peer for Story
When you state-sync, you might also consider adding [NODERS]TEAM state-sync peer to your persistent_peers setting in config.toml.
@story-t-rpc.noders.services: