Understand how the CPUNK ecosystem runs on Cellframe CF20: active nodes, block heights, synchronization status, and other indicators that describe the state of the post-quantum infrastructure.
Network metrics are the observability layer for CPUNK’s post-quantum infrastructure. They help validators, delegators, and builders understand how the system behaves.
CPUNK depends on the underlying Cellframe CF20 network for identity, messaging, and token operations. To keep this environment secure and reliable, participants need visibility into how the network is performing.
Network statistics provide insight into liveness (is the network moving forward?), participation (how many nodes are active?), and health (are there forks, stalls, or connectivity issues?). When these indicators are tracked over time, they also help detect regressions after software upgrades or configuration changes.
The goal is not to overwhelm with numbers, but to expose a clear, honest picture of how the CPUNK ecosystem is doing at the infrastructure layer.
Different roles care about different metrics. These are the core indicators CPUNK focuses on when describing network health.
Block height and the rate at which new blocks appear are the simplest signals of network liveness. Large gaps or sudden stops can indicate incidents, forks, or connectivity problems that need attention.
The number of active masternodes or validators shows how much infrastructure is currently online and participating in consensus. A diverse set of operators reduces central points of failure.
A node can be online but not fully synced. Network stats highlight whether the majority of nodes are in agreement about the current chain tip and whether there are significant lagging nodes.
Propagation delays and peer connectivity influence how fast blocks and transactions spread across the network. Healthy networks minimize unnecessary latency while maintaining decentralization.
Over time, network stats can be enriched with geographic and operator information (where available) to monitor how decentralization evolves and ensure no single jurisdiction dominates.
For CPUNK, network health also includes staying aligned with the post-quantum threat model – making sure nodes are running up-to-date implementations of PQ-safe cryptography and protocol versions.
CPUNK aims to keep monitoring lightweight and privacy-preserving, using public, protocol-level information rather than invasive tracking.
Most network statistics come from one or more observer nodes connected to the same network as validators and wallets.
Where possible, metrics are derived from public, on-chain or protocol-level information, avoiding any data that would compromise user privacy or identity.
Network stats are exposed via dashboards such as CPUNK.CLUB and can be integrated into other tools and explorers.
This page is designed to connect to the same data sources, giving a consistent view of the network across cpunk.io and cpunk.club.
Validators, delegators, builders, and researchers all look at the network from slightly different angles – but they rely on the same underlying metrics.
The layout is ready to consume data from your existing JSON or RPC proxies
(/stats/net-stats.json, PHP endpoints, or direct Cellframe RPC).
Replace the placeholder values in the metrics panel with real statistics and this
page becomes a simple, public window into CPUNK’s infrastructure health.
For deeper exploration of validators and delegation, connect this with Delegation and Delegation Stats.