mempool: release slot reservations when reorg cleanup removes a duplicate #29
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
pool
post-quantum
question
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ignotusnemo/parano1d#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
readmit_after_reorgremoves a concurrently re-submitted duplicate from the core mempool but does not rebuildadmitted_input_slotsandadmitted_output_slots. The removed entry can therefore leave temporary ghost reservations.This requires a submission to land in the narrow interval after
on_new_blockcompletes and beforereadmit_after_reorgacquires the mempool lock. A later transaction touching one of those slots can receive a falseSlotConflictuntil the next block rebuilds the reservation sets.Expected
Keep the slot-reservation indexes consistent whenever
readmit_after_reorgremoves an entry, preferably by rebuilding once after the removal loop.Scope
This is a transient local mempool bookkeeping issue. It does not alter State, transaction validity, issuance or consensus.
Originally reported by @AGI-is-going-to-arrive and moved here for normal public issue tracking.
Fixed in
13ef215a: reorg duplicate removal now rebuilds input and output slot reservations. A regression test covers both indexes.