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

Maintain mempool caches across Stacks blocks #5591

Open
obycode opened this issue Dec 18, 2024 · 0 comments · May be fixed by #5602 or #5599
Open

Maintain mempool caches across Stacks blocks #5591

obycode opened this issue Dec 18, 2024 · 0 comments · May be fixed by #5602 or #5599
Assignees
Milestone

Comments

@obycode
Copy link
Contributor

obycode commented Dec 18, 2024

During mempool iteration, the miner users two caches

  • a nonce cache, to track the current nonces of accounts
  • a candidate transaction cache, to save transactions that may soon be eligible to include in a block

These caches currently do not persist in between blocks since in the original pre-Nakamoto design, each miner only mined one Stacks block. We might get some significant benefit from maintaining these caches across blocks.

@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Dec 18, 2024
@obycode obycode self-assigned this Dec 18, 2024
@aldur aldur added this to the 3.1.0.0.3 milestone Dec 19, 2024
@aldur aldur moved this from Status: 🆕 New to Status: 💻 In Progress in Stacks Core Eng Dec 19, 2024
@aldur aldur moved this from Status: 💻 In Progress to Status: In Review in Stacks Core Eng Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Status: In Review
2 participants