CPH Core

Sovereign SHA-256 Network

Independent chain operations, public explorer access, and bootstrap-era network visibility.

Network

Public network topology, discovery layer, and operational visibility.

This page summarizes the public-facing surfaces currently used by the live CPH network: DNS seeds, bootstrap nodes, explorer endpoints, and the operational discipline around launch readiness.

Public Surface

Live Bootstrap Topology

DNS Seeds
5
Bootstrap Nodes
5
Explorer
cphcore.org

Network Model

How the current public layer is organized

These are the current building blocks of the live network surface.

Bootstrap Topology

The public network currently runs with multiple DNS seeds, bootstrap nodes, and a live explorer to support opening-stage operations.

Operational Visibility

Status APIs, health probes, mempool inspection, and public block views are all surfaced from the same public-facing stack.

Launch Discipline

CPH uses staged opening, handoff approval, signer return tracking, and live readiness gates instead of treating launch as a one-shot event.

DNS Seeds

Current discovery endpoints

dnsseed1.cphcore.org dnsseed2.cphcore.org dnsseed-us.cphcore.org dnsseed-third.cphcore.org dnsseed-uk.cphcore.org

Bootstrap Nodes

Current public node endpoints

seed1.cphcore.org:39333 seed2.cphcore.org:39333 seed-us.cphcore.org:39333 seed-third.cphcore.org:39333 seed-uk.cphcore.org:39333

DNS Seeds

5

Public discovery hosts

Bootstrap Nodes

5

Public node endpoints

Operators

3

Independent operator groups

Regions

3

Infrastructure regions

Explorer Endpoints

  • Overview: cphcore.org
  • Status: cphcore.org/api/status
  • Health: cphcore.org/healthz
  • Mempool: cphcore.org/mempool

Operational Notes

  • Mainnet P2P is exposed on port 39333.
  • RPC is kept local-only on port 39332.
  • Explorer and readiness visibility are intentionally public during bootstrap operations.

Why This Matters

The network page should explain trust, not just list machines.

CPH is trying to make the public bootstrap layer visible instead of opaque.

Open Participation

Anyone should be able to inspect the chain, run a node, join the bootstrap layer, and review releases without needing private infrastructure.

Verifiable Distribution

Release candidates, manifests, detached signatures, and trusted signer packets are part of the intended public trust model.

Independent Infrastructure

CPH is designed to rely on its own DNS seeds, bootstrap nodes, explorer surface, and operator topology rather than a hidden private stack.

Bitcoin-like Discipline

The project stays close to Bitcoin-style monetary rules while building a staged launch process that makes the earliest network state easier to audit.