-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speed up wallet sync #20
Comments
Thank you for your feedback and solutions @the-metalworker |
Following up progress around BlazeSync to speed up syncs zcash/lightwalletd#350 |
Update: The fast sync optimization is planned to be included with the SDK upgrades for NU5 launch. |
It's been a while since I opened my wallet. It was using about 8GB of storage. I opened it last night around 7pm and it started downloading again. I let it run all night without opening any other apps - in the morning it was at "Scanning... 8%". It's now using 15GB of storage. I've been running it for another 3 hours this morning, and it's now at 11%. This app is not usable for me in it's current state. Is there anything I can do to speed up downloading or scanning time? |
As a side note, I can't use other apps on my phone when Nighthawk is doing this, or it crashes and has to start over, so I've basically been phone-less since last night because I really want it to finish scanning. I'm hoping it will compact storage when it's done - 15GB of storage for a wallet isn't going to work for me - I only have 64GB. |
I really like the idea of having the wallet pointed to my own Zcash node. Anything to make it so that I can actually open it and make a transaction in seconds - even if I haven't opened the wallet in months. |
First initialization very long. I waited 9 hours(download: 90Mb/s, upload: 85MB/s) for wallet to download necessary items. After that, there is a scanning and it's very long(it may be longer). I can't use my phone when wallet initialized. WTF? |
A faster syncing method is shipped with v2. |
Is your feature request related to a problem? Please describe.
There are two related problems:
In the first case, it took my wallet 40 minutes for the initial sync. Yes, 40 minutes before I could use the wallet after I first installed it.
In the second case, I open the wallet about once per week and on average it takes 20 minutes before I can use the wallet.
Describe the solution you'd like
I want the wallet to be usable within a few seconds after opening it. I don't know for sure how to make this happen but this is how the wallet should work while still maintaining privacy guarantees.
Describe alternatives you've considered
Idea for the initial sync problem: if the wallet is new, there should be no need to sync anything.
Only sync from that point forward. This would enable the wallet to be usable right away.
Idea for the subsequent sync problem: have the wallet sync in the background from time to time, that way the next way the user opens the wallet it is most likely already almost synced and the user can either use the wallet right away or only have to wait a short amount of time for the wallet to sync before it is usable.
Another complementary idea (not necessarily a replacement for the above) is to allow the user to pair the wallet with their own full node, ideally over Tor for privacy and NAT traversal benefits, so that they can instantaneously get their wallet balance info from their own full node.
The text was updated successfully, but these errors were encountered: