The problem CompZ – Privacy-Preserving Compliance on Zcash solves

The problem CompZ solves

Compliance today runs on trust-based artifacts: PDFs, spreadsheets, screenshots, and static reports. These are easy to backdate, hard to verify, and impossible to audit cryptographically. Even when teams “pass” compliance checks, there is no mathematical proof of when it happened or that the data hasn’t been altered.

CompZ replaces trust with cryptographic proof. It turns any compliance result into a deterministic hash and anchors it on Zcash, creating a privacy-preserving, verifiable timestamp without exposing sensitive data.

CompZ replaces fragile documents with cryptographic proof. Instead of storing audit files, it anchors a deterministic hash on Zcash, making evidence tamper-proof and time-verifiable without revealing data. This eliminates backdating, prevents silent changes, and removes the need to trust PDFs or spreadsheets. For developers, it reduces complexity to a single API/CLI call — no blockchain expertise required.

In just 6 days, CompZ reached 5,800+ downloads, validating real demand for privacy-first compliance infrastructure.

Challenges I ran into

1. TXID generation is asynchronous and easy to mis-handle

The z_sendmany call does not return a txid directly — it returns an operation ID (opid) that resolves later.

Hurdle: Early versions of CompZ falsely assumed a synchronous return, so “success” didn’t mean “transaction mined.”
Solution: Added polling via:

z_getoperationstatus

z_getoperationresult

…to block until a real txid is available or a failure is returned.

2. Honest limitation: wallets must be funded

Anchoring requires a real Zcash transaction.

Hurdle: Development environments often had no funded shielded address, which blocked txid creation.
Solution: Split the SDK into two modes:

Off-chain mode (hash + memo creation)

On-chain mode (broadcast + txid)

This kept CompZ usable even when a wallet wasn’t available.