Zcash4win BETA is out!

I’ve had ZCash4Win running on my PC since the summer, but I haven’t used it other than to try it out in the beginning. I keep it running all the time to keep the blockchain fresh and to run so it acts as a “node” thingy, understanding that’s a good thing to do…

Anyhow, since I am a lover of freedom and privacy, I did another experimental transaction, but this one was to test specifically the time it takes to send ZEC from one “t” address to another “t” address and then onto a “z” address. I was pleased with the results.

I only send a small amount, 0.0x ZEC, but the total time needed to get the funds into the “z” address took about 20 mins. Yes, 20 minutes is a wait, but the time to do this should come down a lot later this year.

As an aside, I then plan to move any and all ZEC received into my t => z address to another z address to protect the privacy. It’s my assumption it’s what’s needed should I plan to make sends to other t or z destinations.

Thx to David for this simple to use proggy!

thanks… looks like I’m a 0 tier user on Kraken at the moment.

Have you really tried via https://changelly.com/? It is WAY too easy! Just place how much you have, they calculate how much you get, you write the receiving address, and they give you the address where you have to send money.

For example, you place 1 ZEC to LTC, and you get around 2.5 LTC exchange rate. Then you write the LTC address where you want to receive the LTC. Then, they give you the ZEC t address where you have to send the 1 ZEC, and you place this address in your ZCash4Win Software (make sure you have 100% updated the blockchain). And then if you go to history (good idea you create an account in Changelly to see your historical exchanges), you will see all in action. When they receive the 1 ZEC, when they exchange, and when they deposit the 2.5 LTC.

I have tried so many exchanges… all of them are more trading platforms… this seems to be the only “easy” option, and they really give you a very good exchange rate!

And do not be afraid to “play” with it. If you do not complete an exchange, it will just expire and you can create a new one.

I was confused by this… “Enter the recipient’s BTC address (your Bitcoin wallet)” since I don’t have a bitcoin address. Is it my Flypool Miner address? …
… edit… using that, say’s invalid address.

…edit… ah… I see create new btc address on coinbase… I’ll try over there and see what happens.

btw. big thanks for your help meem

If you are converting ZEC to BTC, you need to enter your recipient BTC Address from your BTC Wallet. I honestly do not operate BTC as much as possible since you need to pay 1-2 mBTC fee and take hours to confirm. Most Exchanges accept LTC so I am using that just to move ZEC around.

Good luck!

Good evening, I’ve a problem with zcash4win v1.0.12 and Windows 10
Whenever I try to launch zcash4win it does nothing…

Do you know a way to sove this problem? I’ve tried to reinstall zcash4win several times, but the problems is still here :disappointed_relieved:

Try running as an administrator, also look at Windows smartscreen it might be disabling it thinking it’s malware

Thanks for the reply

I tried, but no difference
I’ve also tried to run it in compatibility mode (windows 7 or windows 8/8.1), but without success

I have a weak PC. For more than 6 days, I’m waiting for the launch of a purse. This is normal? Win7x64

Screenshot_11

Can you post the last 50 or so lines of %AppData%\Zcash\debug.log please?

1 Like

See:

