MAINNET • SECURITY
Security model
Phoncoin’s goal is to keep the protocol simple to verify and hard to fake at scale.
Heartbeat validity
- Signed payload (Ed25519) tied to the miner public key.
- Rate limits to reduce spam and keep fair participation (HB rate configured for global scale).
- Server-side verification: signature, format, timestamps, and protocol fields (v4.1).
Anti‑Sybil direction
- Device fingerprint + device_info v4 (privacy‑conscious, to resist emulator farms).
- Optional attestation hooks (e.g., platform integrity checks) to raise the cost of fake devices.
- One phone ≈ one miner is enforced by protocol rules + node policy.
Chain safety rules
Phoncoin’s goal is to keep the protocol simple to verify and hard to fake at scale.
Heartbeat validity
- Signed payload (Ed25519) tied to the miner public key.
- Rate limits to reduce spam and keep fair participation (HB rate configured for global scale).
- Server-side verification: signature, format, timestamps, and protocol fields (v4.1).
Anti‑Sybil direction
- Device fingerprint + device_info v4 (privacy‑conscious, to resist emulator farms).
- Optional attestation hooks (e.g., platform integrity checks) to raise the cost of fake devices.
- One phone ≈ one miner is enforced by protocol rules + node policy.
Chain safety rules
Nodes reject chains that do not match the network’s genesis + consensus rules. This is the foundation for keeping the network consistent across gateways and future core nodes.
Recommendation: publish (and pin) your genesis hash, protocol version (v4.1), and the official endpoints.
What changes over time
Some parameters (like rate limits or networking defaults) can evolve without breaking the genesis. Any consensus change must be treated as a protocol upgrade (versioned + communicated clearly).
- Wallet/UI settings change freely (no consensus impact).
- Node policy knobs (anti-spam, rate limits) can be updated with caution.
- Consensus rules require a planned upgrade path.