Live node directory
Every node this network knows how to reach: the seeds shipped with the client, plus the
providers an access point currently reports as healthy. It is read straight from
/seeds.json — the same directory a bootstrapping node uses, not a marketing list.
The live directory could not be fetched, so nothing is listed here. This does not mean
the network is down — nodes still ship with the compiled-in seed list and will keep dialing it.
Try reloading, or read the raw JSON at /seeds.json.
Network at a glance
Directory metadata, as published by the network itself.
Nodes
A seed is a fixed entry point shipped with the client. A backbone node is a
long-lived public full node. A provider is a GPU serving AI jobs right now. Only entries with a
/p2p/<peer-id> multiaddr are dialable; endpoints without one are shown for reference.
| Role | Multiaddr | Peer ID | Source | Endpoint / address |
|---|---|---|---|---|
| Loading the directory… | ||||
Peer IDs are shortened to 8…6 characters; hover for the full value, or use the copy button. Multiaddrs are copied in full.
How to join
- Download the client for Linux, macOS, or Windows from the download page.
- Start it with one of the installers — mining begins by default and the node serves AI work when a job arrives. Steps are in run a node.
- Become dialable. Open the P2P port (default
30333, or whateverlisten_addryou set) so other peers can reach you; a node behind NAT is still a client, but it cannot be listed as a seed. - Get discovered. A healthy provider registered with an access point is published in this directory automatically, usually within one TTL (60 s).
Machine-readable
Point a node at the directory and it bootstraps from the whole list — seeds plus live providers — instead of a hardcoded address:
GPN_BOOTNODES_URL=https://gpncoin.ai/seeds.json gpn-nodeEndpoints (all CORS-enabled, cached for 60 s):
GET https://gpncoin.ai/seeds.json # metadata + multiaddrs + per-node detail
GET https://gpncoin.ai/bootnodes.txt # one dialable multiaddr per lineThe wire format is stable: multiaddrs is
always present and is all a simple client needs. nodes adds roles, peer IDs, and
provider endpoints; source says whether the AP answered
(static+ap) or only the compiled-in seeds were available
(static-fallback).
This is the public testnet. Nodes come and go, the chain can be reset, and testnet tokens have no monetary value. Directory freshness is bounded by the 60 s TTL — a node that just went offline can appear for up to a minute.