2006-12-31 14:02:24 Zcash version v1.0.11-a527ab6 (2017-08-23 01:11:01 +0000)
2006-12-31 14:02:24 Using OpenSSL version OpenSSL 1.1.0d 26 Jan 2017
2006-12-31 14:02:24 Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
2006-12-31 14:02:24 Default data directory C:\Users\Mi1\AppData\Roaming\Zcash
2006-12-31 14:02:24 Using data directory C:\Users\Mi1\AppData\Roaming\Zcash
2006-12-31 14:02:24 Using config file C:\Users\Mi1\AppData\Roaming\Zcash\zcash.conf
2006-12-31 14:02:24 Using at most 125 connections (2048 file descriptors available)
2006-12-31 14:02:24 Using 2 threads for script verification
2006-12-31 14:02:24 scheduler thread start
2006-12-31 14:02:24 Loading verifying key from C:\Users\Mi1\AppData\Roaming\ZcashParams\sprout-verifying.key
2006-12-31 14:02:24 Loaded verifying key in 0.015625s seconds.
2006-12-31 14:02:26 libevent: getaddrinfo: no address associated with nodename
2006-12-31 14:02:26 Binding RPC on address ::1 port 8232 failed.
2006-12-31 14:02:26 HTTP: creating work queue of depth 16
2006-12-31 14:02:26 HTTP: starting 4 worker threads
2006-12-31 14:02:26 Using wallet wallet.dat
2006-12-31 14:02:26 init message: Verifying wallet…
2006-12-31 14:02:26 CDBEnv::Open: LogDir=C:\Users\Mi1\AppData\Roaming\Zcash\database ErrorFile=C:\Users\Mi1\AppData\Roaming\Zcash\db.log
2006-12-31 14:02:26 Bound to [::]:8233
2006-12-31 14:02:26 Bound to 0.0.0.0:8233
2006-12-31 14:02:26 Cache configuration:
2006-12-31 14:02:26 * Using 2.0MiB for block index database
2006-12-31 14:02:26 * Using 32.5MiB for chain state database
2006-12-31 14:02:26 * Using 65.5MiB for in-memory UTXO set
2006-12-31 14:02:26 init message: Loading block index…
2006-12-31 14:02:26 Opening LevelDB in C:\Users\Mi1\AppData\Roaming\Zcash\blocks\index
2006-12-31 14:02:27 Opened LevelDB successfully
2006-12-31 14:02:27 Opening LevelDB in C:\Users\Mi1\AppData\Roaming\Zcash\chainstate
2006-12-31 14:02:27 Opened LevelDB successfully
2006-12-31 14:03:31 LoadBlockIndexDB: last block file = 62
2006-12-31 14:03:31 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=249, size=16846670, heights=239529…239776, time=2017-12-19…2017-12-20)
2006-12-31 14:03:31 Checking all blk files are present…
2006-12-31 14:03:32 LoadBlockIndexDB: transaction index disabled
2006-12-31 14:03:32 LoadBlockIndexDB: hashBestChain=0000000014fdb813fb355938cb16e77d6deb843383764e7111a723b29859eed2 height=239776 date=2017-12-20 01:32:46 progress=-0.168562
2006-12-31 14:03:32 *** This version has been deprecated as of block height 239776. You should upgrade to the latest version of Zcash. To disable deprecation for this version, set -disabledeprecation=1.0.11.
2006-12-31 14:03:32 Error: This version has been deprecated as of block height 239776. You should upgrade to the latest version of Zcash. To disable deprecation for this version, set -disabledeprecation=1.0.11.
2006-12-31 14:03:32 init message: Verifying blocks…
2006-12-31 14:03:32 Verifying last 288 blocks at level 3
2006-12-31 14:03:32 ERROR: CheckBlockHeader(): block timestamp too far in the future
2006-12-31 14:03:32 ERROR: VerifyDB(): *** found bad block at 239776, hash=0000000014fdb813fb355938cb16e77d6deb843383764e7111a723b29859eed2

2006-12-31 14:03:32 : Corrupted block database detected.
Please restart with -reindex to recover.
2006-12-31 14:03:32 Aborted block database rebuild. Exiting.
2006-12-31 14:03:32 Shutdown: In progress…
2006-12-31 14:03:32 StopRPC: waiting for async rpc workers to stop
2006-12-31 14:03:32 StopNode()
2006-12-31 14:03:32 scheduler thread interrupt
2006-12-31 14:03:32 Shutdown: done
2018-01-10 05:10:29

