expose stable_hashrate via monitoring HTTP APIs#496
Draft
plebhash wants to merge 9 commits into
Draft
Conversation
This was referenced May 12, 2026
plebhash
force-pushed
the
2026-05-12-stable-hashrate-bool
branch
from
a6daa7e to
821b3d0
Compare
plebhash
force-pushed
the
2026-05-12-stable-hashrate-bool
branch
from
821b3d0 to
f60050e
Compare
github-project-automation
Bot
moved this to Todo 📝
in Stratum V2 - 2026 Q2 - Roadmap 📍🗺️
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
companion stratum-mining/stratum#2152
draft due to f60050e (avoids accidental merge)
but this is ready for review
note:
this is updating
stratum-apps/src/monitoring/openapi.jsondue to the following changes:stable_hashrateis exposed on downstream SV2 channel data (/api/v1/clients/{id}/channels)stable_hashrateis exposed on downstream SV1 client data (/api/v1/sv1/clients*)