ZERYNEX / DEVELOPER TOOLS 001
ZERYNEX TOOLING / LOCAL FIRST

Build with privacy.

Run real PCZT checks, enforce disclosure policies and integrate tested Rust tooling into Zcash applications.

ENGINE INITIALIZING
EXPERIMENT 02 / RUST + WASMPCZT Stage ComparatorCompare two real local PCZTs for policy and pool-structure changes.EXPERIMENT 03 / SYNTHETIC ROLESRole Handoff TestsRun four upstream role-fixture regressions and export the results.
01 / INPUT SOURCE
LOCAL DEVICE ONLY
Drop a PCZT into the fieldOr click to select a binary Zcash transaction filePCZT / MAX 8 MiB
TRY A SYNTHETIC PCZT
Files are parsed in this browser using WebAssembly. No upload. No account. No telemetry.
02 / DISCLOSURE POLICY
SELECT A PROFILE
ADDITIONAL PRIVACY INVARIANTS
These profiles are early checks. A passing report is not proof of anonymity, and restrictive policies may reject data a real signer needs.
03 / ANALYSIS CONSOLE
NO REMOTE PROCESSING
AWAITING SOURCE / 000

Your privacy report
starts here.

Load a real binary PCZT, choose a disclosure profile, and run the Rust engine. Results appear here.

IN / BROWSER ONLY · 127.0.0.1 PRINCIPLE
ZERO UPLOAD ARCHITECTUREEARLY ACCESS / V0.1
Prefer your terminal?

Run the same engine as a local Rust CLI. No service dependency.

cargo run -- path/to/file.pczt --profile external-signer --jsonRead installation guide
04 / CONNECT YOUR TOOLCHAIN

Integrate Zerynex your way.

Use the same Rust policy rules through the ecosystem your team already knows. No new hosted trust boundary.

PACKAGE MANAGER GUIDE
CLI + CILOCAL FIRST

Use the canonical Rust engine

Run policy-as-code checks on a locally held PCZT. Exit status 0 is no findings, 2 means findings, and 1 indicates an input or runtime problem.

DEVELOPER QUICKSTART
cargo build --locked --release
./target/release/zerynex apps/web/public/examples/transparent-v6.bin \
  --policy-file policies/shielded-only.json --json
READ INTEGRATION DOCUMENTATION

GITHUB ACTION SUPPORTS EXTERNAL REPOSITORIES. SDK PACKAGES ARE STILL SOURCE-ONLY, NOT REGISTRY-RELEASED.

NOT A CONSENSUS VALIDATOR OR SECURITY AUDITZIP-374 REFERENCE