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

Polish delayed node #240

Closed
nathanielhourt opened this issue Aug 17, 2015 · 1 comment
Closed

Polish delayed node #240

nathanielhourt opened this issue Aug 17, 2015 · 1 comment

Comments

@nathanielhourt
Copy link
Contributor

Following up on #237, there are some limitations of the initial implementation. Primarily, that the delayed node does not handle forking right now.

Optimally, the delayed node will check that the block ID's match for a given block number between its trusted node and itself, and, if they don't, pop blocks until they do. If it runs out of undo history, it needs to resync (this is currently hard to do without restarting the process, as it's impossible to clear the object graph from memory without destroying the database). Then it will resume syncing from the trusted node as usual.

@vikramrajkumar
Copy link
Contributor

This issue was moved to bitshares/bitshares-core#63

pmconrad pushed a commit to pmconrad/graphene that referenced this issue May 24, 2017
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

3 participants