4
1
I wanted to start mining Bitcoin from the genesis block, so I cloned Bitcoin and removed the checkpoints. Then I compiled and started up the daemon. I wasn't connected to any other peers, however, so it wouldn't let me mine. I did ./bitcoin-cli setgenerate true but ./bitcoin-cli getmininginfo said I had 0 hashespersecond. When I connected to just one other peer, though, (a peer which also didn't have the checkpoints or the block chain), I could start mining.
Theoretically, though, why wouldn't the peer just let me mine on my own chain and not broadcast my results to anybody? I know it's not really a peer-to-peer network in this case, but I don't see why it would harm anyone to allow mining like this. Where in the v0.9.3 code does it essentially say "if not connected to peers, then don't allow generation"?
The
fMiningRequiresPeers = trueisn't on v0.9.3... ? – morsecoder – 2014-11-19T01:52:40.517@StephenM347 So it isn't. Fixed. – Nick ODell – 2014-11-19T01:56:17.620
And it may be pointless, but my point was that (I thought) it wasn't harmful. It seems like from the comment in the code, though, that allowing mining while not connected might actually be harmful because you could waste time mining on an obsolete chain. This also shows me where to change if I want to temporarily disable this for debugging, so thanks! – morsecoder – 2014-11-19T03:14:53.617