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 leapfrogging #16

Closed
nopara73 opened this issue Apr 24, 2017 · 2 comments
Closed

Implement leapfrogging #16

nopara73 opened this issue Apr 24, 2017 · 2 comments

Comments

@nopara73
Copy link
Contributor

If the user is 100% sure it didn't receive transaction while it was away, it can skip the syncing.

@nopara73
Copy link
Contributor Author

nopara73 commented Feb 2, 2018

Another hybrid idea:

Download headers from the creation of the wallet (-100 headers) from trusted server.
Always check the last 100 header hash for reorgs.
Get notification for newblock from trusted server.
Download full blocks whenever wallet is online.
Mempool txs should come from trusted server.
From peers. Compare to headers.
If wallet closed with unconf txs download full blocks until it either confirms or 1008 block is downloaded.
If tx comes when wallet is off then user must manually write txid in it, it request over tor for trusted server then download full block.

Full wallet resyc: slow download all blocks

nopara73 added a commit that referenced this issue Apr 9, 2018
@nopara73
Copy link
Contributor Author

nopara73 commented Apr 9, 2018

In the new version this is not needed, it's light by design.

@nopara73 nopara73 closed this as completed Apr 9, 2018
nopara73 added a commit that referenced this issue May 20, 2019
Add comments to AsyncMutex.
soosr added a commit that referenced this issue Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
@nopara73 and others