Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments
And none didn't answer for my question 
It will be good, that in wallet will be added opportunity to chose address for tip (like in Electrum or some others bitcoin clients). 'Cause in another way it's very hard to do all this work by yourself.
It will be good, that in wallet will be added opportunity to chose address for tip (like in Electrum or some others bitcoin clients). 'Cause in another way it's very hard to do all this work by yourself.
It's for this reason that it is necessary to save completely the directory of the byteballs, not just seed
Yeah, but you must save it after each transaction lol. It's very hard and here can be some other problems. Like an empty balance... private assets, such as blackbytes, are stored only in the wallet (exactly because they are private) and get updated every time you send or receive a private asset.
To secure against loss of the wallet, I recommend that you use multisig. For example, 1-of-2 multisig with one wallet on the phone, the other on a desktop computer. This way, the private assets will be automatically copied to the two devices.
To secure against loss of the wallet, I recommend that you use multisig. For example, 1-of-2 multisig with one wallet on the phone, the other on a desktop computer. This way, the private assets will be automatically copied to the two devices.
Yep, but how does it help with problem of creating new address after transaction? I dont understand for sure.
After any transaction tip will go to new address in your wallet. To denied it you can:
1. Send money again from new address to your main (i didn't test that way)
2. Back up your data wallet.
The idea behind 1-of-2 is to have some kind of backup. It doesn't help with the problem of creating a new address. How would backing up your data solve that? All your addresses stay accessible through your wallet. If you back it up and restore it, you just restore to a previous state (ie you won't have transactions that were made after the back up), so I don't really understand your point #2.