What is Zclassic?
Zclassic is a cryptocurrency with a focus on privacy. It uses the same initial ceremony parameters generated for Zcash, as well as ZK-SNARKs for transaction shielding. The major change - there is no 20% founders' fee taken for mining each block.
More technical details are available in the Zcash Protocol Specification.
This software is the Zclassic client. It downloads and stores the entire history of Zclassic transactions; depending on the speed of your computer and network connection, the synchronization process could take a day or more once the blockchain has reached a significant size.
Two main files of interest in this repo are
zcash-cli, which should be renamed to
zcl-cli for use in the full-node wallet. The project needs to be built (per the instructions) in order to generate them.
P2P Port - 8033
RPC Port - 8023
Documentation is at the Zclassic wiki
View unsolved problems on the issue tracker
Join the conversation on Discord: https://discord.gg/NyPnDJS
Participation in the Zclassic project is subject to a Code of Conduct. This is based on the original Zcash Code of Conduct.
Build and Installation
sudo apt-get install \ build-essential pkg-config libc6-dev m4 g++-multilib \ autoconf libtool ncurses-dev unzip git python \ zlib1g-dev wget bsdmainutils automake
# Build ./zcutil/build.sh -j$(nproc) # fetch key ./zcutil/fetch-params.sh # Run ./src/zcashd
There are two proven ways to build Zclassic for Windows:
- On Linux using MinGW-w64 cross compiler tool chain. Ubuntu 16.04 Xenial is proven to work and the instructions is for such release.
- On Windows 10 (64-bit version) using Windows Subsystem for Linux (WSL) and the MinGW-w64 cross-compiler toolchain.
With Windows 10, Microsoft released a feature called WSL. It basically allows you to run a bash shell directly on Windows in an Ubuntu environment. WSL can be installed with other Linux variants, but as mentioned before, the distro proven to work is Ubuntu. Follow this link to install WSL (recommended method).
Building for Windows 64-Bit
- Get the usual dependencies:
sudo apt-get update sudo apt-get install \ build-essential pkg-config libc6-dev m4 g++-multilib \ autoconf libtool ncurses-dev unzip git python \ zlib1g-dev wget bsdmainutils automake make cmake mingw-w64
- Set the default mingw32 gcc/g++ compiler option to posix, and fix other packing problems with Xenial.
sudo apt install software-properties-common sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu zesty universe" sudo apt update sudo apt upgrade sudo update-alternatives --config x86_64-w64-mingw32-gcc sudo update-alternatives --config x86_64-w64-mingw32-g++
- Install Rust
curl https://sh.rustup.rs -sSf | sh source ~/.cargo/env rustup install stable-x86_64-unknown-linux-gnu rustup install stable-x86_64-pc-windows-gnu rustup target add x86_64-pc-windows-gnu vi ~/.cargo/config
[target.x86_64-pc-windows-gnu] linker = "/usr/bin/x86_64-w64-mingw32-gcc"
Note that in WSL, the Zclassic source code must be somewhere in the default mount file system, i.e
/usr/src/zclassic, and not on
/mnt/d/. What this means is that you cannot build directly on the Windows system.
- Build for Windows
PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var. ONLY FOR WSL ./zcutil/build-win.sh -j$(nproc)
After building in WSL, you can make a copy of the compiled executables to a directory on your Windows file system. This is done the following way
make install DESTDIR=/mnt/c/zcl/zclassic
This will install the executables to
#install xcode xcode-select --install /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" brew install cmake autoconf libtool automake coreutils pkgconfig gmp wget brew install gcc5 --without-multilib
# Build ./zcutil/build-mac.sh -j$(sysctl -n hw.ncpu) # fetch key ./zcutil/fetch-params.sh # Run ./src/zcashd
See important security warnings in doc/security-warnings.md.
Zclassic and Zcash are unfinished and highly experimental. Use at your own risk.
This release is considered deprecated 16 weeks after the release day. There is an automatic deprecation shutdown feature which will halt the node some time after this 16 week time period. The automatic feature is based on block height and can be explicitly disabled.
For license information see the file COPYING.