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.

Sign up for GitHub

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

Jump to bottom

Implement a 'bad tipset cache' #250

Closed
whyrusleeping opened this issue Sep 30, 2019 · 2 comments
Closed

Implement a 'bad tipset cache' #250

whyrusleeping opened this issue Sep 30, 2019 · 2 comments

Comments

@whyrusleeping
Copy link
Member

If a chain is synced to and it doesnt link to our chain, we may end up wasting a lot of work syncing to it. When we detect a bad chain, we should mark it as such and not make the mistake of attempting to sync to it at any point in the future.
@magik6k
Copy link
Contributor

magik6k commented Sep 30, 2019

Note that it may be the case that our chain is actually on the 'bad' side, which may happen when the network gets separated for some time

@whyrusleeping
Copy link
Member Author

closed in #305

nonsense added a commit that referenced this issue Nov 6, 2020
@nonsense
Update README.md (#250)
d3f6657
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whyrusleeping @magik6k