Privacy & Threat Model

Cryptographic privacy architecture: what is shielded off-chain, what is proven zero-knowledge, and what remains public by design.

ZK Groth16 Prover & Onchain Verifier Active

Zero-Knowledge circuit (withdraw.circom) and onchain Groth16 Verifier (0x9D9C…F915) are actively live on Robinhood Chain. Client-side proof synthesis runs directly in-browser using WebAssembly.

Inspect ZK Verifier Onchain ↗
Settlement LayerOnchain

Public Accounting

Transparent parameters required for trustless accounting & settlement audits:

  • •
    Pool Aggregate Balances

    Total vault reserves held in contract to guarantee 1:1 asset backing.

  • •
    Public Event Receipts

    Cryptographic confirmation of state changes emitted for indexed explorers.

  • •
    Merkle Tree Commitments

    Root hashes stored onchain proving inclusion without revealing individual notes.

Verifiable proof of reserves ensures the vault is never fractional or over-leveraged.
Shielded EngineZero-Knowledge

Private Cryptography

Confidential state protected by Groth16 zero-knowledge proofs:

  • •
    Private Account Identity

    Deterministic keys control notes; public wallet address is never linked.

  • •
    Private Balances & Portfolio

    Hidden inside Poseidon note commitments; unreadable by chain observers.

  • •
    Trade Wave Batch Netting

    Intents execute uniformly at the clearing price with no individual trace.

Client-side Circom/Groth16 proving: the witness never leaves your browser.
Protocol BoundaryBy Design

Permanently Public

Actions at the Robinhood Chain layer that can never be hidden:

  • •
    Deposits & Withdrawals

    Asset amount and exit destination when crossing the vault boundary.

  • •
    Trade Wave Aggregates

    Total netted volume and execution clearing price on L2.

  • •
    Network Metadata

    IP address and RPC timestamps (ZK does not alter transport layer).

Privacy means reducing linkage, not fabricating mathematical miracles.