I have downloaded and installed ZecWallet for both windows and mac os. I have got really bad user experience with the ZecWallet software. When i imported private key into the software, I got the alert box telling me that “the private key imported successfully”, but the balance is not synchronized. I have got two different balances in windows and mac os, which are not right balance either. Has someone meet the same problem?
Is the blockchain fully synced for both your installations?
Yes. It took quiet a while to sync fully. I know that, the problem happen after that. I check the balance with https://zcha.in/ as well.
You may need to
rescan to have your node reindex the Blockchain to find your funds if you imported the keys after it had already synced.
There is a way to start the Zcashd with the
-rescan flag using the command line, but it depends how your system is configured.
For instance on Mac zcashd is in:
reindex per Gareths recommendation
Keep in mind that when you import the private key, the key is not imported instantly. It can take from several minutes to hours (depending on your hardware) for the process to finish due to blockchain rescanning in the background.
Are you still seeing the issue, now that 6 hours have passed?
A rescan would actually be the best first step and will likely cure this and a reindex would be a last resort as it entails re-downloading the entire blockchain.
Long story short though it’s just starting
zcashd with a
rescan option so
As per that issue I think we could make this a lot easier with support in ZecWallet as this is a pretty common issue.
I am trying rescan right now, and already took 10 minutes. How long does it usually take to rescan?
@Shawn @garethtdavies @anon16456014 zcashd -rescan worked. For people without computer background, the ZecWallet software still need to be refined. Correct balance should always show after importing private key without users doing anything.
This makes absolutly sense. This is exactly one of the problems that hinder large adoption an usage. For devs and people familar to to wallets, crypto in general it’s an easy task. But for people new or with less knowledge with computing, software, wallets, whatever it’s something it’s a big burden.
Such things like an automatic rescan when importing private keys should be done just automaticaly to ensure people don’t run into problems that can be solved only with advanced computer/wallet knowledge.
Just to be clear, this does happen by default z_importkey - Zcash 4.5.1-1 RPC Docs which is why importing a key typically takes a while. I’ve never tried to reproduce but I guess when you do the private key import relative to the sync progress matters. Maybe in addition to the ideas in that issue helping users perform a rescan, any importing of keys in ZecWallet is restricted until the node is fully synced (if that indeed is the issue).
I have tried importing again, and noticed the message as above. However, the User interface does not remind me the rescan is being processed. It does not show me the progress of the rescan either. Sometime people may not be patient to quit the Wallet, and I guess the rescan process would be terminated. When Wallet is relaunched, the rescan may not continue so that wrong balance is shown with the transactions partially rescanned. Please correct me if I got something wrong. but in general, the user experience of the Wallet really needs to be improved.
Yes, agreed but ultimately a lot of this is dependent on the functionality of the underlying zcashd so there are limits to what can be accomplished. Large wallet rescans for example can take a huge amount of time (days) but there is some research to improve it: Research Spike for Large t-addr Wallet Performance Improvements · Issue #3889 · zcash/zcash · GitHub
Still there are some good suggestions and minor tweaks that can be made to improve things with ZecWallet. Copying @adityapk00 (ZecWallet dev) to make sure he sees this thread but also opening an issue here: Issues · ZcashFoundation/zecwallet · GitHub to suggest stuff would also be very welcome!
Issue submitted in github already.