Skip to main content

System Diagrams

Diagram 1: ZKN Ecosystem Stack

Text Transcription

The ZKN Ecosystem Stack is structured as five interconnected layers, each building upon the one beneath:

Sub Layer — Hardware & DePIN: Physical infrastructure including NØDEs (network operation devices), zerOS (hardened Linux-based OS), edge devices, and hardware security modules. These provide tamper-resistant execution, hardware-backed identity, and physical decentralization to host the mix network nodes.

Layer 0 — Mix Networks: Katzenpost Echomix provides the privacy-preserving mix-net transport layer, using post-quantum cryptographic primitives for metadata-private communication across the network.

Layer 1 — Settlement Layer: Aztec serves as the settlement layer for aggregated ZKProofs, providing finality and cryptographic verification. Ethereum hosts the $ZKN ERC20 token, which bridges into the system.

Layer 2 — zkAppChain: The ZK Application Chain provides a privacy-preserving blockchain layer that hosts core protocol infrastructure: the Token Bridge (connecting $ZKN ERC20 to $ZKN-ZK native token), zkDEX (for private token exchange), DAO Governance (decentralized protocol management), and ZK-dApps (privacy-preserving applications).

Layer 3 — Applications & Services: End-user applications built on zkAppChain: WalletShield for private blockchain RPC, Secure Messaging for metadata-private communication, ZK-Firewall for privacy-preserving access control, ZK Trust Registry for cryptographic identity, and ZK Provenance for supply chain verification.

Data/Value Flow: The stack operates bidirectionally. Infrastructure supports mix networks, which provide private transport for settlement. Settlement proves for the appchain, which powers applications. Revenue flows back from applications to the protocol layers, creating a self-sustaining cycle.


Diagram 2: Token Architecture Overview

Text Transcription

This diagram shows the two-way bridge architecture connecting Ethereum's $ZKN ERC20 token to the ZKN Privacy Layer's native $ZKN-ZK token:

Deposit Path (Left to Right): Users deposit $ZKN ERC20 tokens on Ethereum into the Token Bridge contract, which locks them. The bridge then mints an equivalent amount of $ZKN-ZK native tokens within the ZKN Privacy Layer. These native tokens power the zkAppChain, which in turn incentivizes Mix Network operations.

Utility Path (Middle to Right): The $ZKN-ZK token within the Privacy Layer enables four key outcomes: private network access (paying for mix-net services), private operations (transaction privacy within the zkAppChain), staking rewards (earning yield for network participation), and governance (voting on protocol decisions).

Withdrawal Path (Right to Left): Users can burn their $ZKN-ZK tokens, which triggers the bridge to unlock the corresponding $ZKN ERC20 tokens on Ethereum, completing the round-trip.


Diagram 3: Regenerative-DePIN Flywheel

Text Transcription

The Regenerative-DePIN Flywheel is ZKNetwork's dual-engine economic model that interlocks DePIN revenue with regenerative tokenomics:

Revenue Layer (Input): Users and enterprises pay for network services using stablecoins, providing predictable, non-volatile revenue. These payments form the energy input to the system.

Regenerative Tokenomics Router: Revenue splits across four strategic pools:

  • Yield Vault — Pays stablecoin rewards to node operators and stakers, decoupling operator sustainability from token volatility
  • ZKN Treasury — Automatically converts revenue to ZKN tokens and locks them, creating structural buy pressure without dilution
  • Grants & ReFi Pool — Funds ecosystem builders who commit to revenue recursion (sending future income back to the protocol)
  • Liquidity Reserve — Provides market stability and protocol-owned liquidity, pairing with ZKN for deep, DAO-owned liquidity

Convergence Layer (The Bridge): Each pool creates distinct feedback effects:

  • Treasury locks reduce circulating supply
  • Stable rewards reduce sell pressure from operators
  • Grants create new utility that attracts more users
  • Reserves enable stable payments and risk coverage

Token Layer (Output): The ZKN token serves multiple functions: liquidity provision, staking/verification, incentive rewards, governance voting, network access, and regeneration. Each function feeds back to attract more participants and revenue, creating a self-reinforcing cycle.


Diagram 4: Coordination Framework

Text Transcription

The ZKN Token Coordination Framework illustrates how protocol revenue is distributed and how it regenerates:

Revenue Flow: Stablecoin revenue from network services enters the Regenerative Router, which distributes it across four pools by percentage: Treasury (40%), Yield Vault (30%), Grants Pool (20%), and Liquidity Reserve (10%).

Output Generation: Each pool produces specific ecosystem outputs. The Treasury funds protocol growth and node operator rewards. The Yield Vault provides staker yields and additional operator rewards. The Grants Pool funds builder initiatives. The Liquidity Reserve ensures market stability.

Regeneration Feedback: Each output triggers a regeneration cycle: more node operators lead to better service quality, which attracts more users generating more revenue. More builders create more utility, expanding the ecosystem. Treasury growth drives token value appreciation. These feedback loops create a self-sustaining system where today's outputs become tomorrow's inputs, enabling continuous compound growth without external extraction.