PHONCOIN
Phonchain • PoP Secure v4.1
Bootstrap
MAINNET • REFERENCE

PHONCOIN Bible

A canonical technical bible for PHONCHAIN: network identity, consensus, security model, tokenomics, and public endpoints. Everything here is meant to be verifiable.

Phoncoin does for phones what Bitcoin did for CPUs in 2009 — turning everyday devices into participants.

1 · Identity

PHONCOIN (PHC)

  • Native asset of PHONCHAIN
  • Mobile-first monetary network
  • Secured by real smartphones
  • Fair distribution — no privileges

PHONCHAIN

  • Public blockchain designed for mobile
  • Consensus: Proof-of-Phone (PoP Secure v4.1)
  • Crypto: Ed25519 + SHA-256
  • Open endpoints: API / gateway / explorer

2 · Consensus Proof-of-Phone Secure v4.1

Core idea

  • 1 real phone = 1 participant
  • No heavy Proof-of-Work
  • No Proof-of-Stake based on wealth
  • Security comes from cryptography + hardware uniqueness + protocol checks

What a phone does

  • Generates an Ed25519 keypair
  • Sends signed heartbeats (activity proofs)
  • Solves a light PoW puzzle (difficulty target)
  • Attaches a hashed device fingerprint + device_info v4

What a node verifies

  • Ed25519 signature validity
  • Timestamp rules (anti-replay)
  • Difficulty target (light PoW)
  • Fingerprint binding & reuse detection
  • Security profile (emulator/root flags, trust score, rate limits)

3 · Security PoP-Secure v4.1 anti-fraud

Anti-emulator

  • Detects Android Emulator / Genymotion / suspicious environments
  • Immediate rejection when confirmed

Anti-root & trust score

  • Root detection signals
  • Trust score (0–100) computed on-device
  • Node policy rejects devices below the minimum threshold

Anti-cloning

  • Hashed device fingerprint (privacy-preserving)
  • Binding: 1 fingerprint → 1 address
  • Reuse is flagged and can be restricted

Anti-replay & rate limiting

  • Old/reused timestamps rejected
  • Heartbeats too close rejected (anti-spam)
  • Per-device and per-pubkey limits

Attestation ready

  • Device schema v4 includes a field reserved for Play Integrity / attestation verdicts
  • Protocol is designed to accept stronger attestations later without breaking compatibility

4 · Data model

Heartbeat (PoP-S4.1)

  • pubkey (Ed25519)
  • timestamp
  • nonce (light PoW)
  • signature
  • hashed device_fingerprint
  • device_info v4: OS, hardware, security flags, latency, trust score

Block

  • index, timestamp
  • prev_hash, hash
  • validated heartbeats
  • block reward
  • participating miner addresses

5 · Canonical network parameters

  • Target block time: 300 seconds (5 minutes)
  • Consensus: Proof-of-Phone (PoP Secure v4.1)
  • Algorithms: Ed25519, SHA-256
  • Ticker: PHC
  • Genesis block timestamp: 2025-10-09 08:53:20 UTCc098fa5e985edd56634af262975b771f0dadc607494d6875cb725f1006611658

6 · Tokenomics PHC

Total supply

  • Hard cap: 21,000,000 PHC

Block reward & halving

  • Initial reward: 25 PHC per block
  • Halving: every 420,000 blocks
  • Target block time: 5 minutes

Halving schedule (example)

PhaseBlock heightReward
Phase 10 – 419,99925 PHC
Phase 2420,000 – 839,99912.5 PHC
Phase 3840,000 – 1,259,9996.25 PHC

Fair distribution

  • No premine
  • No ICO
  • No reserved team allocation
  • 100% minted through real participation

7 · Wallet PHONCOIN Android

Principles

  • Non-custodial
  • Keys stored on-device only
  • No central server required

Security model (important)

  • The wallet never stores IPs
  • The wallet trusts only the canonical genesis_hash
  • Any endpoint with a mismatching genesis is rejected

8 · Public network architecture

Domains

  • phoncoin.org — official website, whitepaper, documentation
  • phonchain.org — public nodes: API, gateway/seed, explorer, bootstrap

Official endpoints

  • Bootstrap: https://bootstrap.phonchain.org/nodes.json
  • API: https://api.phonchain.org
  • Gateway/Seed: https://seed2.phonchain.org
  • Explorer: https://explorer.phonchain.org/explorer

9 · Bootstrap file nodes.json

Purpose

  • Provides an official list of public endpoints (HTTPS)
  • Allows wallets to evolve without app updates (priority/order can change)
  • Must include: network, mode, min_version, genesis_hash, nodes[] (url/role/region/priority)
  • Wallets should only select endpoints whose genesis_hash matches the canonical chain

10 · Principles

  • One phone = one voice
  • Security comes from real participation
  • Energy is precious → near-idle usage
  • No hidden privileges
  • Everything is cryptographically verifiable

11 · Current status

ComponentStatus
ConsensusFinal
Genesis block timestamp: 2025-10-09 08:53:20 UTCFrozen (canonical)
Public nodesOnline (production)
WalletSecured
WebsiteOnline
BootstrapCanonical