Skip to content
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

Closed
sasha-abramovich opened this issue Apr 3, 2019 · 5 comments
Closed
Assignees

Comments

@sasha-abramovich
Copy link
Contributor

sasha-abramovich commented Apr 3, 2019

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).

@sasha-abramovich
Copy link
Contributor Author

@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.

@sasha-abramovich sasha-abramovich changed the title Consider node-less restore process (for desktop and mobile) Implement node-less restore process (for desktop and mobile) Jun 30, 2019
@sasha-abramovich
Copy link
Contributor Author

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

@sasha-abramovich
Copy link
Contributor Author

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.

@sasha-abramovich
Copy link
Contributor Author

Following discussion with @gingervik, this task is moved to the next sprint, where my functional requests might be considered.

@gingervik gingervik assigned sinaizd and unassigned valdok Jul 22, 2019
@gingervik
Copy link
Member

checked with ios build

echoby added a commit that referenced this issue Jun 27, 2022
echoby added a commit that referenced this issue Jun 30, 2022
echoby added a commit that referenced this issue Jul 12, 2022
echoby added a commit that referenced this issue Jul 13, 2022
echoby added a commit that referenced this issue Jul 14, 2022
echoby added a commit that referenced this issue Jul 18, 2022
echoby added a commit that referenced this issue Jul 18, 2022
echoby added a commit that referenced this issue Jul 19, 2022
echoby added a commit that referenced this issue Jul 19, 2022
echoby added a commit that referenced this issue Jul 20, 2022
echoby added a commit that referenced this issue Jul 22, 2022
echoby added a commit that referenced this issue Jul 22, 2022
echoby added a commit that referenced this issue Jul 22, 2022
echoby added a commit that referenced this issue Jul 25, 2022
echoby added a commit that referenced this issue Jul 26, 2022
echoby added a commit that referenced this issue Jul 29, 2022
echoby added a commit that referenced this issue Aug 5, 2022
echoby added a commit that referenced this issue Aug 8, 2022
echoby added a commit that referenced this issue Aug 8, 2022
echoby added a commit that referenced this issue Aug 10, 2022
echoby added a commit that referenced this issue Aug 19, 2022
echoby added a commit that referenced this issue Aug 19, 2022
echoby added a commit that referenced this issue Sep 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants