A common practice is to use a seed to connect to the network.
You can add our seed node in seeds in your config.toml file:
b85358e035343a3b15e77e1102857dcdaf70053b@seeds.bluestake.net:23856Community seed nodes
If you would like to add additional seeds, here are some provided by the community:
cb91a11588d66cfd9c01f99541df4978a08e0e39@seedv1.main.stridenet.co:26656,babc3f3f7804933265ec9c40ad94f4da8e9e0017@seed.rhinostake.com:12256Quickly update your seed nodes
Update your seeds in config.tomlseeds="b85358e035343a3b15e77e1102857dcdaf70053b@seeds.bluestake.net:23856,cb91a11588d66cfd9c01f99541df4978a08e0e39@seedv1.main.stridenet.co:26656,babc3f3f7804933265ec9c40ad94f4da8e9e0017@seed.rhinostake.com:12256" sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.stride/config/config.toml# Restart your nodesystemctl restart stride.service
Here is a list of active peers as observed by our nodes
If you have trouble finding peers, you can add these 5 random peers as persistent_peers in your config.toml file:
BlueStake
Stride Peering...Quickly update your peers# Update your persistent_peers in config.tomlpeers="..." sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.stride/config/config.toml# Restart your nodesystemctl restart stride.service
BlueStake contribute to Stride by offering several tools and services,
tailored for users, developers, and node operators.
