System Overview

ZKGate is built on a three-layer architecture, where each layer plays a specific role in privacy execution, proof generation, and multi-chain interoperability. Together, they form a complete privacy-first Layer-2 that enables private state, private liquidity, and private settlement across multiple blockchains.

---

1️. ZK Pools Layer — Private Execution & State Layer

- Role:

This is the core state layer where all private user actions, commitments, balances, and liquidity are stored and updated.

- Detailed Description:

The ZK Pools Layer consists of isolated privacy domains called ZK Pools. Each pool represents an independent execution environment for a specific project or module.

A ZK Pool manages:

• A dedicated Merkle state tree

• User commitments & nullifiers

• Private balances and token notes

• Private liquidity positions

• Supported private actions (transfer, swap, stake, lend, vote…)

• Circuit configuration for each action type

- Core Responsibilities:

• Maintains private state for users and projects

• Ensures correctness via ZK proofs

• Prevents double spending using nullifiers

• Supports multi-asset and multi-module execution

• Handles pooled liquidity routing inside the L2

- Examples of Pools:

• Pool #1: Private Wallet Pool

• Pool #2: Private DEX Pool

• Pool #3: Private Launchpad Pool

• Pool #4: Private Staking Pool

• Pool #5: Private NFT/Game Economy Pool

Each pool is isolated, meaning activity in one pool cannot be correlated with activity in another.

---

2️. Sequencer + Prover Network — Proof Generation & Batch Settlement Layer

- Role:

This layer is the execution engine of the L2, responsible for:

• ordering actions

• batching multiple pools together

• generating ZK proofs

• submitting final batches to the settlement chain

- Detailed Description:

Sequencer Responsibilities:

• Collects private actions from all ZK Pools

• Determines execution order (MEV-safe, deterministic)

• Aggregates actions into a batch

• Prepares public inputs for the Prover

The Sequencer does NOT see private data — only encrypted metadata and proof commitments.

Prover Responsibilities:

• Generates ZK-SNARK / ZK-STARK proofs for the batch

• Optimizes proof generation using:

  • GPU clusters

  • parallelized proving

  • recursive proofs

• Ensures state transition validity across all pools in the batch

• Sends a final compressed proof to the L1 verifier

- Core Responsibilities:

• Multi-pool batching

• ZK proof generation

• Gas optimization via batch settlement

• State root updates

• L1 finality & verification

- Why This Layer Matters:

It allows ZKGate to process:

• thousands of private actions

• across dozens of pools

• with a single aggregated proof

dramatically reducing fees while retaining full privacy.

---

3️. Cross-chain Private Bridge — ZK Message Passing & Interoperability Layer

- Role:

This layer connects ZKGate to multiple chains, enabling private transfers to and from any supported ecosystem.

- Detailed Description:

The Cross-chain Private Bridge uses Zero-Knowledge Message Passing (ZK-MP) to move assets and proofs between chains.

It consists of:

• Bridge contracts deployed on each L1/L2

• Pooled asset vaults

• ZK relayer system

• Cross-chain settlement logic

• Finality watchers & fraud protection

- Bridge Capabilities:

• Private Deposits: Users deposit assets from Solana/EVM → ZK Pool, generating a private commitment.

• Private Withdrawals: Users withdraw from ZK Pool → public address on any supported chain using withdrawal proofs.

• Cross-Pool Routing: Move value from one pool to another without revealing sender/receiver.

• ZK Message Passing: Pass encrypted messages across chains with validity proofs.

- Supported / Planned Chains:

• Solana

• Ethereum

• BNB Chain

• Base

• Cosmos SDK chains

- Why This Layer Matters:

It lets ZKGate act as a universal privacy backend for multiple chains instead of one isolated L2.