The Parity Zcash client.
Installing from source
pzec from source requires
Minimal supported version is
rustc 1.23.0 (766bd11c8 2018-01-01)
Install rustc and cargo
cargo are a part of rust tool-chain.
An easy way to install the stable binaries for Linux and Mac is to run this in your shell:
curl https://sh.rustup.rs -sSf | sh
Windows binaries can be downloaded from rust-lang website.
Install C and C++ compilers
You will need the cc and gcc compilers to build some of the dependencies.
build-essential is a Debian package. On macOS you will need to make sure you have Xcode installed. If you already have Homebrew installed, you probably also already have the Xcode tools installed as well. If not, you can run the command below:
sudo apt-get update
sudo apt-get install build-essential
Clone and build pzec
Now let's clone
pzec and enter it's directory:
git clone https://github.com/paritytech/parity-zcash
# builds pzec in release mode
cargo build -p pzec --release
pzec is now available at
Installing the snap
In any of the supported Linux distros:
sudo snap install parity-zcash --edge
pzec has internal unit tests and it conforms to external integration tests.
Running unit tests
Assuming that repository is already cloned, we can run unit tests with this command:
cargo test --all
By default parity connects to Zcash seednodes. Full list is here.
To start syncing the main network, just start the client without any arguments:
To start syncing the testnet:
To not print any syncing progress add
Importing zcashd database
It it is possible to import existing
# where $ZCASH_DB is path to your zcashd database. By default:
# on macOS: "/Users/user/Library/Application Support/Zcash"
# on Linux: "~/.zcash"
./target/release/pzec import "$ZCASH_DB/blocks"
By default, import verifies the imported blocks. You can disable this, by adding the
./target/release/pzec --verification-level=none import "$ZCASH_DB/blocks"
Command line interface
Full list of CLI options, which is available under
pzec --help: see here
This is a section only for developers and power users.
You can enable detailed client logging by setting the environment variable
pzec started with this environment variable will print all logs coming from
verification module with verbosity
info or higher. Available log levels are:
It's also possible to start logging from multiple modules in the same time:
pzec documentation will be available here. Meanwhile it's only possible to build it locally: