BitShares Forum
Main => Technical Support => Topic started by: anycoin on December 15, 2014, 04:41:22 am
-
My client started reporting all transaction dates in the year 1969 and I was not recieving shares some time ago. After checking here I saw that my client needed upgrading and that the current release had some problems. I waited and installed .04.2.6 I believe is the number. It is the latest release as of 12/14. I am using opensuse linux 64bit. After recieving the errors I renamed my old bitshare directory and let it rebuild the .bitshares. I ran the QT interface and it asked for new password etc. Which I set it to the same password as before. I then attempted to import the wallet file and it asked for a passphrase...........I do not remember ever
creating a passphrase......this is the first problem..lol. It of course would not let me continue and Im dead...The QT interface did not acknowledge the upgrade either so I assume I have to reinstall that also. So, to simplify this here are my questions.
1) How to recover my bitshares
2) do I need to rebuild the QT wallet or can it be done yet for (Linux)
3) What in the world did I do wrong here??
Thank-you for the assistance.
-
you are using the most recent version 0.4.26 ???
-
Which I set it to the same password as before. I then attempted to import the wallet file and it asked for a passphrase...........I do not remember ever
creating a passphrase......this is the first problem..lol.
Did you move your old wallet directory into .bitshares/wallets directory or did you import wallet backup json file? Either way you need to provide the password that your original wallet was created with.
-
Found a yast installable qt version and it read my old wallet ok......I did provide the correct password the cli version was giving me a headache but the qt read my wallet file ok....next problem is its showing transactions but a 0 balance. I assume because it needs to download the blockchain.
-
you can check the progress with "getinfo" in the console .. the interesting lines say something like block_head_last ... the time tells you how far back the last block is synced ... everything above 10 to 20 secs indicates that you have not synced completely yet