Sentinel Peering

We provide seeds and live-peers to allow node operators to efficiently connect a node to the network

Seed node [email protected]:26556

Sentinel Seeds nodes

A common practice is to use a seed to connect to the network.

BlueStake seed node

You can add our seed node in seeds in your config.toml file:

[email protected]:26556
Community seed nodes

If you would like to add additional seeds, here are some provided by the community:

cb91a11588d66cfd9c01f99541df4978a08e0e39@seedv1.main.stridenet.co:26656,[email protected]:12256
Quickly update your seed nodes
Update your seeds in config.toml
seeds="[email protected]:26556,cb91a11588d66cfd9c01f99541df4978a08e0e39@seedv1.main.stridenet.co:26656,[email protected]:12256"
sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.sentinelhub/config/config.toml

# Restart your node
systemctl restart sentinel.service

Sentinel Live peers

Here is a list of active peers as observed by our nodes

Live peers

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.toml
peers="..."
sed -i -e "s/^persistent_peers *=.*/persistent_peers = \"$peers\"/" $HOME/.sentinelhub/config/config.toml

# Restart your node
systemctl restart sentinel.service