- Support for getblocktemplate (GBT, BIP 22). With getwork deprecated and soon to be removed from Bitcoin, it was important to get this implemented, especially for testing solo mining. The getblocktemplate method is now used by default for protocol HTTP, but the miner should automatically switch to getwork if the newer method is not available. To force the miner to use getwork, a --no-gbt option is provided.
I found that for solo mining with cpuminer V1.4 I have to extend command line with parameter
--no-gbt or --coinbase-addr otherwise it will not connect to the "coin server":
[2014-05-21 13:05:06] json_rpc_call failed, retry after 30 seconds
BTW, I think this is a cpuminer bug that it doesn't try to switch to getwork protocol and stays in never-ending loop waiting for a miracle...
I added --coinbase-addr because I think it can address a problem with wallet design, where it is not possible to export default key (at least I failed to find how to do it) and I have to keep backup of binary wallet that is far from perfect.
I test it at the moment, no block was found so far and that could be an indicator that something is wrong... Maybe I have only bad luck...
I found bfgminer notice, that when several clients are connected to the same "coin server" and are mining to the same address, than parameter --coinbase-sig has to be added
https://github.com/luke-jr/bfgminer, section SOLO MINING.
Is it true that --coinbase-sig with unique parameter has to be added when more clients are connected with the same address?? So far, I just configured all my clients with the same --coinbase-addr address but I am not sure if this is good idea because it is possible that they work on the same units and my computing power is reduces compared to configuration with --no-gbt (operation mode of older cpuminer)...