Privacy and trust model
Understand disclosure rules, private PCZT handling and limitations.
Zerynex privacy model
Local PCZT privacy analysis at component handoff boundaries. Both Rust CLI and browser WASM process local bytes; no hosted analysis endpoints.
Protected: unnecessary disclosure to signers/provers, unreviewed proprietary fields, and dummy spending keys.
Reports intentionally emit only fixed rule identifiers and field paths, never field values.
Not covered: consensus validity, proof validation, complete Sapling/transparent pool scanning, compromised browsers/devices, or network metadata privacy. Passing checks is not a security audit.
Synthetic fixtures are v6 PCZTs created by official Zcash Rust APIs with no spendable funds; one includes intentionally flagged synthetic global metadata.
Additional invariants
Zerynex can enforce a no-transparent-components policy and optionally prohibit Sapling spends/outputs. This checks the intermediary PCZT, not earlier or later transactions in the wallet history. Sapling inspection does not cover private fields hidden behind upstream crate internals.
Policy files use strict JSON validation and have an upper size bound. There is no configurable allowlist for proprietary fields in this release.