ZclassicDev · nimbosa · Mar 6, 2018 · Feb 4, 2018 · Feb 11, 2018 · Feb 11, 2018
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,5 +1,7 @@
 <!--- Remove text and sections that do not apply -->
 
+Zclassic Wallet Daemon and CLI Issue Template
+
 This issue tracker is only for technical issues related to zcashd.
 
 General Zcash questions and/or support requests and are best directed to the [Zcash Forums](https://forum.z.cash) or [Community Rocket.Chat](https://chat.zcashcommunity.com).
@@ -21,7 +23,7 @@ Tell us what should happen
 ### Actual behaviour + errors
 Tell us what happens instead including any noticable error output (any messages displayed on-screen when e.g. a crash occurred)
 
-### The version of Zcash you were using:
+### The version of Zclassic / Zcash you were using:
 Run `zcashd --version` to find out
 
 ### Machine specs:
@@ -34,9 +36,9 @@ Run `zcashd --version` to find out
 - Compiler version (gcc -version):
 
 ### Any extra information that might be useful in the debugging process.
-This includes the relevant contents of `~/.zcash/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
+This includes the relevant contents of `~/.zclassic/debug.log`. You can paste raw text, attach the file directly in the issue or link to the text via a pastebin type site.
 Please also include any non-standard things you did during compilation (extra flags, dependency version changes etc.) if applicable.
 
-### Do you have a back up of `~/.zcash` directory and/or take a VM snapshot?
-- Backing up / making a copy of the `~/.zcash` directory might help make the problem reproducible. Please redact appropriately.
+### Do you have a back up of `~/.zclassic` directory and/or take a VM snapshot?
+- Backing up / making a copy of the `~/.zclassic` directory might help make the problem reproducible. Please redact appropriately.
 - Taking a VM snapshot is really helpful for interactively testing fixes
diff --git a/.gitignore b/.gitignore
@@ -1,6 +1,7 @@
 *.tar.gz
 *.deb
 *.exe
+*.dSYM
 src/bitcoin
 src/zcashd
 src/zcash-cli
@@ -56,7 +57,7 @@ src/univalue/gen
 *.pyc
 *.o
 *.o-*
-.zcash
+.zclassic
 *.a
 *.pb.cc
 *.pb.h

diff --git a/COPYING b/COPYING
@@ -1,3 +1,4 @@
+Copyright (c) 2016-2018 The Zclassic Team
 Copyright (c) 2016-2017 The Zcash developers
 Copyright (c) 2009-2017 The Bitcoin Core developers
 
@@ -32,7 +33,7 @@ software written by Eric Young ([email protected]),
 and UPnP software written by Thomas Bernard.
 
 
-Although almost all of the Zcash code is licensed under "permissive" open source
+Although almost all of the Zclassic code is licensed under "permissive" open source
 licenses, users and distributors should note that when built using the default
-build options, Zcash depends on Oracle Berkeley DB 6.2.x, which is licensed
+build options, Zclassic depends on Oracle Berkeley DB 6.2.x, which is licensed
 under the GNU Affero General Public License.
diff --git a/INSTALL b/INSTALL
@@ -1,5 +1,5 @@
-Building Zcash
+Building Zclassic
 
-See the Zcash github wiki (https://github.com/zcash/zcash/wiki) for instructions on building zcashd,
+See the Zclassic (https://github.com/z-classic/zclassic/wiki) and Zcash wiki (https://github.com/zcash/zcash/wiki) for instructions on building the daemon and cli tools,
 the intended-for-services, no-graphical-interface, reference
-implementation of Zcash.
+implementation of Zclassic.
diff --git a/README.md b/README.md
@@ -1,13 +1,34 @@
-Zclassic v1.0.10-1
-
-NOTICE, the default ports have changed! The p2p port is now 8033 and rpcport is 8023
+# Zclassic
 
 What is Zclassic?
 ----------------
-Zclassic is financial freedom.
+Zclassic is a cryptocurrency with a focus on privacy. It uses the same initial ceremony parameters generated for [Zcash](https://github.com/zcash/zcash), as well as ZK-SNARKs for transaction shielding. The major change - there is no 20% [founders' fee](https://blog.z.cash/funding/) taken for mining each block.
 
-Install
------------------
+More technical details are available
+in the [Zcash Protocol Specification](https://github.com/zcash/zips/raw/master/protocol/protocol.pdf).
+
+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 `zcashd` and `zcash-cli`, which should be renamed to `zcld` and `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](https://github.com/z-classic/zclassic/wiki)**
+
+**View unsolved problems on the [issue tracker](https://github.com/z-classic/zclassic/wiki)**
+
+**Join the conversation on Discord:
+https://discord.gg/NyPnDJS**
+
+Participation in the Zclassic project is subject to a
+[Code of Conduct](code_of_conduct.md). This is based on the original Zcash Code of Conduct.
+
+Build and Installation
+----------------------
 ### Linux
 
 Get dependencies
@@ -29,20 +50,68 @@ Install
 ```
 
 ### Windows
-Get dependencies
+There are two proven ways to build Zclassic for Windows:
+
+* On Linux using [MinGW-w64](https://mingw-w64.org/doku.php) 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)](https://msdn.microsoft.com/commandline/wsl/about) 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](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide) to install WSL (recommended method).
+
+### Building for Windows 64-Bit
+1. Get the usual dependencies:
 ```{r, engine='bash'}
+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 mingw-w64
+      zlib1g-dev wget bsdmainutils automake make cmake mingw-w64
 ```
 
-Install (Cross-Compiled, building on Windows is not supported yet)
+2. Set the default mingw32 gcc/g++ compiler option to posix, and fix other packing problems with Xenial.
+
 ```{r, engine='bash'}
-# Build
+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++
+```
+
+3. Install Rust
+```{r, engine='bash'}
+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
+```
+and add:
+```
+[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.
+
+4. Build for Windows
+
+```{r, engine='bash'}
+PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var. ONLY FOR WSL
 ./zcutil/build-win.sh -j$(nproc)
 ```
-The exe will save to `src` which you can then move to a windows machine
+
+5. Installation
+
+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
+
+```{r, engine='bash'}
+make install DESTDIR=/mnt/c/zcl/zclassic
+```
+This will install the executables to `c:\zcl\zclassic`
 
 ### Mac
 Get dependencies
@@ -66,27 +135,13 @@ Install
 ./src/zcashd
 ```
 
-About
---------------
-
-[Zclassic](http://zclassic.org/), like [Zcash](https://z.cash/), is an implementation of the "Zerocash" protocol.
-Based on Bitcoin's code, it intends to offer a far higher standard of privacy
-through a sophisticated zero-knowledge proving scheme that preserves
-confidentiality of transaction metadata. Technical details are available
-in the Zcash [Protocol Specification](https://github.com/zcash/zips/raw/master/protocol/protocol.pdf).
-
-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.
-
 Security Warnings
 -----------------
 
 See important security warnings in
 [doc/security-warnings.md](doc/security-warnings.md).
 
-**Zclassic and Zcash are unfinished and highly experimental.** Use at your own risk.
+Zclassic and Zcash are **unfinished** and **highly experimental**. Use at your own risk.
 
 Deprecation Policy
 ------------------
@@ -96,31 +151,6 @@ 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.
 
-Where do I begin?
------------------
-We have a guide for joining the main Zclassic network:
-https://github.com/z-classic/zclassic/wiki/1.0-User-Guide
-
-### Need Help?
-
-* See the documentation at the [Zclassic Wiki](https://github.com/z-classic/zclassic/wiki)
-  for help and more information.
-* Ask for help on the [Zclassic](http://zcltalk.tech/index.php) forum.
-
-### Want to participate in development?
-
-* Code review is welcome!
-* If you want to get to know us join our slack: http://zclassic.herokuapp.com/
-
-
-Participation in the Zcash project is subject to a
-[Code of Conduct](code_of_conduct.md).
-
-Building
---------
-
-Build Zcash along with most dependencies from source by running
-./zcutil/build.sh. Currently only Linux is officially supported.
 
 License
 -------

diff --git a/contrib/debian/examples/zcash.conf → contrib/debian/examples/zclassic.conf b/contrib/debian/examples/zcash.conf → contrib/debian/examples/zclassic.conf
@@ -1,10 +1,10 @@
 ##
-## zcash.conf configuration file. Lines beginning with # are comments.
+## zclassic.conf configuration file. Lines beginning with # are comments.
 ##
 
 # Network-related settings:
 
-# Run on the test network instead of the real zcash network.
+# Run on the test network instead of the real zclassic network.
 #testnet=0
 
 # Run a regression test network
@@ -72,15 +72,15 @@
 #rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593
 
 # How many seconds zcash will wait for a complete RPC HTTP request.
-# after the HTTP connection is established. 
+# after the HTTP connection is established.
 #rpcclienttimeout=30
 
 # By default, only RPC connections from localhost are allowed.
 # Specify as many rpcallowip= settings as you like to allow connections from other hosts,
 # either as a single IPv4/IPv6 or with a subnet specification.
 
 # NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
-# because the rpcpassword is transmitted over the network unencrypted and also because anyone 
+# because the rpcpassword is transmitted over the network unencrypted and also because anyone
 # that can authenticate on the RPC port can steal your keys + take over the account running zcashd
 # For more information see https://github.com/zcash/zcash/issues/1497
 
@@ -122,8 +122,6 @@
 
 # Pay an optional transaction fee every time you send zcash.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
-# be validated sooner. This setting does not affect private transactions created with 
+# be validated sooner. This setting does not affect private transactions created with
 # 'z_sendmany'.
 #paytxfee=0.00
-
-
diff --git a/contrib/debian/zcash.examples b/contrib/debian/zcash.examples
@@ -1 +1 @@
-DEBIAN/examples/zcash.conf
+DEBIAN/examples/zclassic.conf
diff --git a/depends/packages/librustzcash.mk b/depends/packages/librustzcash.mk
@@ -6,14 +6,21 @@ $(package)_download_file=$($(package)_git_commit).tar.gz
 $(package)_sha256_hash=a5760a90d4a1045c8944204f29fa2a3cf2f800afee400f88bf89bbfe2cce1279
 $(package)_git_commit=91348647a86201a9482ad4ad68398152dc3d635e
 $(package)_dependencies=rust
+ifeq ($(host_os),mingw32)
+  rust_build=cargo build --release --lib --target="x86_64-pc-windows-gnu"
+  rust_target=target/x86_64-pc-windows-gnu/release/rustzcash.lib $($(package)_staging_dir)$(host_prefix)/lib/librustzcash.a
+else
+  rust_build=cargo build --release
+  rust_target=target/release/librustzcash.a $($(package)_staging_dir)$(host_prefix)/lib/
+endif
 
 define $(package)_build_cmds
-  cargo build --release
+  $(rust_build)
 endef
 
 define $(package)_stage_cmds
   mkdir $($(package)_staging_dir)$(host_prefix)/lib/ && \
   mkdir $($(package)_staging_dir)$(host_prefix)/include/ && \
-  cp target/release/librustzcash.a $($(package)_staging_dir)$(host_prefix)/lib/ && \
+  cp $(rust_target) && \
   cp include/librustzcash.h $($(package)_staging_dir)$(host_prefix)/include/
 endef
diff --git a/depends/packages/rust.mk b/depends/packages/rust.mk
@@ -5,6 +5,8 @@ $(package)_file_name_linux=rust-$($(package)_version)-x86_64-unknown-linux-gnu.t
 $(package)_sha256_hash_linux=48621912c242753ba37cad5145df375eeba41c81079df46f93ffb4896542e8fd
 $(package)_file_name_darwin=rust-$($(package)_version)-x86_64-apple-darwin.tar.gz
 $(package)_sha256_hash_darwin=2d08259ee038d3a2c77a93f1a31fc59e7a1d6d1bbfcba3dba3c8213b2e5d1926
+$(package)_file_name_mingw32=rust-$($(package)_version)-x86_64-pc-windows-gnu.tar.gz
+$(package)_sha256_hash_mingw32=523cd248363afdc4e2c0e1f219607897b6925294a33154d7e67224addfd15eb0
 
 define $(package)_stage_cmds
   ./install.sh --destdir=$($(package)_staging_dir) --prefix=$(host_prefix)/native --disable-ldconfig

diff --git a/doc/amqp.md b/doc/amqp.md
@@ -89,7 +89,7 @@ the topic is `hashtx` (no null terminator) and the body is the hexadecimal
 transaction hash (32 bytes).  This transaction hash and the block hash
 found in `hashblock` are in RPC byte order.
 
-These options can also be provided in zcash.conf.
+These options can also be provided in zclassic.conf.
 
 Please see `contrib/amqp/amqp_sub.py` for a working example of an
 AMQP server listening for messages.

diff --git a/doc/files.md b/doc/files.md
@@ -1,4 +1,4 @@
-* zcash.conf: contains configuration settings for zcashd
+* zclassic.conf: contains configuration settings for zcashd
 * zcashd.pid: stores the process id of zcashd while running
 * blocks/blk000??.dat: block data (custom, 128 MiB per file)
 * blocks/rev000??.dat; block undo data (custom)

diff --git a/doc/man/zcash-cli.1 b/doc/man/zcash-cli.1
@@ -25,7 +25,7 @@ This help message
 .HP
 \fB\-conf=\fR<file>
 .IP
-Specify configuration file (default: zcash.conf)
+Specify configuration file (default: zclassic.conf)
 .HP
 \fB\-datadir=\fR<dir>
 .IP
@@ -72,7 +72,7 @@ please see <https://z.cash/support/security/index.html>.
 
 Copyright (C) 2009-2017 The Bitcoin Core Developers
 Copyright (C) 2015-2017 The Zcash Developers
-Copyright (C) 2015-2017 zdeveloper.org
+Copyright (C) 2015-2017 The Zclassic Team
 
 This is experimental software.
 

diff --git a/doc/man/zcashd.1 b/doc/man/zcashd.1
@@ -41,7 +41,7 @@ How thorough the block verification of \fB\-checkblocks\fR is (0\-4, default: 3)
 .HP
 \fB\-conf=\fR<file>
 .IP
-Specify configuration file (default: zcash.conf)
+Specify configuration file (default: zclassic.conf)
 .HP
 \fB\-daemon\fR
 .IP
@@ -467,7 +467,7 @@ console, 600 otherwise)
 <<<<<<< HEAD
 Copyright \(co 2009\-2017 The Bitcoin Core Developers
 Copyright \(co 2015\-2017 The Zcash Developers
-Copyright \(co 2015\-2017 zdeveloper.org
+Copyright \(co 2015\-2017 The Zclassic Team
 =======
 
 In order to ensure you are adequately protecting your privacy when using Zcash,

diff --git a/doc/payment-api.md b/doc/payment-api.md
@@ -32,7 +32,7 @@ RPC calls by category:
 * Addresses : z_getnewaddress, z_listaddresses, z_validateaddress
 * Keys : z_exportkey, z_importkey, z_exportwallet, z_importwallet
 * Operation: z_getoperationresult, z_getoperationstatus, z_listoperationids
-* Payment : z_listreceivedbyaddress, z_sendmany
+* Payment : z_listreceivedbyaddress, z_sendmany, z_shieldcoinbase
 
 RPC parameter conventions:
 
@@ -71,7 +71,8 @@ z_importwallet | filename | _Requires an unlocked wallet or an unencrypted walle
 Command | Parameters | Description
 --- | --- | ---
 z_listreceivedbyaddress<br> | zaddr [minconf=1] | Return a list of amounts received by a zaddr belonging to the node’s wallet.<br><br>Optionally set the minimum number of confirmations which a received amount must have in order to be included in the result.  Use 0 to count unconfirmed transactions.<br><br>Output:<br>[{<br>“txid”: “4a0f…”,<br>“amount”: 0.54,<br>“memo”:”F0FF…”,}, {...}, {...}<br>]
-z_sendmany<br> | fromaddress amounts [minconf=1] [fee=0.0001] | _This is an Asynchronous RPC call_<br><br>Send funds from an address to multiple outputs.  The address can be either a taddr or a zaddr.<br><br>Amounts is a list containing key/value pairs corresponding to the addresses and amount to pay.  Each output address can be in taddr or zaddr format.<br><br>When sending to a zaddr, you also have the option of attaching a memo in hexadecimal format.<br><br>**NOTE:**When sending coinbase funds to a zaddr, the node's wallet does not allow any change. Put another way, spending a partial amount of a coinbase utxo is not allowed. This is not a consensus rule but a local wallet rule due to the current implementation of z_sendmany. In future, this rule may be removed.<br><br>Example of Outputs parameter:<br>[{“address”:”t123…”, “amount”:0.005},<br>,{“address”:”z010…”,”amount”:0.03, “memo”:”f508af…”}]<br><br>Optionally set the minimum number of confirmations which a private or transparent transaction must have in order to be used as an input.<br><br>Optionally set a transaction fee, which by default is 0.0001 ZEC.<br><br>Any transparent change will be sent to a new transparent address.  Any private change will be sent back to the zaddr being used as the source of funds.<br><br>Returns an operationid.  You use the operationid value with z_getoperationstatus and z_getoperationresult to obtain the result of sending funds, which if successful, will be a txid.
+z_sendmany<br> | fromaddress amounts [minconf=1] [fee=0.0001] | _This is an Asynchronous RPC call_<br><br>Send funds from an address to multiple outputs.  The address can be either a taddr or a zaddr.<br><br>Amounts is a list containing key/value pairs corresponding to the addresses and amount to pay.  Each output address can be in taddr or zaddr format.<br><br>When sending to a zaddr, you also have the option of attaching a memo in hexadecimal format.<br><br>**NOTE:**When sending coinbase funds to a zaddr, the node's wallet does not allow any change. Put another way, spending a partial amount of a coinbase utxo is not allowed. This is not a consensus rule but a local wallet rule due to the current implementation of z_sendmany. In future, this rule may be removed.<br><br>Example of Outputs parameter:<br>[{“address”:”t123…”, “amount”:0.005},<br>,{“address”:”z010…”,”amount”:0.03, “memo”:”f508af…”}]<br><br>Optionally set the minimum number of confirmations which a private or transparent transaction must have in order to be used as an input.  When sending from a zaddr, minconf must be greater than zero.<br><br>Optionally set a transaction fee, which by default is 0.0001 ZEC.<br><br>Any transparent change will be sent to a new transparent address.  Any private change will be sent back to the zaddr being used as the source of funds.<br><br>Returns an operationid.  You use the operationid value with z_getoperationstatus and z_getoperationresult to obtain the result of sending funds, which if successful, will be a txid.
+z_shieldcoinbase<br> | fromaddress toaddress [fee=0.0001] | _This is an Asynchronous RPC call_<br><br>Shield transparent coinbase funds by sending to a shielded z address.  Utxos selected for shielding will be locked.  If there is an error, they are unlocked.  The RPC call `listlockunspent` can be used to return a list of locked utxos.  The number of coinbase utxos selected for shielding is limited by both the -mempooltxinputlimit=xxx option and a consensus rule defining a maximum transaction size of 100000 bytes.  <br><br>The from address is a taddr or "*" for all taddrs belonging to the wallet.  The to address is a zaddr. The default fee is 0.0001.<br><br>Returns an object containing an operationid which can be used with z_getoperationstatus and z_getoperationresult, along with key-value pairs regarding how many utxos are being shielded in this trasaction and what remains to be shielded.
 
 ### Operations