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

Fix "mempool analyzer" tool #3097

Closed
gregorycoppola opened this issue Apr 18, 2022 · 2 comments
Closed

Fix "mempool analyzer" tool #3097

gregorycoppola opened this issue Apr 18, 2022 · 2 comments
Labels

Comments

@gregorycoppola
Copy link
Contributor

gregorycoppola commented Apr 18, 2022

The "mempool analyzer tool", once advanced as #3020, but never checked in, is broken, in the sense that I can't get it to work on my node.

I'm not sure what is wrong.

We should consider:

  1. fixing it
  2. turning it into a process that runs continually

To be a process that runs continually, we could either:

  1. make it like the "mock miner", but have it iterate over all transactions
  2. just have this process each transaction once, queued up when it is received in the mempool, and removed from the queue once it has been tested a single time. This is different than the "mock miner" style set-up, where a transaction could be processed multiple times, giving more up-to-date information, but making it harder to get through all transactions.
@jcnelson
Copy link
Member

Closing due to inactivity.

@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants