I searched a lot in the forum and on the Internet but doesn’t seem to understand a few things.
In short - I started mining in late 2017 and stopped at the beginning of 2018, using the zcash4win desktop wallet and the zcash.flypool.org pool. Then I sold most of the rig components and only recently decided to connect the rig again and transfer what I already mined. I found out that zcash4win is not supported anymore and ZECwallet is its successor. However, I tried the latest versions of Lite and Fullnode but with no success. Than, I saw that the only thing I need is the wallet.dat file, copied it and pasted it on another PC, in folder CurrentUsers/AppData/Roaming/Zcash. I installed the FullNode version of ZECwallet and for nearly two days of syncing, the progress is only 5%. What is more bothering is that my balance is currently zero. I can see the outgoing transactions that were made from the wallet, so the wallet.dat file is surely recognizable but I’m wondering why the balance is zero and if the whole 100% should be synced before anything appears on it. I’m also wondering if the old miner should be active during this syncing or not. The last thing I’m not sure of is whether I can even do this on another PC or this must be done on the original rig.
If anybody could help here, I would much appreciate it.
This is correct, depending on when you made your transaction (blockheight of the tx) your balance will not show up until the node is 100% synced.
Also, when you install ZecWallet Fullnode the first time it created it’s own empty wallet.dat. after it syncs if the funds don’t show, try to replace the wallet.dat with your old one to be sure it wasn’t overwritten, then perform a -rescan and your funds should show.
Hey Shawn (or anybody who could also help here) - I took the last rows of the debug file, containing info about my attempt to start ZECWallet on my old rig. Would be able to take a look and maybe point me at a possible action please? I would really like to spare myself the extra days I would have to wait for the sync on the other PC. Thanks!
Dec 03 16:58:12.036 INFO main: Zcash version v4.1.1 (2020-11-16 18:45:38 +0000)
Dec 03 16:58:12.046 INFO Init: main: Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
Dec 03 16:58:12.046 INFO Init: main: Default data directory C:\Users\trimata\AppData\Roaming\Zcash
Dec 03 16:58:12.046 INFO Init: main: Using data directory C:\Users\trimata\AppData\Roaming\Zcash
Dec 03 16:58:12.046 INFO Init: main: Using config file C:\Users\trimata\AppData\Roaming\Zcash\zcash.conf
Dec 03 16:58:12.046 INFO Init: main: Using at most 125 connections (2048 file descriptors available)
Dec 03 16:58:12.046 INFO Init: main: Using 2 threads for script verification
Dec 03 16:58:12.046 INFO Init: main: Loading Sapling (Spend) parameters from C:\Users\trimata\AppData\Roaming\ZcashParams\sapling-spend.params
Dec 03 16:58:12.046 INFO Init: main: Loading Sapling (Output) parameters from C:\Users\trimata\AppData\Roaming\ZcashParams\sapling-output.params
Dec 03 16:58:12.046 INFO Init: main: Loading Sapling (Sprout Groth16) parameters from C:\Users\trimata\AppData\Roaming\ZcashParams\sprout-groth16.params
Dec 03 16:58:12.046 INFO main: scheduler thread start
Dec 03 16:58:14.493 INFO Init: main: Loaded Sapling parameters in 2.437916s seconds.
Dec 03 16:58:14.583 INFO Init: main: HTTP: creating work queue of depth 16
Dec 03 16:58:14.584 INFO Init: main: Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
Dec 03 16:58:14.584 INFO Init: main: HTTP: starting 4 worker threads
Dec 03 16:58:14.586 INFO Init: main: Using wallet wallet.dat
Dec 03 16:58:14.587 INFO Init: main: init message: Verifying wallet…
Dec 03 16:58:14.588 INFO Init: main: CDBEnv::Open: LogDir=C:\Users\trimata\AppData\Roaming\Zcash\database ErrorFile=C:\Users\trimata\AppData\Roaming\Zcash\db.log
Dec 03 16:58:15.558 INFO Init: main: Bound to [::]:8233
Dec 03 16:58:15.559 INFO Init: main: Bound to 0.0.0.0:8233
Dec 03 16:58:15.559 INFO Init: main: Cache configuration:
Dec 03 16:58:15.559 INFO Init: main: * Using 2.0MiB for block index database
Dec 03 16:58:15.559 INFO Init: main: * Using 120.0MiB for chain state database
Dec 03 16:58:15.559 INFO Init: main: * Using 328.0MiB for in-memory UTXO set
Dec 03 16:58:15.559 INFO Init: main: init message: Loading block index…
Dec 03 16:58:15.563 INFO Init: main: Opening LevelDB in C:\Users\trimata\AppData\Roaming\Zcash\blocks\index
Dec 03 16:58:15.598 INFO Init: main: Opened LevelDB successfully
Dec 03 16:58:15.598 INFO Init: main: Opening LevelDB in C:\Users\trimata\AppData\Roaming\Zcash\chainstate
Dec 03 16:58:15.628 INFO Init: main: Opened LevelDB successfully
Dec 03 16:58:15.632 INFO Init: main: LoadBlockIndexDB: last block file = 0
Dec 03 16:58:15.634 INFO Init: main: LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0…0, time=1970-01-01…1970-01-01)
Dec 03 16:58:15.634 INFO Init: main: Checking all blk files are present…
Dec 03 16:58:15.634 INFO Init: main: LoadBlockIndexDB: transaction index disabled
Dec 03 16:58:15.634 INFO Init: main: LoadBlockIndexDB: insight explorer disabled
Dec 03 16:58:15.634 INFO Init: main: LoadBlockIndexDB: light wallet daemon disabled
Dec 03 16:58:15.644 INFO Init: main: Initializing databases…
Dec 03 16:58:15.658 INFO Init: main: Pre-allocating up to position 0x1000000 in blk00000.dat
Shawn: thanks a lot for your help, I’m updating as promised and logging this here in case a similar case appears.
Zcash4win->ZECWallet - if somebody installs zecwallet on another PC, all you need is your original wallet.dat file. Create a folder in C:/Users/CurrentUser/AppData/Roaming and name it Zcash. Paste the walled.dat file inside. When ZECWallet is first installed, tick the enable fast sync option. The blockchain is chronologically read and depending on when you mined, it will update your balance accordingly (mine started showing up exactly when blocks from end of 2017 were being read - that can be seen in real time in the debig.log file, located in the same Zcash folder). What I found out is that closing and re-opening the ZECWallet app from time to time helped in increasing the read speed (maybe because I’m using the laptop for other stuff and the CPU priority is changed - do this close/re-open just before going to sleep - this will ensure higher reading speed).
When I saw this post, I tried Windows again, and the result was still the same.
If you manually interrupt the program while synchronizing the data block, an error will occur after restarting, and you will be prompted to view the log
Without interruption, the data block is synchronized to about 50%, and the same error message will appear