2018-01-10 05:10:29 Zcash version v1.0.11-a527ab6 (2017-08-23 01:11:01 +0000)
2018-01-10 05:10:29 Using OpenSSL version OpenSSL 1.1.0d 26 Jan 2017
2018-01-10 05:10:29 Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
2018-01-10 05:10:29 Default data directory C:\Users\Mi1\AppData\Roaming\Zcash
2018-01-10 05:10:29 Using data directory C:\Users\Mi1\AppData\Roaming\Zcash
2018-01-10 05:10:29 Using config file C:\Users\Mi1\AppData\Roaming\Zcash\zcash.conf
2018-01-10 05:10:29 Using at most 125 connections (2048 file descriptors available)
2018-01-10 05:10:29 Using 2 threads for script verification
2018-01-10 05:10:29 Loading verifying key from C:\Users\Mi1\AppData\Roaming\ZcashParams\sprout-verifying.key
2018-01-10 05:10:29 Loaded verifying key in 0.000000s seconds.
2018-01-10 05:10:29 scheduler thread start
2018-01-10 05:10:32 libevent: getaddrinfo: no address associated with nodename
2018-01-10 05:10:32 Binding RPC on address ::1 port 8232 failed.
2018-01-10 05:10:32 HTTP: creating work queue of depth 16
2018-01-10 05:10:32 HTTP: starting 4 worker threads
2018-01-10 05:10:32 Using wallet wallet.dat
2018-01-10 05:10:32 init message: Verifying wallet…
2018-01-10 05:10:32 CDBEnv::Open: LogDir=C:\Users\Mi1\AppData\Roaming\Zcash\database ErrorFile=C:\Users\Mi1\AppData\Roaming\Zcash\db.log
2018-01-10 05:10:32 Bound to [::]:8233
2018-01-10 05:10:32 Bound to 0.0.0.0:8233
2018-01-10 05:10:32 Cache configuration:
2018-01-10 05:10:32 * Using 2.0MiB for block index database
2018-01-10 05:10:32 * Using 32.5MiB for chain state database
2018-01-10 05:10:32 * Using 65.5MiB for in-memory UTXO set
2018-01-10 05:10:32 init message: Loading block index…
2018-01-10 05:10:32 Opening LevelDB in C:\Users\Mi1\AppData\Roaming\Zcash\blocks\index
2018-01-10 05:10:32 Opened LevelDB successfully
2018-01-10 05:10:32 Opening LevelDB in C:\Users\Mi1\AppData\Roaming\Zcash\chainstate
2018-01-10 05:10:32 Opened LevelDB successfully
2018-01-10 05:14:51 LoadBlockIndexDB: last block file = 62
2018-01-10 05:14:51 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=249, size=16846670, heights=239529…239776, time=2017-12-19…2017-12-20)
2018-01-10 05:14:51 Checking all blk files are present…
2018-01-10 05:14:52 LoadBlockIndexDB: transaction index disabled
2018-01-10 05:14:52 LoadBlockIndexDB: hashBestChain=0000000014fdb813fb355938cb16e77d6deb843383764e7111a723b29859eed2 height=239776 date=2017-12-20 01:32:46 progress=0.964689
2018-01-10 05:14:52 *** This version has been deprecated as of block height 239776. You should upgrade to the latest version of Zcash. To disable deprecation for this version, set -disabledeprecation=1.0.11.
2018-01-10 05:14:52 Error: This version has been deprecated as of block height 239776. You should upgrade to the latest version of Zcash. To disable deprecation for this version, set -disabledeprecation=1.0.11.
2018-01-10 05:14:52 init message: Verifying blocks…
2018-01-10 05:14:52 Verifying last 288 blocks at level 3
2018-01-10 05:15:00 Shutdown requested. Exiting.
2018-01-10 05:15:00 Shutdown: In progress…
2018-01-10 05:15:00 StopRPC: waiting for async rpc workers to stop
2018-01-10 05:15:00 StopNode()
2018-01-10 05:15:01 scheduler thread interrupt
2018-01-10 05:15:01 Shutdown: done

Maybe I should stop the program and get new logs?

First of all, upgrade to the v12 see if the problem goes away.

1 Like

Thank you! Now good work.

Почему не отправляет перевод! IMG_0958|666x500

Is there a way to limit bandwidth used by the wallet? Over 800GB used last month pushed me over ISP limit and now I am only turning on occasionally to update but this doesn’t help the network.

Network usage stats:

(a few days after I started manually throttling)

I suspect this is because the wallet needed to download a large chunk of
the blockfile (new wallet, perhaps?). I guess this is not normal if your
wallet is fully synced.

Right now this issue hits zcash and all its (and most other bitcoin) forks.
In my experience if you fire up your wallet every day or two it just takes
a few minutes to sync to 100%, and then the outbound bandwidth won’t kill
you

Thanks for the reply, but no, this is not a new wallet. It’s been running nearly full time and staying synched for >9 months (plus the full history is nowhere near 800GB). According to my ISP, bandwidth usage has been very high the whole time, but didn’t go over my limit until last month which prompted me to check what application was the culprit.

Anyone else letting their wallet stay open all the time check bandwidth usage (Windows/Settings/Network&Internet/Data usage/view usage details)? I was trying to be supportive by leaving it running, but won’t be able to do so until there is a way to limit traffic.