Infrastructure-Level Privacy

Privacy Architecture

Privacy is treated as a transport-layer problem, not just a ledger problem. Every validator is simultaneously a consensus participant, Mixnode, and bandwidth broker.

The Metadata Surveillance Gap

Most "privacy coins" focus solely on the ledger. They ignore that an adversary monitoring the network layer can de-anonymize users through traffic analysis—correlating IP addresses with transaction timing.

The Problem

If you broadcast a ZK-transaction from your home IP, observers can see: User IP A sent packet X at time T → Validator B received packet X at T+δ → Block contained transaction of size X. You're de-anonymized regardless of on-chain privacy.

Po8 closes this gap by mandating that every validator is a Mixnode. Privacy scales linearly with network security.

Sphinx Packets & Cover Traffic

Po8 integrates a Nym/Loopix-style Mixnet directly into the node software.

Constant Size Packets

All packets are padded to exactly 32 KB. An observer cannot distinguish between a block header, transaction, chat message, or control signal.

Bitwise Unlinkability

Packets undergo cryptographic transformation at each hop. The bitstream entering a node is completely uncorrelated to the bitstream leaving it.

Loop Cover Traffic

Nodes emit packets at a constant rate following a Poisson distribution. Real data replaces dummy packets—no traffic burst betrays your action.

Stratified Topology

Valid paths traverse exactly one node from each layer (Entry → L1 → L2 → L3 → Exit). Prevents Sybil routes through attacker-controlled nodes.

Decentralized VPN

For low-latency traffic where Mixnet delays are unacceptable, Po8 nodes function as dVPN relays.

AmneziaWG

Standard WireGuard is easily detected by Deep Packet Inspection. AmneziaWG obfuscates handshake headers, making VPN traffic look like random noise or generic HTTPS. Po8 nodes provide uncensored access even in hostile jurisdictions.

Dandelion++ Propagation

Before transactions enter the Mixnet, Dandelion++ creates a "stem phase" passing data to one peer at a time. Only the "fluff phase" is visible to observers—originating far from the actual source.

Zero-Knowledge Architecture

While the Mixnet protects IP addresses, the ledger protects the transaction graph using Halo2 with KZG Commitments.

Recursive SNARKs

Block proposers aggregate thousands of transaction proofs (π_tx) into a single Block Proof (π_block). Mobile light clients verify the entire blockchain history with a single proof check.

View Key Hierarchy

Po8 introduces compliance-optional privacy. Every account possesses a hierarchy of keys for granular disclosure.

sk
Spending Key

Master key for authorizing transfers. Never shared.

fvk
Full Viewing Key

Decrypts entire transaction history. Share with auditors or tax accountants.

ivk
Incoming Viewing Key

Decrypts only incoming funds. Useful for POS terminals verifying payment receipt.

tvk
Transaction View Key

Decrypts a single specific transaction. Prove "I sent 50 USDC to Bob" without revealing other history.

Compliance Patterns

zkLedger Solvency Proofs

Exchanges maintain internal ledgers in shielded pools while publishing proofs that liabilities don't exceed reserves. Regulators verify without seeing individual balances.

Verifiable Credentials

DeFi pools require ZK-proof of valid KYC credentials. Users prove they possess credentials without revealing identity on-chain.

Per-Transaction Disclosure

Transaction View Keys let users prove specific payments to arbitrators without exposing other financial history.

Siniel Delegation

Mobile wallets outsource heavy ZK proof generation to miners via MPC. Workers compute on encrypted data—never see the witness.

Bandwidth Market

Validators are incentivized to relay traffic through a Proof of Relay market.

Orchid Model

Probabilistic nanopayments for high-volume traffic. Users attach "lottery tickets" to packets—small probability of large reward, expected value equals bandwidth cost. Millions of payments with minimal on-chain load.

Sentinel Model

Deterministic billing for enterprise users. Nodes track bytes per session and submit signed "Bandwidth Usage Proofs" to claim from escrow contracts. Reliable SLAs for institutional requirements.

Beyond raw throughput, nodes earn additional Po8 for maintaining Mixnet cover traffic via Proof of Mixing. Orchid-style lottery tickets keep per-packet payments off-chain while the expected value converges to the true bandwidth cost.