zkBob primary-source snapshot
Fetched: 2026-04-27 UTC
1) Website / product framing
Source: https://zkbob.com/ Source: https://docs.zkbob.com/zkbob-overview/readme.md
Selected excerpts from the official site/docs:
With zkBob, the contents of your wallet and the amounts you spend and receive are completely private.
zkBob is an open-source, decentralized application available for the community.
zkBob is a stablecoin-based privacy application deployed on Polygon and Optimism and designed for everyday users and common use cases.
Additional signals from the site/docs:
- The homepage frames zkBob as a smart-contract wallet for private salary, payments, donations, and other everyday transfers rather than as a research project or privacy coin
- The docs emphasize usable privacy for ordinary payments and repeatedly pair that with compliance and safety language
- The rendered docs also mention current multichain support spanning Polygon, Optimism, and Tron, with supported pools for USDC, ETH, and USDT
2) Architecture / operating model
Source: https://docs.zkbob.com/implementation/high-level-overview.md Source: https://docs.zkbob.com/zkbob-overview/readme.md?ask=What%20are%20zkBob%27s%20main%20components%2C%20supported%20networks%20and%20tokens%2C%20privacy%20mechanics%2C%20and%20compliance%20controls%3F
Selected excerpts from the docs:
The zkBob application is comprised of the following components: zkBob Pool, Bob Token, Relayer, Operator Manager, Application.
The Relayer receives user transactions, calculates zkSNARKs, and sends transactions to the Pool in a serial manner.
Deposits, transfers, and withdrawals use zkSNARKs to hide sender, receiver, and amounts.
Additional signals from these pages:
- The relayer is central to the UX and safety model because it serializes transactions against the pool and abstracts gas from users
- The docs treat the pool contract as the core state-holding component and the application as a convenience layer around it
- GitHub corroborates that the public implementation surface includes contracts, relayer code, UI, client libraries, and docs rather than only a wallet frontend
3) Compliance controls / restrictions
Source: https://docs.zkbob.com/zkbob-overview/compliance-and-security.md Source: https://docs.zkbob.com/zkbob-overview/readme.md?ask=What%20are%20zkBob%27s%20main%20components%2C%20supported%20networks%20and%20tokens%2C%20privacy%20mechanics%2C%20and%20compliance%20controls%3F
Selected excerpts from the docs:
Politically exposed individuals or associates of those individuals are not permitted to use the application under existing laws.
zkBob usage is currently restricted in several jurisdictions: United Arab Emirates (UAE) … United States (US).
An integration with TRM … ensure 0x wallets interacting with the protocol do not contain funds obtained from illicit sources.
Suspicious wallets cannot deposit into the protocol, and funds cannont be withdrawn to suspicious wallets.
Additional signals from these pages:
- The project is unusually explicit about user eligibility and geography restrictions for a privacy-focused product
- Deposit/withdrawal limits and pool-size caps are presented as risk mitigations, not just as product limitations
- These controls make zkBob look much closer to compliance-mediated privacy payments infrastructure than to a maximal-anonymity protocol
4) Security / audit surface
Source: https://docs.zkbob.com/resources/security-audit.md Source: https://github.com/zkBob/zkbob-contracts
Selected excerpts from the docs/repo:
ChainSecurity delivered their final audit report on January 5, 2023 covering the zkBobPool, BOBToken, and BobVault contracts.
High: 1 found, 1 corrected.
This repository contains all smart contracts that are being used in BOB and zkBOB projects.
Additional signals from these sources:
- The docs publicly summarize audit findings by severity and remediation status, which is useful for evaluating maturity
- The contracts repo gives a concrete first-party anchor for the protocol implementation and licensing
- This pass did not uncover a newer canonical protocol whitepaper, so the docs plus audit materials appear to be the best source of truth
5) GitHub / implementation footprint
Source: https://github.com/zkBob Source: https://raw.githubusercontent.com/zkBob/zkbob-contracts/master/README.md
Selected excerpts/signals from GitHub:
zkBob is a smart contract wallet with compliance-friendly privacy.
A stablecoin-based zkprotocol designed for simplicity, privacy and utility.
Additional signals from GitHub:
- The org exposes active repos for contracts, UI, relayer, client JS, console tooling, and docs, which supports cataloging zkBob as live infrastructure rather than just a static consumer app
- Repo descriptions reinforce the project’s stablecoin-plus-privacy framing and make the “compliance-friendly privacy” positioning explicit
- Public repos updated through 2025-2026 suggest the technical surface remains maintained
Notes
- This pass did not locate a canonical standalone whitepaper or litepaper in the first-party materials reviewed.
- The strongest source-of-truth surfaces were the official docs portal, the website, the GitHub org/contracts repo, and the linked ChainSecurity audit page.
- zkBob appears best categorized as privacy payments infrastructure / zk smart-contract wallet / compliance-mediated shielded transfers.