Shibarium peers

Current Heimdall persistent_peers and Bor static-nodes, copy-paste ready. Peer sets rotate and the old ones get retired, so a node left on a stale list drops to peercount=0 and stops syncing even though nothing else is wrong with it.

← back to the dashboard

Updated2026-09-15· Shibarium mainnet (chain 109)2 hosts

Full rotation, not an addition. The previous peer set is being retired, so a node left on the old list will drop to peercount=0 and stop syncing. Source: Shib core team, posted by Vinayak Sharma.

1 · Heimdall

Edit <path-to-heimdall>/config/config.toml and replace the persistent_peers line.

persistent_peers =

0a1c867a107ac6d1a479f1b5bef6b155c9b85992@62.238.108.108:26656,01a8ae557c6f2b26572c31692f0b6425fe8bf7ac@138.199.152.233:26656

2 · Bor

Edit <path-to-bor>/config.toml, and under [p2p] replace static-nodes.

static-nodes =

["enode://05e8db3aa99dae4d967588f33b0b6284b3ecd1c32479278bfdf1b1cbf292dac2b70af768ddc9f2e732f1407b8a451ae6de2303276fe07b61359e06d174e64ea8@138.199.152.233:30303","enode://e045ab30b8b9dcaa493007f299743c1d434ee340278ce26d514e61b25757c55f75aeb38257a6ffd424a654dad97e91c19f9243aa2893384275f88565d8c8bded@62.238.108.108:30303"]

3 · Restart

shell

sudo systemctl daemon-reload
sudo systemctl restart heimdalld
sudo systemctl restart bor

Before you restart

Both services run on the same machines, so check they are reachable from your network first. If these fail from a host with working outbound access, it is your firewall or security group rather than the peers, and editing the config will not help on its own. Port 30303 needs both TCP and UDP.

reachability check

for hp in 138.199.152.233:30303 62.238.108.108:30303 \
          138.199.152.233:26656 62.238.108.108:26656; do
  timeout 5 bash -c "</dev/tcp/${hp/:/ }" 2>/dev/null \
    && echo "OK   $hp" || echo "BLOCKED $hp"
done

After restarting, watch peercount in the Bor logs settle above zero. That is the number that tells you it worked.