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:25156Community seed nodes
If you would like to add additional seeds, here are some provided by the community:
e7b6016ce5663a69ba71a982072315545eb0d5f6@seed.xpla.delightlabs.io:26656,20e1000e88125698264454a884812746c2eb4807@seeds.lavenderfive.com:20157Quickly update your seed nodes
Update your seeds in config.tomlseeds="b85358e035343a3b15e77e1102857dcdaf70053b@seeds.bluestake.net:25156,e7b6016ce5663a69ba71a982072315545eb0d5f6@seed.xpla.delightlabs.io:26656,20e1000e88125698264454a884812746c2eb4807@seeds.lavenderfive.com:20157" sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.xpla/config/config.toml# Restart your nodesystemctl restart xpla.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:
...Quickly update your peers# Update your persistent_peers in config.tomlpeers="..." sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.xpla/config/config.toml# Restart your nodesystemctl restart xpla.service
BlueStake contribute to XPLA by offering several tools and services,
tailored for users, developers, and node operators.