Timeline for bitcoind getmininginfo says hashespersec is 0
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 19, 2012 at 23:53 | vote | accept | SparrowG | ||
Dec 19, 2012 at 23:53 | comment | added | SparrowG | Fine, I'll install a good miner. Any suggestions? | |
Dec 19, 2012 at 23:51 | comment | added | SparrowG | I did the rpc call, note the generate attribute is true. So, I expected bitcoind to mine. | |
Dec 19, 2012 at 11:29 | comment | added | Pieter Wuille | @DavidPerry Yes, I suppose that will happen soon. | |
Dec 19, 2012 at 5:50 | comment | added | David Perry |
Isn't it in the plans to fully deprecate both -gen and its related statistics fields?
|
|
Dec 19, 2012 at 4:32 | comment | added | Pieter Wuille | 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. | |
Dec 19, 2012 at 2:44 | comment | added | SparrowG | I'm doing this for fun rather than profit. How can I get the reference miner to do some work? Need not be significant. | |
Dec 19, 2012 at 0:12 | comment | added | Pieter Wuille | 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. | |
Dec 18, 2012 at 23:49 | comment | added | SparrowG | Does that mean my bitcoind instance is not trying to mine? | |
Dec 18, 2012 at 23:41 | history | answered | Pieter Wuille | CC BY-SA 3.0 |