Validators & bootstrap peers

This page publishes the canonical bootstrap multiaddr for the QSDM Phase 4 testnet. A new validator uses this value once, at startup, to discover the libp2p mesh. After the handshake your node gossips directly with every other peer — api.qsdm.tech is a bootstrap, not a hub.

The validator network is itself audited. DHT Sybil resistance, libp2p P2P stack, peer discovery, and the bootstrap protocol you wire into bootstrap_peers below are pinned by 5 rows in the network category of the public audit checklist — all passing. Operational infra (deploy hygiene, systemd, log rotation, RFC 9116 disclosure surface) is pinned by 6 rows under infrastructure. See audit.html?category=network for the live view.

Canonical · Testnet · Live

Reference validator — `api.qsdm.tech`

The genesis validator for the Phase 4 testnet. Operated by the QSDM project.

libp2p bootstrap multiaddr

/ip4/206.189.132.232/tcp/4001/p2p/12D3KooWRH4MGiaRYMZEr9LvdxYrpePT5LPbNqLTMGukD32yhkZ8

This is the value you paste into bootstrap_peers in your qsdm.toml / qsdm.yaml, or into the BOOTSTRAP_PEERS environment variable for Docker deployments. The peer-id rotates when the node's libp2p private key rotates. The values on this page refresh live from /api/v1/status every 30 s in a browser; the static HTML is also re-synced on every redeploy so curl / non-JS crawlers see the current value too.

Peers: — Chain tip: — Uptime: — Version: — refreshed —

Public endpoints

REST / JSON-RPC

https://api.qsdm.tech/api/v1/*

Trust summary

.../trust/attestations/summary

Trust recent

.../trust/attestations/recent

Mining work

.../mining/work — point your miner here with --validator=https://api.qsdm.tech

Live status

.../status — returns current node-id, chain tip, peer count

Prometheus

.../api/metrics/prometheus

Dashboard

https://dashboard.qsdm.tech/

Using this value

Drop the multiaddr above into the [network] bootstrap_peers block of your validator config, then start the service. You do not need to list every peer — libp2p discovers the rest via PEX after the initial handshake.

TOML

[network]
port            = 4001
bootstrap_peers = [
  "/ip4/206.189.132.232/tcp/4001/p2p/12D3KooWRH4MGiaRYMZEr9LvdxYrpePT5LPbNqLTMGukD32yhkZ8",
]

Environment variable (Docker / systemd)

BOOTSTRAP_PEERS=/ip4/206.189.132.232/tcp/4001/p2p/12D3KooWRH4MGiaRYMZEr9LvdxYrpePT5LPbNqLTMGukD32yhkZ8

CLI (`bring-up-validator.sh`)

sudo bash QSDM/deploy/bring-up-validator.sh \
  --bootstrap /ip4/206.189.132.232/tcp/4001/p2p/12D3KooWRH4MGiaRYMZEr9LvdxYrpePT5LPbNqLTMGukD32yhkZ8

Full procedure: see the Operator Guide (end-to-end) or VALIDATOR_QUICKSTART.md (reference).

Why only one bootstrap peer?

Phase 4 testnet is early — api.qsdm.tech is currently the genesis validator. As more operators stand up validators, this page will list multiple bootstrap peers (any single one is enough to join the mesh). The protocol does not assign privileged status to the project's VPS; you are welcome to stand up your own validator and become an alternate bootstrap peer. To have your validator listed here, open an issue on github.com/blackbeardONE/QSDM/issues with your public multiaddr and a brief ops description (uptime target, contact email).

If the multiaddr looks stale

The libp2p peer-id (the 12D3Koo… suffix) rotates whenever the node's node-p2p-id.json is regenerated. If your validator logs show failed to dial bootstrap peer errors or connected_peers=0 that never resolves, pull the current node-id live from the status endpoint and try again:

curl -s https://api.qsdm.tech/api/v1/status | jq -r .node_id

The IP (206.189.132.232) and port (4001/tcp) do not change within a Phase 4 release cycle.

Operator guide (end-to-end) VALIDATOR_QUICKSTART.md Attestation transparency Back to landing