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

Boost MPOOL to show local boost/miner, not network. #1545

Closed
5 of 10 tasks
michieljmitchell opened this issue Jun 28, 2023 · 2 comments
Closed
5 of 10 tasks

Boost MPOOL to show local boost/miner, not network. #1545

michieljmitchell opened this issue Jun 28, 2023 · 2 comments
Labels

Comments

@michieljmitchell
Copy link

Checklist

  • This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • Other

Improvement Suggestion

Would be preffered to see the message pool summary for the local boost/miner instead of the entire networks mpool or both. Having the entire networks mpool size is usefull but it does not make sense to have to drill down for the local mpool.

image

@LexLuthr
Copy link
Collaborator

This bug was already resolved in #1523 and further improvements to the page are planned in #1530

@dirkmc
Copy link
Contributor

dirkmc commented Jun 29, 2023

Thanks for the bug report
Closing as fixed by #1523

@dirkmc dirkmc closed this as completed Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

3 participants