Zcash4win BETA is out!

yup, if you check the end of the logfile at %AppData%\Zcash\debug.log it shows progress= where is a FRACTION, not a percent, so for instance progress=0.9700000 is 97% and 1.00000 is 100% synced

so you can check how far along it is, if it is having trouble or not, etc by checking the end of that file every now and then, and once it is close to 100% fire up the GUI while leaving it running

if there is a running zcashd on the rpc port, it does NOT fire it up on its own

@kbill and @IB76 and anyone else who’s zcashd is “stuck” (and this bit of advice goes for windows, linux AND mac! on arm64 or intel!) needs to check your logfile when launching on the command line as above and see if it is actually stuck/crashed or if lines with progress= are still coming in…because there are some patches of blocks that take almost the whole block interval to verify (google the “bitcoin quadratic verification problem”, sigh, which zcash inherited from upstream bitcoin 0.11.2)

what that means is that there are some blocks that take 2.5 minutes or more to VERIFY, which is the time between blocks, so when you are verifying those stretches of the blockchain in the past, new blocks come in every 2.5 minutes on average while it is taking you up to 2.5 minutes to verify past ones you are still syncing

once it gets past those bits you don’t need to sync them again, and if you launch it at least every few days it should only take a few minutes to get back to 100%

but when its verifying those blocks, it LOOKS like it is “stuck”, while in reality your computer is merely Very Busy

1 Like

so please check your debug.log a few times over at least 10-15 minutes and see if the end of the file has new lines coming in or not

it PROBABLY still does and as the man says, “first thing you learn is that you always gotta wait”

but NO MATTER WHAT, so long as you have a textfile export of your private keys, you can always import them onto another node on a different version of Windows, zcash4win or a diff platform entirely.

the keys are the coins, nothing else matters!

Hey, I read a big part on this forum, buy nothing help
I’m using zcash4win-1.0.12.


Try in PowerShell
and last

2017-12-23 20:57:24 Zcash version v1.0.12-d6c5478-dirty (2017-10-29 22:17:43 +0000)
2017-12-23 20:57:24 Using OpenSSL version OpenSSL 1.1.0d 26 Jan 2017
2017-12-23 20:57:24 Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
2017-12-23 20:57:24 Default data directory C:\Users\Asus\AppData\Roaming\Zcash
2017-12-23 20:57:24 Using data directory C:\Users\Asus\AppData\Roaming\Zcash
2017-12-23 20:57:24 Using config file C:\Users\Asus\AppData\Roaming\Zcash\zcash.conf
2017-12-23 20:57:24 Using at most 125 connections (2048 file descriptors available)
2017-12-23 20:57:24 Using 4 threads for script verification
2017-12-23 20:57:24 scheduler thread start
2017-12-23 20:57:24 Loading verifying key from C:\Users\Asus\AppData\Roaming\ZcashParams\sprout-verifying.key
2017-12-23 20:57:24 Loaded verifying key in 0.010997s seconds.
2017-12-23 20:57:24 libevent: getaddrinfo: nodename nor servname provided, or not known
2017-12-23 20:57:24 Binding RPC on address ::1 port 8232 failed.
2017-12-23 20:57:24 HTTP: creating work queue of depth 16
2017-12-23 20:57:24 HTTP: starting 4 worker threads
2017-12-23 20:57:24 Using wallet wallet.dat
2017-12-23 20:57:24 init message: Verifying wallet…
2017-12-23 20:57:24 CDBEnv::Open: LogDir=C:\Users\Asus\AppData\Roaming\Zcash\database ErrorFile=C:\Users\Asus\AppData\Roaming\Zcash\db.log
2017-12-23 20:57:24 Bound to [::]:8233
2017-12-23 20:57:24 Bound to 0.0.0.0:8233
2017-12-23 20:57:24 Cache configuration:
2017-12-23 20:57:24 * Using 2.0MiB for block index database
2017-12-23 20:57:24 * Using 32.5MiB for chain state database
2017-12-23 20:57:24 * Using 65.5MiB for in-memory UTXO set
2017-12-23 20:57:24 init message: Loading block index…
2017-12-23 20:57:24 Opening LevelDB in C:\Users\Asus\AppData\Roaming\Zcash\blocks\index
2017-12-23 20:57:24 Opened LevelDB successfully
2017-12-23 20:57:24 Opening LevelDB in C:\Users\Asus\AppData\Roaming\Zcash\chainstate
2017-12-23 20:57:25 Corruption: error in middle of record
2017-12-23 20:57:25 : Error opening block database.
Please restart with -reindex to recover.
2017-12-23 20:57:25 Aborted block database rebuild. Exiting.
2017-12-23 20:57:25 scheduler thread interrupt
2017-12-23 20:57:25 Shutdown: In progress…
2017-12-23 20:57:25 StopRPC: waiting for async rpc workers to stop
2017-12-23 20:57:25 StopNode()
2017-12-23 20:57:25 Shutdown: done

