Quote from: coinling on January 02, 2017, 12:32:36 PM

But what's the point of regular data recovery ? The software will just find deleted files , right ? In this case the file actually wasn't deleted, but rather changed.
So i need tool to reset several data to a specific snapshot time.

I see your point, regular data recovery would just find deleted files.

Did you save your wallet words when you created your wallet? You might be able to restore a wallet using them and access your byteballs with it, but not your black byteballs.

The dev said you only needed to backup your appdata folder because of your black byteballs. Perhaps you could install byteball on a different computer, find the file that stores the wallet words, and change them to the wallet words from your old computer.

Quote from: tonych on September 28, 2016, 12:38:06 AM

Quote from: galaxiekyl on September 28, 2016, 12:16:57 AM

pls, wht means : "to restor your wallets, you will need full backup of Bytesball setting. Just the wallet seed is not enough."

how i must save my wallet to restor it ?

You need to backup the entire wallet data folder, its location depends on your platform: https://github.com/byteball/byteball#byteball-backups-and-recovery.
But doing it is not practical, as you'll have to back up again every time you send or receive blackbytes (which are only saved in this folder).
A better option is to set up a multisig wallet with redundancy (such as 1-of-2 or 2-of-3) on multiple devices, which ensures that in case one of the devices fails you will still be able to use the wallet on the other device(s). All devices will have a copy of the private payments (blackbytes).

Quote from: galaxiekyl on September 28, 2016, 12:16:57 AM

yu say first 100k wallet loader will receive an part of 1% of all bytesball..yu talk of bytesball test or bytesball after beta..how you will distribute them ?

Quote from: pm7 on December 25, 2016, 06:10:50 PM

About seed, see here: https://github.com/byteball/byteball

Quote

Byteball uses a single extended private key for all wallets, BIP44 is used for wallet address derivation. There is a BIP39 mnemonic for backing up the wallet key, but it is not enough. Private payments and co-signers of multisig wallets are stored only in the app's data directory, which you have to back up manually:

   macOS: ~/Library/Application Support/byteball
   Linux: ~/.config/byteball
   Windows: %LOCALAPPDATA%\byteball

This quote is from the github for the headless (no GUI) version of byteball. It says the BIP39 mnemonic is saved in the file keys.json in the app data directory.

https://github.com/byteball/headless-byteball

Quote

The first time you run it, it will generate a new extended private key (BIP44) and ask you for a passphrase to encrypt it. The BIP39 mnemonic will be saved to the file keys.json in the app data directory (see byteballcore for its location),