Source PeeringWe provide seeds and live-peers to allow node operators to efficiently connect a node to the network
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:
[email protected]:23256Community seed nodes
If you would like to add additional seeds, here are some provided by the community:
7347b05f140e4ed5d3da7b26c754a486dc1d2ecd@source-mainnet-seed.itrocket.net:32656,ebc272824924ea1a27ea3183dd0b9ba713494f83@source-mainnet-seed.autostake.com:27446Quickly update your seed nodes
Update your seeds in config.tomlseeds="[email protected]:23256,7347b05f140e4ed5d3da7b26c754a486dc1d2ecd@source-mainnet-seed.itrocket.net:32656,ebc272824924ea1a27ea3183dd0b9ba713494f83@source-mainnet-seed.autostake.com:27446" sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.source/config/config.toml# Restart your nodesystemctl restart source.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...Quickly update your peers# Update your persistent_peers in config.tomlpeers="..." sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.source/config/config.toml# Restart your nodesystemctl restart source.service
BlueStake contribute to Source by offering several tools and services,
tailored for users, developers, and node operators.
