<p>The <code>hashespersec</code> field reports the speed of the built-in miner. It does not (and can't accurately) report the hashing power connected to it via the <code>getwork</code> or <code>getblocktemplate</code> interfaces.</p>

CC BY-SA 3.0
2012-12-18T23:49:04.147Z
Does that mean my bitcoind instance is not trying to mine?
SparrowG
CC BY-SA 3.0
2012-12-19T00:12:07.517Z
Indeed - it doesn't do that by default, and there is no reason to turn that on either. The internal miner is just there as reference, but is 1) not optimized 2) you shouldn't mine on CPUs anyway.
Pieter Wuille
CC BY-SA 3.0
2012-12-19T02:44:55.713Z
I'm doing this for fun rather than profit. How can I get the reference miner to do some work? Need not be significant.
SparrowG
CC BY-SA 3.0
2012-12-19T04:32:08.033Z
Start with -gen, or run the RPC command: ./bitcoind setgenerate true. But really, even if you want to do CPU mining, use an external miner program. It'll be a lot faster. Especially as the built-in miner cannot use pools, the result of running it will be a 99.97% chance for having nothing after a month, and a 0.03% chance for 25 BTC.
Pieter Wuille
CC BY-SA 3.0
2012-12-19T05:50:05.137Z
Isn't it in the plans to fully deprecate both `-gen` and its related statistics fields?
David Perry
CC BY-SA 3.0
2012-12-19T11:29:27.837Z
@DavidPerry Yes, I suppose that will happen soon.
Pieter Wuille
CC BY-SA 3.0
2012-12-19T23:51:27.900Z
I did the rpc call, note the generate attribute is true. So, I expected bitcoind to mine.
SparrowG
CC BY-SA 3.0
2012-12-19T23:53:02.800Z
Fine, I'll install a good miner. Any suggestions?
SparrowG
CC BY-SA 3.0
2012-12-18T23:41:05.613Z
2012-12-18T23:41:05.613Z
Pieter Wuille
<p>I started mining yesterday on a low-end system, trying to figure out how it works.
I used the bincoind build from Debian. When I try
<code>bitcoind getmininginfo</code> today, I get the following output.</p>

<pre><code>{
    "blocks" : 208085,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 3368767.14053294,
    "errors" : "",
    "generate" : true,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "pooledtx" : 69,
    "testnet" : false
}
</code></pre>

<p>It looks like hashes per sec is 0. Shouldn't that be some positive number? 
Am I doing something wrong?</p>

CC BY-SA 3.0
2012-12-19T16:57:32.007Z
Are you certain that you are actually mining? What command line did you use?
Colin Dean
<bitcoind><hash><miner-configuration><cpu-mining>
bitcoind getmininginfo says hashespersec is 0
SparrowG
# bitcoind getmininginfo says hashespersec is 0

(Asked by: username_0 on 2012-12-18)

I started mining yesterday on a low-end system, trying to figure out how it works.
I used the bincoind build from Debian. When I try
`bitcoind getmininginfo` today, I get the following output.

```
{
    "blocks" : 208085,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 3368767.14053294,
    "errors" : "",
    "generate" : true,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "pooledtx" : 69,
    "testnet" : false
}

```

It looks like hashes per sec is 0. Shouldn't that be some positive number?
Am I doing something wrong?

**Tags:** bitcoind, hash, miner-configuration, cpu-mining

> **Comments:**
> **username_1**: Are you certain that you are actually mining? What command line did you use?  

---

## 1 answers

### Answer by username_2 on 2012-12-18. Score: 4 | Accepted answer

The `hashespersec` field reports the speed of the built-in miner. It does not (and can't accurately) report the hashing power connected to it via the `getwork` or `getblocktemplate` interfaces.

> **Comments:**
> **username_0**: Does that mean my bitcoind instance is not trying to mine?  
> **username_2**: Indeed - it doesn't do that by default, and there is no reason to turn that on either. The internal miner is just there as reference, but is 1) not optimized 2) you shouldn't mine on CPUs anyway.  
> **username_0**: I'm doing this for fun rather than profit. How can I get the reference miner to do some work? Need not be significant.  
> **username_2**: Start with -gen, or run the RPC command: ./bitcoind setgenerate true. But really, even if you want to do CPU mining, use an external miner program. It'll be a lot faster. Especially as the built-in miner cannot use pools, the result of running it will be a 99.97% chance for having nothing after a month, and a 0.03% chance for 25 BTC.  
> **username_3**: Isn't it in the plans to fully deprecate both `-gen` and its related statistics fields?  
> **username_2**: @username_3 Yes, I suppose that will happen soon.  
> **username_0**: I did the rpc call, note the generate attribute is true. So, I expected bitcoind to mine.  
> **username_0**: Fine, I'll install a good miner. Any suggestions?  

---

