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