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:23356Community seed nodes
If you would like to add additional seeds, here are some provided by the community:
aebb8431609cb126a977592446f5de252d8b7fa1@104.236.201.138:26656,b6beabfb9309330944f44a1686742c2751748b83@5.161.47.163:26656Quickly update your seed nodes
Update your seeds in config.tomlseeds="b85358e035343a3b15e77e1102857dcdaf70053b@seeds.bluestake.net:23356,aebb8431609cb126a977592446f5de252d8b7fa1@104.236.201.138:26656,b6beabfb9309330944f44a1686742c2751748b83@5.161.47.163:26656" sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.passage/config/config.toml# Restart your nodesystemctl restart passage.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
Passage Peering...Quickly update your peers# Update your persistent_peers in config.tomlpeers="..." sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.passage/config/config.toml# Restart your nodesystemctl restart passage.service
BlueStake contribute to Passage by offering several tools and services,
tailored for users, developers, and node operators.
