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

need direction on bug with invalidateblock #512

Open
BrannonKing opened this issue Aug 17, 2022 · 0 comments
Open

need direction on bug with invalidateblock #512

BrannonKing opened this issue Aug 17, 2022 · 0 comments
Assignees
@cpacia

Comments

@BrannonKing
Copy link

The invalidateblock command has a bug wherein it doesn't follow side-chains with more work (after the best chain is invalidated).

See lbryio/lbcd#86 .

Is this because the getReorganizeNodes -> bestchain.FindFork doesn't account for the newly invalidated nodes (since they haven't been invalidated at the time it's called)?

Would calling getReorganizeNodes again after the invalidations work?

Any other ideas on how to fix this issue?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cpacia cpacia

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BrannonKing @cpacia