-
Notifications
You must be signed in to change notification settings - Fork 205
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
Implement node-less restore process (for desktop and mobile) #585
Comments
@valdok @gingervik reminder about what we've mentioned during the dev meeting: when a wallet connects to the node, it should know whether a node supports this restore functionality and if the node does support restore, clear and human readable reporting about the all the restore process errors should propagate to the wallet. |
also, can client please ask the expected file size from the restore server or whatever? this is to avoid redundant download and also to inform the user as file size might affect his data plan. @valdok @gingervik @BigRomanov |
one more thing please: when the node is downloading the files it's better to have an API that will inform the mobile regarding the progress of forming/updating the files. if you guys want me to open separate tasks - just tell. |
Following discussion with @gingervik, this task is moved to the next sprint, where my functional requests might be considered. |
checked with ios build |
As @valdok noticed, for successful restore only UTXO set and the first header+chainwork proof should be downloaded. The rest of headers and kernels are not required.
Lighter restore process can make mobile restore simpler (and consuming less battery power).
The text was updated successfully, but these errors were encountered: