Author Topic: wallet_collect_vested_balances for KeyID  (Read 1958 times)

0 Members and 1 Guest are viewing this topic.

Offline lafona

  • Sr. Member
  • ****
  • Posts: 231
    • View Profile
  • BitShares: lafona
Everything is working now. I had imported the wallet using the wallet_import_keys_from_json command. When I went back to check the wallet today I realized that the block count was about half of what it should be. It seems like something had stopped the blockchain from syncing. Sorry I don't have a better description, everything is working fine now. Thanks
BTS Witnesses: delegate-1.lafona     Witness Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: lafona

Offline vikram

How did you import the wallet? You need to use the "wallet_import_keys_from_json" command to import the private keys into an existing DVS wallet.

Do you see your vesting balances when you do "wallet_check_sharedrop"?

Offline lafona

  • Sr. Member
  • ****
  • Posts: 231
    • View Profile
  • BitShares: lafona
I imported my KeyID json and used the wallet_collect_vested_balances command to try to claim my vested balance from DNS, however in the transaction history it is still listed as pending and doesn't show up as a balance in the account. Is there another step I am missing, or some time I have to wait? It was enabled at 25000, right?

Also I tried the command wallet_rescan_blockchain just to see if it would help.
BTS Witnesses: delegate-1.lafona     Witness Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: lafona