Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.privacyboost.io/llms.txt

Use this file to discover all available pages before exploring further.

Privacy Boost enables applications to integrate private transfers and privacy-preserving DeFi workflows into public blockchains while keeping the data private from the public, viewable by the sponsoring app, and auditable by regulators. Deposit, transfer, and withdraw ERC-20 tokens with amounts, counterparties, and balances fully hidden onchain.

Protocol Deep Dive

Understand the protocol, cryptographic foundations, and architecture

Start Building

Integrate private payments into your app with our multi-platform SDKs

​
Who is this for?

On public blockchains, every transfer, every balance, and every counterparty relationship is visible to anyone. For applications handling real financial flows, this creates immediate business, competitive, and regulatory risk.

Wallets

User balances and transaction history must remain private — not broadcast onchain.

Stablecoin Networks

Payment and settlement flows require confidentiality between counterparties.

RWA Platforms

Institutional positions and counterparty identities are commercially sensitive.

Fintech Applications

Privacy must align with financial regulatory frameworks, not conflict with them.

​
Why Privacy Boost?

Sub-500ms Transactions

Server-side ZK proof generation inside a hardware-isolated enclave. No client-side proving — works instantly on any device, including mobile.

1,800+ TPS

Proof aggregation batches hundreds of transfers into a single onchain transaction, reducing gas costs by orders of magnitude.

Auditability

Authorized auditors can query specific accounts. Every audit access is logged immutably onchain. Privacy for users, accountability for regulators.

True Self-Custody

Your keys, your funds. Forced withdrawal lets you exit directly through the smart contract — even if every server goes offline permanently.

Instant Balances & History

A TEE-secured indexer decrypts and serves your balance and transaction history in real time. No blockchain scanning required.

Drop-In Integration

Works with MetaMask, WalletConnect, and any EOA. TypeScript, React, CLI, and Rust SDKs — with iOS, Android, and React Native coming soon. No new wallet software needed.

​
Demo

Try the live app →

​
How It Works

Privacy Boost Pool Architecture: encrypted requests flow from users through TEE Server, which batches transactions and submits ZK proofs to the shielded pool smart contract 1. Deposit — Tokens move from a public wallet into the privacy layer and become encrypted private notes. 2. Transfer Request — The user signs a transfer with their spending keys and submits it to the TEE Prover. 3. ZK Proof Generation — The TEE generates a zero-knowledge proof in ~500ms, and aggregates ZK proofs for higher throughput while enforcing regulatory rules. 4. Onchain Verification — The smart contract verifies the proof and records the result. Amounts, balances, and counterparties remain hidden. 5. Encrypted State Indexing — The TEE Indexer reads onchain state and indexes encrypted metadata, giving sender and recipient instant access to their balances and history. 6. Auditability — When required, authorized auditors can query specific accounts’ balances and history through a scoped disclosure mechanism. Every query is logged immutably onchain.

​
Why ZK + TEE?

Most privacy protocols force a tradeoff: client-side proving is trustless but costs 5–30+ seconds per transaction, can’t serve balance queries, and has no auditability. Privacy Boost combines both:
  • ZK proofs provide the privacy guarantees — sender, recipient, amounts, and token types are all hidden onchain. The smart contract verifies every proof and holds all funds. This is the cryptographic foundation.
  • TEE handles what ZK alone can’t deliver: sub-500ms proof generation, instant balance and transaction history queries, and auditability through scoped audit access — all inside a hardware-isolated enclave.
The result: a privacy protocol with the speed and UX of a centralized system, the trustlessness of ZK, and the custody guarantees of a smart contract. Self-custody is unconditional. Even if the TEE goes offline permanently, users exit directly through the smart contract via forced withdrawal — using only their own keys and public onchain data.

Trust & Security Model

How the TEE works, what it can and can’t see, forced withdrawal, and the full threat model

​
Explore the Docs

Trust & Security

TEE guarantees, self-custody, forced withdrawal, and threat model

Compliance & Auditing

How auditors query data with onchain accountability

Protocol Deep Dive

UTXO model, notes, nullifiers, Merkle trees, transaction lifecycle

Keys & Encryption

Key hierarchy, dual-path ECDH encryption, privacy addresses