From a demo to your project.

Zerynex does not automatically connect to a developer's computer or Zcash wallet. Choose an interface, install it into your trusted environment, then run checks against files your application explicitly supplies.

01 / Try bundled demo 02 / Analyze a local PCZT 03 / Integrate your project — below

01 / CHOOSE YOUR ENVIRONMENT

Local-first boundaries. No account, wallet connection, background scanner or remote PCZT upload is created by this onboarding page. Private data remains under your control.

02 / INSTALL · CONFIGURE · VERIFY

Verify Zerynex in your own codebase

PROJECT BOOTSTRAP

Zcash developers adopting local PCZT privacy checks and CI

BEFORE YOU START

An existing project directory, Python 3.11+, the published zerynex-python SDK, and a separately installed Rust CLI executable

Install the public Python SDK

Install the official v0.2.0 PyPI distribution. It does not require a hosted Zerynex account; PCZT checks also need the separate Rust CLI.

COPYABLE EXAMPLE

python3 -m venv .venv
.venv/bin/python -m pip install zerynex-python==0.2.0

Create nonspendable checks in your repository

Only two reviewed synthetic PCZTs, a policy, manifest and an optional immutable-pin CI workflow are created. Existing files are never overwritten.

COPYABLE EXAMPLE

zerynex-project init --project /absolute/path/to/my-zcash-app --ci --json

Verify the actual local Rust installation

Runs the real CLI against both bundled fixtures. One passes cleanly; the transparent example must produce the expected policy finding.

COPYABLE EXAMPLE

zerynex-project verify --project /absolute/path/to/my-zcash-app --cli /absolute/path/to/zerynex --json

What success looks like

The local CLI is installed and passes real tests on bundled synthetic files. This does not connect to private code or wallets, execute a payment, or prove wallet integration.

Read Project bootstrap reference Privacy & security boundaries