Version 1.0.14 Beta Release (2018-01-29)
Zclassic 1.0.14 beta
you may use at your own risk, but best build from master
: these are January 29 public builds of x64 GNU/Linux binaries provided for your convenience, they have been tested as the same software that powers our nodes running on Amazon instances
official GUI wallet is updated and available here: https://github.com/z-classic/zclassic-full-node-wallet/releases but the bundled binaries there are only for MacOS & Windows, and are based on Zclassic's official 1.0.10 code, if you want to use the bundled GUI with updated 1.0.14 node, it is available here: https://github.com/ZclassicDev/zclassic/blob/master/ZClassicSwingWalletUI.jar - the updated Java Swing Wallet referenced above
you can report issues and give suggestions here: https://github.com/ZclassicDev/zclassic/issues
it WORKS!
extract contents to ~ home folder, or wherever convenient
ZCLd => zcld / zcld-linux // TODO: rename from zcashd NAME COLLISION!
ZCLi => zcl-cli // TODO: rename from zcash-cli NAME COLLISION!
ZCL-tx => zcl-tx // TODO: rename from zcash-tx NAME COLLISION!
BEWARE of NAME COLLISION when installing .deb or building from source!!!
you have been warned..
:)
rename is necessary to avoid conflict with Zcash on the same machine!
configuration
A.) before running ZCLd:
mkdir ~/.zcash-params
cd ~/.zcash-params
wget https://z.cash/downloads/sprout-verifying.key
wget https://z.cash/downloads/sprout-proving.key
- we use the same parameters as in Zcash, and it is a one time download
B.) create a ~/.zclassic
folder and put your zclassic.conf inside it:
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-testing/zclassic.conf
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
verification
this uploaded beta release 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-x64-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-x64-binaries.tar.xz
# OR,
md5sum /path/to/ZCL-x64-binaries.tar.xz
VERIFY that the checksums match those BELOW!
MD5: 002B0648B21E6495D9903155587A2427
base64: 7e8u+iCyYBnDD7Gg/CESO1LV+3BqhmHNSNZIW2HnR50=
HEX: EDEF2EFA20B26019C30FB1A0FC21123B52D5FB706A8661CD48D6485B61E7479D
hex: edef2efa20b26019c30fb1a0fc21123b52d5fb706a8661cd48d6485b61e7479d
h:e:x: edef:2efa:20b2:6019:c30f:b1a0:fc21:123b:52d5:fb70:6a86:61cd:48d6:485b:61e7:479d
OR simply run: sha256sum --check checksums.TXT
you can donate
ZEC, ZCL, ZEN or HUSH:
Transparent Address: (use from exchanges or mining pool payouts)
t1KQ3HrQ4A8rW6xxADkwJ5AjgD3hPw2ZNEz
Shielded Z-address: (safe to use from own wallet)
zcMjE6wy1F7KBXygFwyLBdJPNDKxDj9oXzpRk3zed92SbsWt6KkxpaUvT9P2p1fomMQ8CWhQQEsNGnQGjdx3ASJPjVaAB3Z