First, you should carefully read what your powershell output tells you, see
the 7th line from the bottom?
I had the same so I read the log, started zcashd with a param like it
suggested and it worked.

tl;dr in cmd window type zcashd.exe -reindex

If it does not work, you can try adding 2 more params, -showmetrics=1
-daemon=0 but I doubt these are of any significance.

I see
Open zcashd.exe and its close at once.
Don t understand what I need to do ?!

Please go through this. For what it’s worth, I did not use power shell, just a plain cmd.exe (admin mode) and ran c:\Program Files\zcash4win\app>zcashd.exe -reindex

Hi, This folder doen’t has the file “zcashd.exe”.

the folder C:\Program Files\zcash4win has a “zcash4win.exe” file.

I’m using Windows 10 64bits.

Someone can fix it?

Thanks for helping guys.

If you’re missing zcashd, chances are something removed it or blocked it from installing. The most likely culprit is your AV software.

Below is the error I received from running Powershell last night.

2017-12-24 14:16:33 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2017-12-24 14:16:34 receive version message: /BeanStalk:1.0.12/: version 170002, blocks=242386, us=[2001:0:9d38:6ab8:2cf2:12de:e7f2:bf5c]:62369, peer=42
2017-12-24 14:16:34 Added time data, samples 27, offset -3 (+0 minutes)
2017-12-24 14:16:34 nTimeOffset = -2 (+0 minutes)
2017-12-24 14:17:21 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:17:56 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:19:31 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:21:11 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:24:27 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:26:16 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:27:42 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:30:58 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:31:01 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:32:06 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:34:39 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:38:34 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:39:20 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:44:55 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:47:28 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:51:57 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:55:51 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 14:59:14 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:02:19 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:03:02 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:03:33 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:03:52 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:06:27 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:07:09 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:08:48 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:13:29 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:17:18 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:18:52 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:21:19 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:22:03 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:25:19 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:27:30 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:28:33 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:31:48 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:34:33 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:35:03 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:37:18 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:38:18 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:38:52 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:40:12 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:41:35 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:44:51 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:45:49 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:48:08 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:49:08 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:57:29 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 15:57:39 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 16:02:13 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 16:03:03 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 16:05:59 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 16:08:27 ERROR: AcceptToMemoryPool: joinsplit requirements not met
2017-12-24 16:10:23 ERROR: AcceptToMemoryPool: joinsplit requirements not met

a general unexpected critical error has occurred : connection reset
help . win 10 x64

Hey Radix,
I have a bit of a niche issue. I have two drives on my computer, and the drive I wanted to install zcash4win on is not my C: Drive. Could you add the option to make it “portable”, allowing you to chose the primary install directory, and the block chain directory separate from the default values. I’ve fixed the issue using symbolic links, and it’s been working like a dream since. Thanks for the software
-Spy

This has been asked for by dozens of people in this thread. It is something that is planned to implement in some future release. Until then …

1 Like

it is planned tentatively for the next major release

1 Like

It is running on powershell and it says;
"downloading blocks 106551 / ~242920 (%43)
** “Connections 8”**
** " Network sloution rate 55880218 Sol/s**
** “You have validated 5965 transactions !”**

and it keeps validating transactions but it takes more than two minutes to validate next transaction. So I guess this is not stuck but very slow progress, do you think it may take a month to sync %100?

Thanks for all your support and happy holidays!

help plz .start zcash4win error ( a general unexpected critical error has occurred : connection reset

Dear radix42, I’ve done all the things mentioned earlier here for solution of my problem, but it seems nothing’s helping to work it out. And all the problems are exactly the same as the user IB76 has. When it got stuck on 44% according to debug.log it was due to this ERROR: AcceptToMemoryPool: joinsplit requirements not met and then after I started it with reindex it just crushed on bad checksum of block.
2017-12-25 10:03:18 Corruption: block checksum mismatch
2017-12-25 10:03:18 *** System error while flushing: Database corrupted
2017-12-25 10:03:18 Error: Error: A fatal internal error occurred, see debug.log for details
2017-12-25 10:03:18 Error: Failed to connect best block
So my question is - If I install the client on Ubuntu VM on Win will my wallet.dat or private keys exported file from Zcash4win work in linux client?

As long as you have your wallet.dat file and it is not corrupted, you should be fine.