BitShares Forum
Main => Technical Support => Topic started by: Harvey on January 22, 2015, 04:43:17 pm
-
I tried to import PTS wallet file to check the allocation of my share in the BTS v0.5.1 .
However, the BTS client reports error after I import one wallet file:
"*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name! "
Then I try to import the same wallet file into the account given in the error message.
Unfortunately, the same error occurs. This time, the Key was reported to belong to the first account! :(
It seems that the keys in the PTS wallet file were registered in both of the BTS account A and BTS account B. Therefore, whenever I import the wallet into either A or B, the same error will occur.
Someone probably encounter the similar problem.
Any suggestions will be really appreciated.
-
Should be addressed in the next release: https://github.com/BitShares/bitshares/issues/1297
-
+5%
-
Should be addressed in the next release: https://github.com/BitShares/bitshares/issues/1297
In BTS 0.6.0:
>> wallet_import_bitcoin \.wallet.dat account_name
10 assert_exception: Assert Exception
*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name!
-
Should be addressed in the next release: https://github.com/BitShares/bitshares/issues/1297
In BTS 0.6.0:
>> wallet_import_bitcoin \.wallet.dat account_name
10 assert_exception: Assert Exception
*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name!
Looks like I overlooked the details of the original post--I thought this was the bug in "wallet_import_keys_from_json" which has been fixed now, but it looks like the same bug is present in "wallet_import_bitcoin". I will take a look: https://github.com/BitShares/bitshares/issues/1362