Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments
Let me butt in here to say that in some cases users might not have a choice in running a light wallet.
I personally had an app installed in full mode which had bytes and blackbytes on it, I didn't run it for months. When I launched it to sync, it synced well up to some point but then it was just almost stuck (on an HDD). What I did was make a full backup, copy it to a computer with an SSD and restore from it. Needless to say that using a light wallet wouldn't have solved the problem ...
I personally had an app installed in full mode which had bytes and blackbytes on it, I didn't run it for months. When I launched it to sync, it synced well up to some point but then it was just almost stuck (on an HDD). What I did was make a full backup, copy it to a computer with an SSD and restore from it. Needless to say that using a light wallet wouldn't have solved the problem ...
Welcome to butt in. Everyone has a choice at running a light wallet or full node.
You chose to run a full node (not the default).
Needless to say.... running a light wallet WOULD have solved the problem.
It wouldn't have
. I'm not talking about a fresh install, I'm talking about a case where a full wallet contains blackbytes. There are two ways to regain control over the blackbytes, either sync the current full wallet up or restore in another full wallet that will sync up faster (SSD).A full backup of a light wallet does in fact keep youis fr bytes and blackbytes with a full restore. It takes about 15 seconds to sync. No matter how far back in history.
Of course it does, nobody's arguing about that
. Again the case I'm exposing is if one already had blackbytes in a full wallet, the only way out, is to sync up a full wallet.Again, a light wallet is fast and stores (and restores) bytes/blackbytes via a full backup/full restore.
Again, nobody's arguing about that and again you are missing the point by talking about something that is irrelevant to the case of a full wallet with blackbytes in it (I know I'm repeating myself but it seems necessary).
Resolution:
I do understand that since you have a full wallet and you will need to sync.
I do understand that since you have a full wallet and you will need to sync.
Yay! Finally
.You can resolve the problem for the future by starting up another wallet and move your funds to it. This way, you will not have the sync issue in the future.
Yes. Having said that, once the full wallet is running on an SSD it syncs up fast and there is no more syncing issue.
The whole point of my comment was actually to say that answering people who complain about syncing speed, "use a light wallet" is not helpful ... Yes "use a light wallet" in case you are fresh-installing or in case you only have bytes on your slow-syncing full wallet (cuz they can be restored through the seed), but if you have blackbytes on a slow-syncing full wallet and you want to regain control over them, well you are stuck until your full wallet syncs up or another fast-syncing (running on an SSD) full wallet where you restored from your full backup syncs up.
Using a light wallet would have solved the problem as you never would have had the problem. It was a choice made to go against the defaults.
It's the same argument people have for using Bitcoin Core wallet. - slow, SSD, takes lots of space, etc.
So, we agree that full node is slow. Must have a modern computer for speed.
There are other methods to restoring to a light wallet as I have done it before for several people and never charged anyone.
I think, and believe you would agree, that it would be awesome if there was a tool to convert a full node wallet to light wallet.
------------------------
Here is your link to receive 0.001 GB: https://byteball.org/openapp.html#textcoin?glove-crime-mystery-yellow-mean-globe-ensure-note-raw-hunt-lab-luggage