-
Notifications
You must be signed in to change notification settings - Fork 38.7k
document return value of networkhashps for getmininginfo RPC endpoint #8461
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
Conversation
|
ACK 205eb35 As you are touching the helptext, can you please align "errors" and "chain" helptexts by adding two spaces before "(string)"? |
|
ACK 205eb35 agree with @paveljanik about the PR related nits. |
|
ACK 65f4532 |
|
Updated to align "chain" and "errors" output with rest of help text. |
|
Thank you! ACK 65f4532 |
|
ACK 65f4532 |
1 similar comment
|
ACK 65f4532 |
… RPC endpoint 65f4532 document return value of networkhashps for getmininginfo RPC endpoint (Jameson Lopp)
|
Backport needed, I guess. (all the way back to 0.9.x, but we don't maintain that far back) |
|
@luke-jr According to current https://bitcoincore.org/en/lifecycle/ 0.11 only receives critical security fixes and this is only a documentation fix. (Though, I am not against backports for 0.12 and 0.13) |
Github-Pull: bitcoin#8461 Rebased-From: 65f4532
…inginfo RPC endpoint 65f4532 document return value of networkhashps for getmininginfo RPC endpoint (Jameson Lopp)
…inginfo RPC endpoint 65f4532 document return value of networkhashps for getmininginfo RPC endpoint (Jameson Lopp)
It looks like this value isn't documented in the RPC help. If it would be helpful, we could be even more specific and mention that it uses the default trailing 120 blocks parameter to calculate the hashrate.