Persistence Persistence Peering

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

Seed node [email protected]:28556

Persistence 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]:28556
Community seed nodes

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

eaa76966cad27a9807b7d8b9a62c9b2ca4924581@tenderseed.ccvalidators.com:26003,ebc272824924ea1a27ea3183dd0b9ba713494f83@persistence-mainnet-seed.autostake.com:26896
Quickly update your seed nodes
Update your seeds in config.toml
seeds="[email protected]:28556,eaa76966cad27a9807b7d8b9a62c9b2ca4924581@tenderseed.ccvalidators.com:26003,ebc272824924ea1a27ea3183dd0b9ba713494f83@persistence-mainnet-seed.autostake.com:26896"
sed -i -e "s/^seeds *=.*/seeds = \"$seeds\"/" $HOME/.persistenceCore/config/config.toml

# Restart your node
systemctl restart persistence.service

Persistence 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/.persistenceCore/config/config.toml

# Restart your node
systemctl restart persistence.service