Zcash-inspired. Robinhood-built.
beprivate explores how the principles behind Zcash shielded transactions could inform a privacy layer for Robinhood Chain. This is a research direction, not an existing Zcash integration.
The inspiration: prove without revealing
Zcash uses zero-knowledge proofs to validate shielded transactions while keeping their private details encrypted. Its Orchard protocol uses the Halo 2 proving system. These are properties of Zcash’s protocol, not properties that an EVM application inherits by using similar language or interface controls.
What runs on Robinhood today
Only pre-trade RFQ intent is private/offchain; shield deposits, contract balances, final fills, and unshield withdrawals are public onchain.
The beta uses an EVM custody ledger, signed RFQ quotes, a wallet approval registry, and a configured solver. Its only supported trading pair is WETH / USDG. The server and solver can see quote requests. Zcash is not used to execute, settle, prove, or shield these trades.
Research, integration, then verification
- Define a privacy threat model: which information is hidden, from whom, and under which assumptions.
- Evaluate proof-system and EVM-verification options informed by Zcash research. Orchard and Halo 2 are not drop-in Solidity components; their feasibility, cost, and compatibility remain to be established.
- Design commitments, nullifiers, encrypted notes, key recovery, and relaying together with deposit and withdrawal visibility.
- Specify how compliance and user-authorized disclosure would work without claiming services or partnerships that do not exist.
- Audit circuits, contracts, and wallet behavior independently; verify deployed code and only then describe the resulting privacy guarantees.
What the brand does not imply
beprivate is independent software. It is not affiliated with or endorsed by Robinhood, the Zcash Foundation, or Electric Coin Company. ZEC is not a supported deposit asset and no Zcash-to-Robinhood bridge exists in this codebase.
The deployed EIP-712 signing domain remains Hide Settlement for compatibility with existing contracts. The beprivate brand does not change the contract address, signature domain, or users’ recorded balances.