Zclassic 1.0.14 Release Binaries
(release candidate #1: this will be the Final Release if no bugs were found/reported)
- Zclassic Daemon version v1.0.14-0082b67
- Zclassic RPC client version v1.0.14-0082b67
you may use at your own risk, but best build from master, these are public builds for x64 systems provided for your convenience, they have been tested as the same software that powers our nodes running on Amazon instances (Project: ZCLAWS)
official Full Node GUI wallet is available here: https://github.com/z-classic/zclassic-full-node-wallet/releases
instructions
download files & extract contents to ~ home folder, or wherever convenient,
wget https://github.com/ZclassicDev/zclassic/releases/download/v1.0.14-rc1/ZCL-1.0.14-binaries.TAR.xz
tar xvf ZCL-1.0.14-binaries.TAR.xz -C ~/target/folder/
you may use PeaZip as your program to create and extract files, if you don't have one yet (available for Windows / MacOS / GNU/Linux)
configuration
A.) before running ZCLd / zcashd.exe
we use the same parameters as in Zcash, and it is a one time download:
-
Windows
- go to your user data folder (type:
%AppData%) and Create a New Folder namedZcashParams - inside
%AppData%/ZcashParamsdownload these files: https://z.cash/downloads/sprout-verifying.key & https://z.cash/downloads/sprout-proving.key
- go to your user data folder (type:
-
GNU/Linux
mkdir ~/.zcash-params
cd ~/.zcash-params
wget https://z.cash/downloads/sprout-verifying.key
wget https://z.cash/downloads/sprout-proving.key
B.) create a ~/.zclassic folder and put your zclassic.conf inside it:
review your zclassic.conf, and MAKE SURE you change your password, an example is provided here, prepopulated with ALL public peers we know, it is needed to synchronize your node
-
Windows
- go to your user data folder (type:
%AppData%) and Create a New Folder namedZclassicif you don't have one yet ; if you do have one already, you may want to copy the folder and back it up and rename it to Zclassic.BAK so you can go back to it if something goes wrong with your data - download https://github.com/ZclassicDev/zclassic/releases/download/v1.0.14-rc1/zclassic.conf or just copy the lines of
addnode=z.z.z.zto add to your list of full nodes if you have an existingzclassic.conf
- go to your user data folder (type:
-
GNU/Linux
mkdir ~/.zclassic
cd ~/.zclassic
wget https://github.com/ZclassicDev/zclassic/releases/download/v1.0.14-testing/zclassic.conf
OR back up your existing folder if you have one with previous data, just in case something goes wrong
cp ~/.zclassic ~/.zclassic.BAK
cd ~/.zclassic
wget https://github.com/ZclassicDev/zclassic/releases/download/v1.0.14-rc1/zclassic.conf
BEWARE of NAME COLLISION when installing .deb or building from source!!!
rename is necessary to avoid conflict with Zcash on the same machine!
ZCLd.exe => zcld / zcld-linux // TODO: rename from zcashd.exe NAME COLLISION!
ZCLi.exe => zcl-cli // TODO: rename from zcash-cli.exe NAME COLLISION!
ZCL-tx.exe => zcl-tx // TODO: rename from zcash-tx.exe NAME COLLISION!
symlink-ing
you may also use symbolic links (symlinks) to support older applications like Eleos or Java Swing wallets, put symlinks into the same folder as your legacy wallets, like so:
Windows
- open command prompt (type:
cmd) and right-click to "Run as administrator" - click "YES" and type: (the direction is destination==>source)
mklink /J C:\path\of\Eleos\or\Swing\zcld.exe D:\Real\Location\of\zcashd.exe
mklink /J C:\path\of\Eleos\or\Swing\zcl-cli.exe D:\Real\Location\of\zcash-cli.exe
mklink /J C:\path\of\Eleos\or\Swing\zcl-tx.exe D:\Real\Location\of\zcash-tx.exe
### OR reverse
mklink /J C:\path\of\Eleos\or\Swing\zcashd.exe D:\Real\Location\of\zcld.exe
mklink /J C:\path\of\Eleos\or\Swing\zcash-cli.exe D:\Real\Location\of\zcl-cli.exe
mklink /J C:\path\of\Eleos\or\Swing\zcash-tx.exe D:\Real\Location\of\zcl-tx.exe
GNU/Linux
- open your favorite terminal ;) and type: (the direction is source==>destination)
ln -s /mnt/download/path/ZCLd ~/wallet/path/zcld
# OR
ln -s /mnt/download/path/ZCLd ~/wallet/path/zcashd
# OR
ln -s /mnt/download/path/ZCLd ~/wallet/path/zclassicd
verification
this uploaded software is VERIFIED by GitHub as can be seen in green, to your left, below the tags and commit id, so if you have gpg OR gpg2 installed you can also verify by doing so:
# curl + gpg pro tip: import nimbosa's keys
curl https://keybase.io/nimbosa/pgp_keys.asc | gpg --import
keybase.io notarizes several attestations across distinct platforms that the uploader, nimbosa, has indeed signed and uploaded these files
once you have imported the PGP key above, you can verify the downloaded file on the same directory where ZCL-1.0.14-Win.EXE.TAR.xz OR ZCL-1.0.14-binaries.TAR.xz, checksums.TXT and checksums.TXT.asc are saved with:
gpg --verify checksums.TXT.asc checksums.TXT
you can check the hashes:
sha256sum /path/to/ZCL-1.0.14-binaries.TAR.xz
# OR,
md5sum /path/to/ZCL-1.0.14-binaries.TAR.xz
VERIFY that the checksums match those BELOW!
f364478d46f56661b05c6cbbb00ff5e65d96f977ac4cb2104e5b062086b883be ZCL-1.0.14-binaries.TAR.xz
74c74e8b769c62c5376fea1e1bd678eb6556592a27acce21b97dc0b730f45805 ZCL-1.0.14-Win.EXE.TAR.xz
OR simply run: sha256sum -c checksums.TXT
an excellent program for Windows to do these tasks above is Kleopatra+Gpg4win: https://www.gpg4win.org
donate now to support further development
$BTC Bitcoin:
bc1q4dgnccqsfa2yj3pxml5k73xumszcu00a928sq6e87rctsnlkvd0sgwfvpf (SegWit-Bech32)
35znxwpzz5rY5RzskPQAaVXje8aK7Gr6Xc (SegWit-P2WPKH-in-P2SH)
3AP2G9vyKTeTERgohqdycp4JcZhWUP2qSx (non-SegWit)
$BTCP Bitcoin Private:
b1F3WKG3tJvMqtuxrMDbnn79mEoZ1Dvq88V (nimbosa)
bxw64R6RwsJN8NVP7fSQGj2EssN2iraZzrJ (MultiSig-ZclassicCE)
ZEC, ZCL or HUSH:
Transparent Address: (use from exchanges or mining pool payouts)
t1KQ3HrQ4A8rW6xxADkwJ5AjgD3hPw2ZNEz (nimbosa)
t3eYEnoMmfUV65CZvPvV2mfAUnfFGoFbkJu (MultiSig-ZclassicCE)
Shielded Z-address: (safe to use from your own wallet)
zcMjE6wy1F7KBXygFwyLBdJPNDKxDj9oXzpRk3zed92SbsWt6KkxpaUvT9P2p1fomMQ8CWhQQEsNGnQGjdx3ASJPjVaAB3Z