Validators

Validator information for the QSDM public pilot network (pre-mainnet). Today the chain is produced by a single block producer during recovery, so the peer count below may read 0. Independent validators cannot join consensus yet; they are on the roadmap. The node id and status below are read live from /api/v1/status.

Network stack is on the internal audit checklist. Five network checklist rows pin DHT, libp2p, discovery, and bootstrap peers. This is a self-maintained checklist, not an independent audit. See audit.html?category=network.

Official · Public · Live

Project validator — `api.qsdm.tech`

The block producer of the public pilot network. It is operated by the QSDM project.

libp2p node id

<node_id>

Read live from /api/v1/status (field node_id) and refreshed every 30 s. It changes when the node's libp2p key rotates. Without JavaScript, run curl -s https://api.qsdm.tech/api/v1/status | jq -r .node_id. Peer-to-peer access to the producer is closed for now. Full nodes follow the chain over HTTPS: see Run a full node.

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

Testing a validator

You can build and run the validator software today to follow along on a test or private network. Bootstrap peers go into the [network] bootstrap_peers block of your validator config (or the BOOTSTRAP_PEERS environment variable). libp2p discovers the rest of the mesh after the first handshake.

TOML

[network]
port            = 4001
bootstrap_peers = [
  "<bootstrap multiaddr>",
]

Environment variable (Docker / systemd)

BOOTSTRAP_PEERS=<bootstrap multiaddr>

Full procedure: see the Operator guide or the Validator quickstart.

Why only one validator?

The public network is a pre-mainnet pilot run by a single block producer during recovery. Signed consensus has been enforced since block 827,000 (every vote and message must carry a valid ML-DSA signature). A standby producer and, later, block production by miners are the next steps on the roadmap; there is no validator set to join. The network status is explained on Network status. To check the chain yourself, run a full node: Run a full node.

Operator guide Validator quickstart Attestation transparency Back to landing