Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - qwerty1234

Pages: [1]
1
Found it. The balances were claimed almost exactly 1 year ago, in block 7333809, by user "bits00":

https://bitshares.openledger.info/account/bits00/overview/
http://cryptofresh.com/b/7333809

Unless you have the private keys to control that account, you should file it under "lost cause".

Thanks for the clarification. My mistake. Mystery solved, I did indeed claim the balance almost exactly 1 year ago. Almost exactly 1 year ago was when my SSD suddenly corrupted, so that explains a lot.

Oh well. Learn from my mistake people, always make multiple backups.

2
I suppose you have claimed the remaining 790 BTS today, which is a pity, because it would have simplified to pinpoint when the last withdraw was made.

Yep. Last week I tried claiming it out of frustration, hoping the full amount would turn up. Didn’t think that would affect anything though.

How I’m understanding this, is that both the balances have already been claimed in the past (or only the regular balance and not the vesting balance?) and almost all the BTS was claimed/withdrawn from the wallet key, leaving 790 BTS. Is that correct? If that’s the case, is there any hope for recovery? Or should I consider this a lost cause.

Thanks for the help.

3
You could try to look up your balances in the old client, then export the private keys for these and import them into the new wallet. I don't remember how that could be done in 1.0, but it is possible.

Thanks for the reply. I've definitely tried something like that before with this: https://github.com/cryptonomex/graphene/wiki/How-To-become-an-active-witness-in-BitShares-2.0.

Using this method, I found the 1 balance ID for the full amount of PTS (21000 PTS), found the owner of that Balance ID, and then dumped the private key for that owner. I'm not quite sure if this is the correct way to do it though, as that only gives me the key for the owner, and all the Balance ID's show the same owner.

Importing that key into 2.0 gives the same result (790 PTS).

I’m 99% sure I haven't claimed the BTS before (shouldn’t claiming it also claim the vesting balance at the same time?), but I’m not ruling out the possibility that it has been claimed in the past... Is it possible to check if the amount has been claimed before?



4
Technical Support / Missing funds after migrating to Bitshares 2.0
« on: June 26, 2017, 11:57:18 am »
I’m hoping someone can help me out. Because I’m at my wits end!

So, I’ve got a bitshares 1.0 backup from 2015 that I’m trying to migrate to a bitshares 2.0 wallet. With an up to date blockchain it's showing I have 21,000 BTS in my bitshares 1.0 account, but no matter what I try, only 790 BTS shows up when I import it into my bitshares 2.0 wallet.

What I don't understand is why 790 BTS is claimable with "lookup balance". I think I only have 1 private key/account associated to the full bts amount, so shouldn't it show either the full amount (21000 BTS) or nothing?

What I have:
bitshares 0.9.3c “BitShares Wallet Backup.json” backup with correct password
bitshares 0.9.3c applications data folder backup with correct password
old protoshares “wallet.dat” backup

What I have tried:
1. This guide: http://docs.bitshares.eu/bitshares/migration/howto-exporting-wallet.html
2. This guide: https://bitsharestalk.org/index.php?topic=18375.0
3. This guide: https://bitsharestalk.org/index.php/topic,20822.0.html
4. Everything in this thread: https://bitsharestalk.org/index.php?topic=9194.60
5. This: https://web.archive.org/web/20150326025854/http://wiki.bitshares.org/index.php/RecoveringFunds
6. Making a new 1.0 wallet and importing the protoshares backup
7. Rescan with latest blockchain, wallet_regenerate_keys <name> 99999, etc
8. Dumped and imported private owner/active keys to bitshares 2.0
9. A whole lotta other stuff.







Pages: [1]