BitShares Forum
Main => Technical Support => Topic started by: pyre207 on March 16, 2016, 04:02:59 pm
-
Hi all,
I'm trying to finish my export from 9.3 to Bitshares 2.0 lite wallet. I have imported the json export, and I can see my unclaimed balances, but when I try to claim, I get the following error:
Failed to broadcast the transaction:
Missing Authority
Can anyone help me please?
-
Paging @svk @jcalfee1. This makes no sense to me. Should all private keys be present in the wallet when they show a balance?
-
Can I bump this?
I know you guys are really busy atm, but I'd rather not loose these funds :/
-
Can I bump this?
I know you guys are really busy atm, but I'd rather not loose these funds :/
Recently I found js console in Chrome very useful.
When you got an error in Chrome, press ctrl+shift+I, then copy all messages from the console, paste here.
//Update: better send the logs to developers privately since it contains maybe confidential info (account ids and etc, but no private keys anyway).
-
Hi abit,
This error is occurring when I try to import funds into the lite wallet, not the web wallet.
Am I missing something about your suggestion?
Thanks in advance.
-
I think the light wallet also has a 'debugging' or developer console available from the main menu
-
Seems to be a bug in version "BitShares-light_2.0.160314".
Got an Error: 3030003 tx_missing_other_auth: missing required other authority
Reinstalled previous version "BitShares-light_2.0.160217" ==> Balance claims are broadcasted without problems.
Log screenshots available if it helps.
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
Update: unfortunately that fix won't work in all cases.. IMO we need a hard fork.
//Update: after closer checking, I believe the key sorting bug won't affect balance claiming, unless the account used to claim funds is a multi-sig account. So, if OP (or @CalabiYau) was not claiming funds to a multi-sig account, it might be caused by another bug, probably a bug which causes loss of key(s).
-
Hi abit,
This error is occurring when I try to import funds into the lite wallet, not the web wallet.
Am I missing something about your suggestion?
Thanks in advance.
As xeroc has mentioned, in light wallet, press Ctrl+Alt+i, in the new window, click "console" from the menu, then righ click, select "save as...", copy the contents of the file here or upload the file to somewhere send the file to develops privately. (Although it doesn't contain your private key, but it does contain some sensitive info).
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
Update: unfortunately that fix won't work in all cases.. IMO we need a hard fork.
//Update: after closer checking, I believe the key sorting bug won't affect balance claiming, unless the account used to claim funds is a multi-sig account. So, if OP (or @CalabiYau) was not claiming funds to a multi-sig account, it might be caused by another bug, probably a bug which causes loss of key(s).
NOT a multisig account.
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
Update: unfortunately that fix won't work in all cases.. IMO we need a hard fork.
//Update: after closer checking, I believe the key sorting bug won't affect balance claiming, unless the account used to claim funds is a multi-sig account. So, if OP (or @CalabiYau) was not claiming funds to a multi-sig account, it might be caused by another bug, probably a bug which causes loss of key(s).
NOT a multisig account.
@CalabiYau Can you help provide some logs if possible? Thanks!
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
Update: unfortunately that fix won't work in all cases.. IMO we need a hard fork.
//Update: after closer checking, I believe the key sorting bug won't affect balance claiming, unless the account used to claim funds is a multi-sig account. So, if OP (or @CalabiYau) was not claiming funds to a multi-sig account, it might be caused by another bug, probably a bug which causes loss of key(s).
NOT a multisig account.
@CalabiYau Can you help provide some logs if possible? Thanks!
PM sent
-
We identified a sorting bug related to account authorities today which may have been the cause of this. jcalfee has fixed it so hopefully that will resolve this issue once the next version goes out.
Update: unfortunately that fix won't work in all cases.. IMO we need a hard fork.
//Update: after closer checking, I believe the key sorting bug won't affect balance claiming, unless the account used to claim funds is a multi-sig account. So, if OP (or @CalabiYau) was not claiming funds to a multi-sig account, it might be caused by another bug, probably a bug which causes loss of key(s).
NOT a multisig account.
@CalabiYau Can you help provide some logs if possible? Thanks!
PM sent
Got it. Thanks.
In the log, multiple operations in the transaction hasn't been sorted. But probably the signatures are calculated as if the operations are sorted. @jcalfee1 @svk thoughts?
-
Hi, not multisig, just trying to upgrade from 9.x to 2.0.
Should i use an earlier build to broadcast then upgrade, or would I be better to wait for the next release of the client?
-
Thanks everyone. This appears fixed in the current version.