Definitions of networkhashps and hashespersec

+1 vote

Hi, 

I have a question regarding the output of the getmininginfo command. I have one node with mining permission. When I run getmininginfo I get this output:

{"blocks" : 59,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000006,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 17,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespersec" : 0}
I was wondering how the networkhashps can be 17, while the hashespersec are 0 for every node. 
Can someone give me the exact definitions of networkhasps and hashespersec?
Thank you!
asked Jan 31, 2018 by bisbaldi

1 Answer

0 votes
If you're performing permissioned mining, i.e. not based on proof-of-work, you should ignore these fields. They are present for backwards compatibility with Bitcoin Core tools, but have no meaning in a chain with permissioned mining.
answered Feb 1, 2018 by MultiChain
Thanks for you answer. Does this apply to all of the values I get returned from getmininginfo?
Only the fields relating to difficulty and hash rate should be ignored. Other fields which describes the chain or blocks being built are still relevant.
OK, thank you. Is there any way to get the hashrate and difficulty using permissioned mining?
In permissioned mining the difficulty and hash rate are negligible, since the security of the chain is based on distributed consensus between identified parties, rather than proof-of-work.
...