Protocol mechanics
PoN replaces hardware-heavy mining with verifiable connectivity and challenge responses. The stack below is conceptual; parameters ship with official specs and testnet releases.
From lightweight device signals to verifier-checked proofs and reward scoring—this is the PoN participation loop in one place.
Flow
Five beats repeat on a cadence tuned for battery, data, and honest network behavior.
The client opens a session and advertises lightweight reachability signals.
Uptime, latency windows, and diversity hints form the participation fingerprint.
The protocol issues randomized network checks with strict timing budgets.
Independent verifiers cross-check proofs against expected network patterns.
Scores roll into the reward engine and wallet-facing balances when rules pass.
Depth
Each layer has its own abstract diagram—transparent PNGs sit on neutral cards so focus stays on structure.
Each device contributes measurable, low-cost network signals instead of hash power.
Challenges keep participation honest by forcing timely, non-replayable responses.
Verifiers validate that submissions are fresh, consistent, and expensive to fake at scale.
Economics
Scores combine positive participation signals and subtract penalties when abuse is detected.
Exact weighting, caps, and decay curves are versioned in the whitepaper and on-chain or off-chain policy modules as the network matures.
Safety
Lightweight mining only works if Sybil and emulator farms cannot trivially farm rewards.
Systems
A readable slice of how components line up in product language—implementation details evolve with releases.
Layer 1
Mobile device
Layer 2
PoN client
Layer 3
Challenge plane
Layer 4
Verifier mesh
Layer 5
Reward engine
Layer 6
Wallet
Labels are product-facing; wire names and deployment topology follow release documentation.
Whitepaper and API docs carry versioned detail; this page is the guided tour of the mechanics.
