0 Members and 1 Guest are viewing this topic.
Quote from: liondani on October 07, 2015, 09:53:49 pmQuote from: Louis on October 07, 2015, 09:16:53 pmThe log file is dated 10/6/2015, it's in this folder: BitShares/wallets/default/000080.log and it's 192KBso it is not exposed from v0.9.3c since this version is released this month....it is an old log file that was created back in June where the old wallet was installed...So since it is not related with the last version I am not worried too much edit:+ as xeroc mentioned it has BTS on the beginning.... so no private key (I was also confused )I am sorry for the mixed up, but the date is not Jun 10, 2015 but Oct 6, 2015, this was generated by v0.9.3c yesterday.The owner_key starts with 5bts... I am just hoping that is not my private keys
Quote from: Louis on October 07, 2015, 09:16:53 pmThe log file is dated 10/6/2015, it's in this folder: BitShares/wallets/default/000080.log and it's 192KBso it is not exposed from v0.9.3c since this version is released this month....it is an old log file that was created back in June where the old wallet was installed...So since it is not related with the last version I am not worried too much edit:+ as xeroc mentioned it has BTS on the beginning.... so no private key (I was also confused )
The log file is dated 10/6/2015, it's in this folder: BitShares/wallets/default/000080.log and it's 192KB
have you a delegate? Have you ever used the command:wallet_delegate_set_block_production <account name> TRUE?
Even with 0.9.3c I found my private key in one of the log files, that's very strange, why would a private key be exposed like that?
Quote from: liondani on October 01, 2015, 06:52:27 pmwith your backup .json file and your password you will recover on any computer your account...with the key you found as far as i know you can NOT do the recover (it's just a public key, at least I think so), it is not your secret key. The wallet don't expose anywhere your secret keys in plain text (it is only encrypted inside your .json backup file). Waiting xeroc to confirm this To clarify:public keys (worthless) start with "BTS...."private keys (to spend your funds) start with "5...."
with your backup .json file and your password you will recover on any computer your account...with the key you found as far as i know you can NOT do the recover (it's just a public key, at least I think so), it is not your secret key. The wallet don't expose anywhere your secret keys in plain text (it is only encrypted inside your .json backup file). Waiting xeroc to confirm this
index idA name xxxxpublic_datagui_datawebsite owner_key5BTS5XXXXXXXXXXXXXXXXXXXXXX2Saactive_key_history2014-09-02T04:46:205BTS5XXXXXXXXXXXXXXXXXXXXXX2Saregistration_date2014-09-02T04:46:20last_update2014-09-02T04:46:20 meta_datatypetitan_accountdata last_child_key_index block_production_enabled custom_data approved Aò}ÓÒí index idA] name xxxxxpublic_datagui_datawebsite
QuoteThe log file is dated 10/6/2015, it's in this folder:BitShares/wallets/default/000080.log and it's 192KBHmm .. very odd .. can you paste the suroundings of the priv key please (do obfuscatethe privkey)
The log file is dated 10/6/2015, it's in this folder:BitShares/wallets/default/000080.log and it's 192KB
$BTS5QXXXXXXXXXXXXXXXXXXXXXDamountÐüz claim_input_data typedeposit_op_typedataamount€9z conditionasset_id slate_id typewithdraw_signature_typedataowner$BTS1XXXXXXXXXXXXXXXXZWmemoone_time_key5BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXtQaQencrypted_memo_data€20f1e157b5380a61578d6daddf82768aeef749a6c2bda652b810c4b065596df4372a0c253042e7f9da4546072b3c22959da640d4f4b0d16c8ee51b90bd0e0f49signatures‚2010e909d8ba62740aae6973ef0694e7ad7d9dc410508b0e88c78b8c55858f35450885b2df12e39b24621f955a739cce9e60c3115eb0048a5cfb31b09c7dd0c310ledger_entriesfrom_account5BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX8to_account5BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2Saamountamount€9z asset_id memomemo9feeamountPà asset_id created_time2015-10-07T08:30:30received_time2015-10-07T08:30:30æˆ!â\ ¶ Iindex key"last_unlocked_scanned_block_numbervalue¦¢9 P<Q\ · Iindex key"last_unlocked_scanned_block_numbervalue¨¢9 Ôpˆ\ ¸ Iindex key"last_unlocked_scanned_block_numbervalue©¢9 —@!&\ ¹ Iindex key"last_unlocked_scanned_block_numbervalueª¢9 qW/c\ º Iindex key"last_unlocked_scanned_block_numbervalue«¢9 ¹éôD\ » Iindex key"last_unlocked_scanned_block_numbervalue¬¢9 ÆG•ä\ ¼ Iindex key"last_unlocked_scanned_block_numbervalue¢9 …w˜Æ\ ½ Iindex key"last_unlocked_scanned_block_numbervalue®¢9 c ª \ ¾ Iindex key"last_unlocked_scanned_block_numbervalue¯¢9 A–ªÁ\ ¿ Iindex key"last_unlocked_scanned_block_numbervalue°¢9 [Q·\ À Iindex key"last_unlocked_scanned_block_numbervalue±¢9 ˜¡¶´\ Á Iindex
The link that you provided says to use the wallet_export_key command, isthat the same as exporting my wallet from the menu (Export Wallet)?
Quote from: Louis on October 07, 2015, 04:15:43 amQuoteONE FINAL STEP:export NOW a backup .json wallet from your current wallet 0.9.3c (and keep the new .json file safe on 2 devices) because THAT .json file will be the compatible import file for graphene(bts2.0)!I am still transferring funds from the exchange over to my wallet. Do I need to make one final backup of my wallet after the final transfer? or does it matter?Do I also need to make a backup of my keys also, with the wallet_export_key command in the console?If you do not expect any funds to receive untill the snapshot you are safe withyour current export:http://docs.bitshares.eu/migration/howto-exporting-wallet.htmlQuoteQuotePS when you are synced I suggest you make one more account on your wallet and move all your funds there since you found a secret key in plain text on your computer... (that way the wallet will use a new secret key for the new account that will not get exposed like the last one,just in case)Even with 0.9.3c I found my private key in one of the log files, that's very strange, why would a private key be exposed like that?How old is that log file. Cant find any priv keys in mine!
QuoteONE FINAL STEP:export NOW a backup .json wallet from your current wallet 0.9.3c (and keep the new .json file safe on 2 devices) because THAT .json file will be the compatible import file for graphene(bts2.0)!I am still transferring funds from the exchange over to my wallet. Do I need to make one final backup of my wallet after the final transfer? or does it matter?Do I also need to make a backup of my keys also, with the wallet_export_key command in the console?
ONE FINAL STEP:export NOW a backup .json wallet from your current wallet 0.9.3c (and keep the new .json file safe on 2 devices) because THAT .json file will be the compatible import file for graphene(bts2.0)!
QuotePS when you are synced I suggest you make one more account on your wallet and move all your funds there since you found a secret key in plain text on your computer... (that way the wallet will use a new secret key for the new account that will not get exposed like the last one,just in case)Even with 0.9.3c I found my private key in one of the log files, that's very strange, why would a private key be exposed like that?
PS when you are synced I suggest you make one more account on your wallet and move all your funds there since you found a secret key in plain text on your computer... (that way the wallet will use a new secret key for the new account that will not get exposed like the last one,just in case)
GOOD NEWS!!!!I downloaded 0.9.3c and I was able to import my .json file and I was able to get it, with my normal password no problem. I just need to sync the wallet.THANK YOU ALL so much for walking me through this.
Just to be sure, a person can slap the v0.92 chain folder under v0.93 correct? (to help sync faster)
Meanwhile under the /wallet/default of (0.9.2 installed on July 10, 2015) , I found a file called 000197.log (dated 7/24/2015) that shows the name of my account and "owner_key" that starts with 5bts5...... all together there are 54 characters, it is followed by registration_date, last_update and a whole bunch of other stuff, the whole file is 192k.
I am confident I have a good backup of the .json wallet file. What I think I need is my recovery key, just in case, can I get this from my old wallet once I login?If I do find my recovery key can I use that to recover my account on another computer if need be?Do you know if the owner_key fond on the file I mentioned earlier is the key I need to recover my account?Thanks again
I am confident I have a good backup of the .json wallet file. What I think Ineed is my recovery key, just in case, can I get this from my old wallet once Ilogin?If I do find my recovery key can I use that to recover my account on another computer if need be?
Do you know if the owner_key fond on the file I mentioned earlier is the key Ineed to recover my account?
But I am afraid that if I installed 0.9.3c it might overwrite something on 0.9.2, should I be concern about that?Or should I do what Xeroc said on 0.9.2, the upgrade to 0.9.3c?BTW the older version is about 10 to 20 minutes from finishing syncing, I should be able to login with my password, would it be worth it just in case my password did change?Thank you so much for putting up with my issue.
Hi Xeroc,I have tried "open default" and I get this:10001 level_map_failure: level_map open failureFailure opening database c:/Users/..../AppData/Roaming/BitShares/wallets/defaultStatus: Curruption: checksum mismatch {"db"::"C:/Users/..SAME PATH/default","msg":Corruption checksum mismatch"}So it might not be a problem with the password, but some corrupted file.What can I do at this point?
Liondani I really appreciate you replies.I just noticed that I may be entering the password correctly, however the wallet (0.9.1) does not give me any indication that I have entered the wrong password, I don't get any error message at all. All it does after I've entered my password is come up with 3 circles that grow from left to right and right to left for about 4 seconds, then I enter another password the three circles appear for a fraction of a second.Shouldn't I be getting a "wrong password" message or something?PS: I did find a backup from Sep 1, 2014, named: Bitshare X Wallet Backup.json
If I remember correctly there is a known bug for older backups that displays "incorect password" or something like that, installing version 0.5.3(if I remember correctly) and importing the wallet and then upgrading to the latest version could solve this, but I don't know if this is what is happening to you
I had downloaded Bitshares 0.9.1 back in July. I synced it and it was up to date.I do have a json backup of my wallet from Frebruary 2015I bought a new computer and am in the process of downloading 0.9.3c.I don't remember changing the password on my current wallet, when I try to login with my normal password it is not letting me in.Is there a way to recover my account with the February json file that I have after installing Bishares 0.9.3c on my new computer?Is there a limit to the password login attemps one can use?Thank you,EDIT: I did find a json backup prior to installing 0.9.1 in July 10th 2015
Thanks for you reply Xeroc.On other question: Let's say that I find my password a week or a month after the 2.0 release, would I be able to still try to use the 0.9.1 wallet to access my account?
Thanks Riverhead and Triglodactyl for your suggestions.are there instructions on how to go about using a dictionary or a brute force strategy?Or do you mean to just create my own dictionary and just try it one by one?
Thanks for your response Troglodactyl,If I am not able to remember my password is there a way to get it back with just the Json backup?