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

getinfo longestchain takes startingheight as the value from a banned unsynced node #72

Open
dimxy opened this issue Sep 8, 2021 · 0 comments

Comments

@dimxy
Copy link
Owner

dimxy commented Sep 8, 2021

on the TOKEL chain getinfo showed bad "longestchain" much greater than the actual tip (53474 vs 52577). There was a banned, not synced node in the net (in getpeerinfo it has the startingheight=53474 taken as longestchain).

So the longestchain calc algo appears incorrect, it should skip not-synced nodes somehow

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

1 participant