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

Mempool cleanup bugs #893

Closed
Warchant opened this issue Nov 19, 2021 · 1 comment · Fixed by #900
Closed

Mempool cleanup bugs #893

Warchant opened this issue Nov 19, 2021 · 1 comment · Fixed by #900
Assignees
Labels
bug Something isn't working P5

Comments

@Warchant
Copy link
Collaborator

  1. When new block arrived fully valid connecting VTB has been removed from the mempool. New block did not contain this VTB.
  2. For some reason VBK statefully duplicate blocks remain in mempool (should be removed).
@Warchant Warchant added the bug Something isn't working label Nov 19, 2021
@Warchant Warchant added the P1 label Nov 19, 2021
@Warchant Warchant assigned Warchant and unassigned Mr-Leshiy Nov 22, 2021
@Mr-Leshiy Mr-Leshiy self-assigned this Nov 23, 2021
@Warchant Warchant added P5 and removed P1 labels Nov 24, 2021
@Warchant Warchant removed their assignment Nov 29, 2021
@Warchant
Copy link
Collaborator Author

For 2 - I found that mempool contained VBK blocks that already existed in VBK tree by running getrawpopmempool 2 - there were some VBK blocks that failed with "VBK-duplicate".

@Mr-Leshiy Mr-Leshiy linked a pull request Dec 6, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P5
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants