Closed stevengdev closed 6 years ago
Looking at logs Claymore never produces the line below, which I suspect is how the slowdown is tracked. This must get tokenized and tracked somewhere, triggering the slowdown.
DevFee: ETH round found 1 shares
21:20:44:294 1f68 DevFee: ETH: 01/02/18-21:20:44 - SHARE FOUND - (GPU 0)
Previous result was with beta patch, which may be broken. Official produces:
14:09:23:401 5cbc DevFee: ETH round found 1 shares
14:09:23:403 5d88 DevFee: ETH: 01/03/18-14:09:23 - SHARE FOUND - (GPU 0)
14:09:23:403 5d88 send: {"id":4,"method":"eth_submitWork","params":["0xe0fd3dc01f06e487","0xbe75d4ba3e24b59e7b9d2dfd9d8952a6f74b62d888a2880b226a2a635aa8275b","0x6a30cb2bbd7899df3a0fc053a2d5540a779bb0fbdfe64779a4cd28284644b9d5"]}
This looks right. I'm still observing to see if process takes a sustained nosedive.
Replacing beta with official seems to have done the trick! NoDevFee 0.2.1 and Claymore 10.0 working together confirmed.
I'm using Claymore 10.0 and the latest beta patch, but the patch does not seem to work. Claymore continues to report the MH/s as steady both to ethermine.org and at command line, but effective MH/s is actually lowered as consistent with the -nodevfee switch. Is there a specific version this should work with?