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:24556Community seed nodes
If you would like to add additional seeds, here are some provided by the community:
ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:13156,c30dacf15e97a30b78792c7fa817fd2ef529b820@comdex.seed.stavr.tech:2026Quickly update your seed nodes
Update your seeds in config.tomlseeds="b85358e035343a3b15e77e1102857dcdaf70053b@seeds.bluestake.net:24556,ade4d8bc8cbe014af6ebdf3cb7b1e9ad36f412c0@seeds.polkachu.com:13156,c30dacf15e97a30b78792c7fa817fd2ef529b820@comdex.seed.stavr.tech:2026" sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.comdex/config/config.toml# Restart your nodesystemctl restart comdex.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
Comdex Peering...Quickly update your peers# Update your persistent_peers in config.tomlpeers="..." sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.comdex/config/config.toml# Restart your nodesystemctl restart comdex.service
BlueStake contribute to Comdex by offering several tools and services,
tailored for users, developers, and node operators.
