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

Handling Orphaned Transactions from Superseded DeclareMiningJob Requests #956

Open
NonsoAmadi10 opened this issue Jun 4, 2024 · 0 comments
Assignees

Comments

@NonsoAmadi10
Copy link
Contributor

NonsoAmadi10 commented Jun 4, 2024

When a DeclareMiningJob request (Job A) is received and processed, the transactions associated with this job are stored in the mempool. If there are missing transactions, a ProvideMissingTransactions request is sent. However, if a new DeclareMiningJob request (Job B) arrives before the missing transactions for Job A are provided, the transactions for Job A that were recognized are correctly eliminated, but the transactions for Job A that are provided later are still added to the mempool. These transactions belong to a job that has already been superseded and thus will never be removed, leading to orphaned transactions in the mempool.

#868 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo 📝
Development

No branches or pull requests

1 participant