MAINNET • ARCHITECTURE

Network architecture

Designed for a smartphone-first miner base, with clear separation between miners and nodes.

1) Phone miners (light clients)

Generate and sign PoP heartbeats (Ed25519) from the wallet/miner app.
Attach device metadata (device_info v4) and anti-Sybil signals (fingerprint).
Send to a public endpoint (Gateway) over HTTPS.

Phones do not keep the full chain. They act as light clients and participate by submitting signed work.

2) Gateway nodes (public API)

Expose stable HTTPS endpoints: API, explorer, metrics.
Rate-limit and protect the network edge (WAF, reverse proxy, caching).
Forward valid heartbeats/transactions to Core nodes.

Gateways are optimized for bandwidth and request handling.

3) Core nodes (consensus + storage)

Validate heartbeats and blocks, enforce the consensus rules.
Maintain the canonical chain and mempools.
Serve blocks/state to gateways and other cores.

Cores are optimized for correctness and data integrity.

4) Explorer (read-only UI)

Human-readable view of blocks, addresses, holders, mempools and network stats.
Can run on the same machine as a gateway or separately.

Most blockchains keep explorers in English by default — PHONCOIN does the same for consistency.

Scaling path (what happens at 30k → millions → billions of miners)

More gateways: add regional gateways close to users (latency + capacity).
More cores: add additional core nodes for redundancy and faster propagation.
Indexers: offload rich queries (top holders, history) to dedicated index services.
Optional aggregators/pools: if a single block cannot pay every miner directly, aggregation layers can distribute rewards fairly without changing phone UX.