0.4.9 will lost private key??(It's the account's owner key)

[alt]

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

Code Select Expand


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


[alt]

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

Code Select Expand


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


[alt]

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.

[vikram]

alt, can you verify if this is still a problem in 0.4.13? https://github.com/dacsunlimited/bitsharesx/tree/v0.4.13

[alt]

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

[xeroc]

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

[alt]

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.

[xeroc]

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)

[alt]

http://wiki.bitshares.org/index.php/RecoveringFunds

thanks, that help much  :)

[alt]

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.

[xeroc]

http://wiki.bitshares.org/index.php/RecoveringFunds

[vikram]

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?

[Empirical1.1]

I think you must save every time you make a new account.

[alt]

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.  :(

[xeroc]

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