Developer Overview

ZKGate is designed to be privacy-as-a-service for any Web3 project. As a developer, you mainly interact with:

• ZKGate SDK – client library to trigger private actions from your dApp.

• PoolKey System – how your project gets its own ZK Pool and permissions.

• REST / JSON-RPC APIs – low-level programmatic access for backends, bots, and services.

• Relayer Network – optional transaction relayers so users don’t need to pay gas directly.

The goal is that:

“If you can call a normal smart contract function, you can also call ZKGate for private execution — without writing any ZK circuits yourself.”