Author Topic: Trying to restore old .json wallets from 2015  (Read 5909 times)

0 Members and 1 Guest are viewing this topic.

Offline Juliatic

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • , , ,
 
The glucophone is a conductor to the contemplative aver of spontaneous improvisation. Because of this break-up in day-to-day soul, we enter the “shoot” and connect to the “start”, which allows us to take a refreshed look at the world in ourselves and ourselves in the in every respect, discover hidden resources and quicken intuition. Сombining the melodic and rhythmical principles of the playing, the petal drum makes the development of mastering musical skills straightforward and fun.  And, thanks to the unambiguous batch and instrumentation of notes, certainly everybody under the sun can tout de suite connect this get ready, and for this, you do not want to have distinguished knowledge. The total happens by way of itself, as if through magic.
 
 
I invite you to stop in my area: http://steel-tongue-drum.info
 
 
 
 
 
 
 
« Last Edit: November 29, 2021, 01:55:53 pm by Juliatic »

Offline FuLl

  • Full Member
  • ***
  • Posts: 101
    • View Profile
You might be able to pay someone a % to hack it,

I'm not even sure there's anything left in them. So far I've gone through restoring a bunch of Electron wallet seeds for BTC & LTC, hoping there was some kind of then-untransferrable change in there that could be worth anything. I found that they had all been emptied to the last decimal.

I don't remember what was going on with BitShares last I interacted with it. Something tells me that since I had a PTS wallet there might be some of that somewhere, otherwise I wouldn't have needed that wallet. Not sure what the KeyID app is, don't recall anything about that.

I wouldn't be surprised if both these wallets are completely empty. I wouldn't want to promise a percentage of zero & end up owing money at the end.

I find it hard to believe you never wrote it down anywhere at all. Perhaps its stored in hiding place you've forgotten about?
I looked where it would have been, & tried a dozen or so combinations of what I was using back then, to no avail.

Offline Permie22

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
  • BitShares: Permie
You might be able to pay someone a % to hack it, particularly if you have a list of passwords or likely words you may have used within a password. You will have had to create and choose the password yourself, and it would have told you that the password would be needed to access the exported json when you wanted to import it somewhere else.

I find it hard to believe you never wrote it down anywhere at all. Perhaps its stored in hiding place you've forgotten about?

Offline FuLl

  • Full Member
  • ***
  • Posts: 101
    • View Profile
You might need use your 0.9.2 wallet

Well, it would appear that the whole darn thing is moot- apparently I failed to document what the passwords were for these .json files when I exported them.

God only knows what riches are lost...

Offline Permie22

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
  • BitShares: Permie
2015 makes a lot more sense

BitShars 2.0 was released in late 2015

You might need use your 0.9.2 wallet to try exporting your keys, and then importing that .bin or .json or whatever file into 0.9.3c. Make sure the blockchain is fully up-to-date with ~October 2015 else some of your keys might be missed in the export.

Then export from 0.9.3c into a BitShares 2.0 compatitble wallet

Offline FuLl

  • Full Member
  • ***
  • Posts: 101
    • View Profile
You created the wallet in 2016?
The timestamps on these are both July 2015. Will edit the title accordingly.

Was it version 0.9.3?

I don't have a 0.9.3, but I do have a 0.9.2.
Here's a screenshot of the versions I have to work with:
https://files.catbox.moe/3b32a8.png

Not sure what's relevant anymore since I've been gone so long.

I guess I can try the method you mention using 0.9.2. Will have a look at those links in a little while.
Thanks for your help.


Offline Permie22

  • Jr. Member
  • **
  • Posts: 21
    • View Profile
  • BitShares: Permie
You created the wallet in 2016?

Was it version 0.9.3?

If so, import the json files you have into 0.9.3 and then on version 0.9.3 export your wallet ready to be imported to the lastest BitShares chain that is running since Late 2015 - "BitShares 2.0"

Some potentially helpful links:

https://bitsharestalk.org/index.php/topic,20822.0.html  - Handy guide for what it seems you are trying to do :)

In the comments of the above guide is this link to download the full 0.9.3 blockchain so you can scan for your keys and export them quicker without waiting for the 0.9.3 client to download the chain https://mega.nz/#!P8BhCZ4I!NZHkhUEbrgVTNRI1QXhDJI6ly7z1Fv2nFgrpQM1UWDQ

https://github.com/bitshares/bitshares-core/wiki/Import-BitShares-0.9.3c-wallets-into-BitShares-2.0-CLI-wallet

« Last Edit: September 12, 2019, 02:33:54 pm by Permie22 »

Offline FuLl

  • Full Member
  • ***
  • Posts: 101
    • View Profile
Please have a look it that helps

https://how.bitshares.works/en/master/bts_holders/investor_guide.html?highlight=PTS

Thanks, but it doesn't seem to apply.

What I've got are .json files for 2 different 'accounts' I had made long ago using the old BitSharesX client. I still have a Windows Installer for them so maybe I'll fire one up & see what happens.
« Last Edit: September 12, 2019, 07:29:26 pm by FuLl »


Offline FuLl

  • Full Member
  • ***
  • Posts: 101
    • View Profile
I had 2 accounts back then, & still have their .json wallet files from when I ran BitSharesX. The last version I used was 0.4.23.1

If I remember correctly I also had some kind of different token from when I was running BitShares-PTS 1.0.0

I've installed BitShares2-light on Ubuntu 16.04 & none of the options I find there want my .json files.

Could use a hand.
« Last Edit: September 12, 2019, 07:28:54 pm by FuLl »