You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using Zcash Wallet for windows since 2018. Every three months an update has been required. These update seem to have included predetermined obsolescence at a pre-determined block height.
With the latest series of updates since 1.8.1, we have not been able to run the wallet or restore from exported keys.
This is maddening and we are still mining to the original wallet address.
In all previous updates, only an installation of the update was needed. We did not need to update the wallet.dat file.
We have a copy of the "wallet.dat" file and the exported private keys from the previous versions that worked.
We need to know how to restore the wallet functionality and have access to our coin/wallet.
I am not an expert user. I only know that every other desktop wallet updates from time to time. None however, have required this frequency of updates.
Any advice you may have would be greatly appreciated.
Michael
The text was updated successfully, but these errors were encountered:
We have been using Zcash Wallet for windows since 2018. Every three months an update has been required. These update seem to have included predetermined obsolescence at a pre-determined block height.
With the latest series of updates since 1.8.1, we have not been able to run the wallet or restore from exported keys.
This is maddening and we are still mining to the original wallet address.
In all previous updates, only an installation of the update was needed. We did not need to update the wallet.dat file.
We have a copy of the "wallet.dat" file and the exported private keys from the previous versions that worked.
We need to know how to restore the wallet functionality and have access to our coin/wallet.
I am not an expert user. I only know that every other desktop wallet updates from time to time. None however, have required this frequency of updates.
Any advice you may have would be greatly appreciated.
Michael
The text was updated successfully, but these errors were encountered: