BitShares Forum
Main => Technical Support => Topic started by: max on February 13, 2017, 04:18:26 pm
-
So I successfully exported keys with 0.9.3c. created new account in 2.0 and and imported the keys, now the the last step where I need to CLAIM does not work, what can be the problem there?
Account is unlocked, I see the balance, checkbox is checked but the button to claim doesn't do anything, i can click it one time or 50 times, nothing.
Am I the only one with this problem? I tried the light client first, then the webwallet, same result.
-
Open Light Client
On the right upper corner find Settings, between your account name and lock wallet option.
Go to Settings
On the left side bar you can find
General
Wallet
Accounts
Password
.......
.......
Clik on Wallet tab. Third button bellow you can find Lookup Balances button.
Thats it..
-
Yes, this is what I'm already doing.
I see the right "UNCLAIMED BALANCES BELONGING TO THESE KEYS", I have chosen the account, the line with the amount is ticked and the "CLAIM BALANCE (ACCOUNT_ID) is requiring to insert a password after i click it, then, nothing happens, doesn't matter if I just wait 15 minutes or click the button again, nothing happens.
What is the problem there?
-
I cant help you neither @max. It may be that you have different accounts in that wallet.
So you should figured out which account contains which vesting balance.
You said you have chosen right account name on:
Settings\Wallet
Active Wallet - did you select right wallet?
In Bitshares 2.0 you can use/chose different wallets. One wallet could contain different accounts. Pls check that too.
-
So this was indeed a bug that seems to be fixed after I updated to latest version from GitHub.
Unfortunately I ended up with another issue in the next step.
Now "Please confirm the transaction" modal window appears, but when I confirm the claim, error shows up and nothing happens again..
The error says:
Failed to broadcast the transaction:
now <= trx.expiration:
Can I do something about that?
-
You local clock is out of sync I would say