BitShares Forum
Main => General Discussion => Topic started by: alt on August 30, 2014, 02:37:58 pm
-
I have made some trade with version 0.4.9 , then close the wallet.
when I open the wallet again, I found lost much balance.
then I found the private key is lost
baozi (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVAL BLOCK PRODUCTION ENABLED
baozi BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG 2014-07-20T00:59:10 NO 0 N/A
baozi (unlocked) >>> wallet_dump_private_key BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG
"key not found"
I restore from the backup json file when upgrade program.
the balance come again.
then I backup to a json file, and compile the 2 json files, I found lost many "key_record_type"
-
I have made some trade with version 0.4.9 , then close the wallet.
when I open the wallet again, I found lost much balance.
then I found the private key is lost
baozi (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVAL BLOCK PRODUCTION ENABLED
baozi BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG 2014-07-20T00:59:10 NO 0 N/A
baozi (unlocked) >>> wallet_dump_private_key BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG
"key not found"
I restore from the backup json file when upgrade program.
the balance come again.
then I backup to a json file, and compile the 2 json files, I found lost many "key_record_type"
Good find. I wonder if this is from the client crashes corrupting the local data files.
-
I have made some trade with version 0.4.9 , then close the wallet.
when I open the wallet again, I found lost much balance.
then I found the private key is lost
baozi (unlocked) >>> wallet_list_my_accounts
NAME (* delegate) KEY REGISTERED FAVORITE APPROVAL BLOCK PRODUCTION ENABLED
baozi BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG 2014-07-20T00:59:10 NO 0 N/A
baozi (unlocked) >>> wallet_dump_private_key BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG
"key not found"
I restore from the backup json file when upgrade program.
the balance come again.
then I backup to a json file, and compile the 2 json files, I found lost many "key_record_type"
Good find. I wonder if this is from the client crashes corrupting the local data files.
I am sure it's not because of crash, this happened every time when I just open another wallet, even not quit the client
-
here are some differ from json file(I have remove some private infomations)
"type": "balance_record_type", | "type": "key_record_type",
"data": { | "data": {
"index": 9, | "index": 9,
"balance": 100000000000, | "account_address": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"condition": { | A> "public_key": "BTSXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"asset_id": 0, | "encrypted_private_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"delegate_slate_id": 1132758749919219197, | "memo": null
"type": "withdraw_signature_type", | ---------------------------------------------------------------------------------
"data": { | ---------------------------------------------------------------------------------
"owner": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", | ---------------------------------------------------------------------------------
"memo": { | ---------------------------------------------------------------------------------
"one_time_key": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX| ---------------------------------------------------------------------------------
"encrypted_memo_data": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx| ---------------------------------------------------------------------------------
} | ---------------------------------------------------------------------------------
} | ---------------------------------------------------------------------------------
}, | ---------------------------------------------------------------------------------
"genesis_info": null, | ---------------------------------------------------------------------------------
"last_update": "20140829TXXXXXX" | ---------------------------------------------------------------------------------
} | }
}, | },
{ | {
"type": "balance_record_type", | "type": "transaction_record_type",
"data": { | "data": {
"index": 10, | "index": 10,
"balance": 300000000000, | "record_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"condition": { | "block_num": xxxx,
"asset_id": 0, | "is_virtual": false,
"delegate_slate_id": 1132758749919219197, | "is_confirmed": true,
"type": "withdraw_signature_type", | "is_market": false,
-
For example, on Windows, the latest binary works for me if I completely wipe the %APPDATA% folder.
However the moment I import an old wallet, it crashes on the blockchain rescan.
Perhaps all these problems people are reporting are just a matter of wallet compatibility.
-
the same with version 0.4.10
here are some differ from json file(I have remove some private infomations)
"type": "balance_record_type", | "type": "key_record_type",
"data": { | "data": {
"index": 9, | "index": 9,
"balance": 100000000000, | "account_address": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"condition": { | A> "public_key": "BTSXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"asset_id": 0, | "encrypted_private_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"delegate_slate_id": 1132758749919219197, | "memo": null
"type": "withdraw_signature_type", | ---------------------------------------------------------------------------------
"data": { | ---------------------------------------------------------------------------------
"owner": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", | ---------------------------------------------------------------------------------
"memo": { | ---------------------------------------------------------------------------------
"one_time_key": "BTSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX| ---------------------------------------------------------------------------------
"encrypted_memo_data": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx| ---------------------------------------------------------------------------------
} | ---------------------------------------------------------------------------------
} | ---------------------------------------------------------------------------------
}, | ---------------------------------------------------------------------------------
"genesis_info": null, | ---------------------------------------------------------------------------------
"last_update": "20140829TXXXXXX" | ---------------------------------------------------------------------------------
} | }
}, | },
{ | {
"type": "balance_record_type", | "type": "transaction_record_type",
"data": { | "data": {
"index": 10, | "index": 10,
"balance": 300000000000, | "record_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"condition": { | "block_num": xxxx,
"asset_id": 0, | "is_virtual": false,
"delegate_slate_id": 1132758749919219197, | "is_confirmed": true,
"type": "withdraw_signature_type", | "is_market": false,
-
Thos is not tooo bad as zge private keys can be derived from the wallet private key .. it makes thing complicated thus way .. also I'd really like to know how addresses and privkeys for market orders are derived .. gonna ask BM on the next hangout
-
Thos is not tooo bad as zge private keys can be derived from the wallet private key .. it makes thing complicated thus way .. also I'd really like to know how addresses and privkeys for market orders are derived .. gonna ask BM on the next hangout
but it's the account's private key. Is this derived from the wallet private key too?
I have try the command wallet_regenerate_keys, nothing get back. :(
-
I think you must save every time you make a new account.
-
alt, I will look at this. Have you noticed this behaviour before 0.4.9? Or only noticed since 0.4.9 and 0.4.10?
-
http://wiki.bitshares.org/index.php/RecoveringFunds
-
alt, I will look at this. Have you noticed this behaviour before 0.4.9? Or only noticed since 0.4.9 and 0.4.10?
I think this maybe happened because of marketing trade.
I have do many operation before this happened, like: short, ask, bid, cover
because I have not use marketing function before version 0.4.9, so I don't know if it happened before 0.4.9.
-
http://wiki.bitshares.org/index.php/RecoveringFunds
thanks, that help much :)
-
http://wiki.bitshares.org/index.php/RecoveringFunds
thanks, that help much :)
I figured too many people complain about "lost" funds .. which is basically not easy to do with TITAN .. only wallet bugs might cause you to just not "see" them ..
I hope this wiki article increses confidence in the AWESOMENESS!!!!! of TITAN and our lead devs!
;D 8) 8)
-
I have repair my wallet by import from an init json file.
maybe the backup json file is not good, which is backup automatic from a upgrade.
alt, I will look at this. Have you noticed this behaviour before 0.4.9? Or only noticed since 0.4.9 and 0.4.10?
I think this maybe happened because of marketing trade.
I have do many operation before this happened, like: short, ask, bid, cover
because I have not use marketing function before version 0.4.9, so I don't know if it happened before 0.4.9.
-
I have repair my wallet by import from an init json file.
maybe the backup json file is not good, which is backup automatic from a upgrade.
alt, I will look at this. Have you noticed this behaviour before 0.4.9? Or only noticed since 0.4.9 and 0.4.10?
I think this maybe happened because of marketing trade.
I have do many operation before this happened, like: short, ask, bid, cover
because I have not use marketing function before version 0.4.9, so I don't know if it happened before 0.4.9.
maybe we should write a script that removes everything from the backupjson except the wallet private key so that we can started over from square 1
-
I have repair my wallet by import from an init json file.
maybe the backup json file is not good, which is backup automatic from a upgrade.
alt, I will look at this. Have you noticed this behaviour before 0.4.9? Or only noticed since 0.4.9 and 0.4.10?
I think this maybe happened because of marketing trade.
I have do many operation before this happened, like: short, ask, bid, cover
because I have not use marketing function before version 0.4.9, so I don't know if it happened before 0.4.9.
maybe we should write a script that removes everything from the backupjson except the wallet private key so that we can started over from square 1
yes, I think this can help. but I don't know much about the wallet json file
-
alt, can you verify if this is still a problem in 0.4.13? https://github.com/dacsunlimited/bitsharesx/tree/v0.4.13
-
alt, can you verify if this is still a problem in 0.4.13? https://github.com/dacsunlimited/bitsharesx/tree/v0.4.13
no, still same problem.
1. I restore wallet from a backup json file.
2. run wallet_close
3. run wallet_open
4. wallet_unlock. the account key lost again.
I have resolved this issue by restore wallet from a clean backup json file(which is automatic backup after create the account), regeneric 150 keys, then all keys come back.
-
I saw something stranger. the size of backup json file became much less at 8.30 12:59. maybe a core dump happened at that upgrade.
restore failed with these two json : default-20140902T114827-version_upgrade.json or default-20140830T045915-version_upgrade.json
restore success with this json: default-20140827T130619-key_import.json
restore with this file block the client with very long time, until now, it's still block: default-20140830T045740-version_upgrade.json
alt@alt-ThinkPad-T430s $ ls -lt
总用量 940
-rw-r--r-- 1 alt alt 247295 9月 2 19:48 default-20140902T114827-version_upgrade.json
-rw-r--r-- 1 alt alt 247295 8月 30 12:59 default-20140830T045915-version_upgrade.json
-rw-r--r-- 1 alt alt 458342 8月 30 12:57 default-20140830T045740-version_upgrade.json
-rw-r--r-- 1 alt alt 2361 8月 27 21:06 default-20140827T130619-key_import.json
-
restore with default-20140830T045740-version_upgrade.json failed....
the same problem
I saw something stranger. the size of backup json file became much less at 8.30 12:59. maybe a core dump happened at that upgrade.
restore failed with these two json : default-20140902T114827-version_upgrade.json or default-20140830T045915-version_upgrade.json
restore success with this json: default-20140827T130619-key_import.json
restore with this file block the client with very long time, until now, it's still block: default-20140830T045740-version_upgrade.json
alt@alt-ThinkPad-T430s $ ls -lt
总用量 940
-rw-r--r-- 1 alt alt 247295 9月 2 19:48 default-20140902T114827-version_upgrade.json
-rw-r--r-- 1 alt alt 247295 8月 30 12:59 default-20140830T045915-version_upgrade.json
-rw-r--r-- 1 alt alt 458342 8月 30 12:57 default-20140830T045740-version_upgrade.json
-rw-r--r-- 1 alt alt 2361 8月 27 21:06 default-20140827T130619-key_import.json