gominer hash bigger than target

[username-rand]

Trying to use gominer to GPU mine with an 5700xt (opencl) to my own decred full node on a different machine. I'm getting the error "hash bigger than target" and I've searched but have been unable to find out how to correct this error. The miner is mining but nothing being accepted by dcrd. dcrd log says chain is synced and I see this when I turn on debug:

2023-09-15 10:17:21.702 [DBG] MINR: Created new block template (1 transactions, 9 stake transactions, 0 treasury transactions, 8940 in fees, 12 signature operations, 2937 bytes, target difficulty 0000000000003ff5260000000000000000000000000000000000000000000000, stake difficulty 278.81263814) 2

Below is the gominer error repeated over and over for each candidate.

2023-09-15 10:20:38.539 [DBG] MINR: DEV #0: Found candidate 1 nonce 81076dcf, extraNonce 090ab87c, workID 32e6f97d, timestamp 65047646 2023-09-15 10:20:38.539 [DBG] MINR: DEV #0: Hash 0000000008f1efa75ab93f390ad78dbcfdb50afc589b50a81e25b28cf08ffe68 bigger than target 0000000000003ff5260000000000000000000000000000000000000000000000 (boo)

Any suggestions on what to do to fix this?

Thanks

Rand

[username-rand]

Another piece of information from dcrd

decred@decred:~/decred/decred$ dcrctl getmininginfo { "blocks": 799498, "currentblocksize": 47164, "currentblocktx": 24, "difficulty": 263411.99807381, "stakedifficulty": 27881263814, "errors": "", "generate": false, "genproclimit": 1, "hashespersec": 0, "networkhashps": 3422983474140, "pooledtx": 24, "testnet": false }

[davecgh]

Answered in the mining channel, but I'll copy it here too for anyone reading later.

That's normal. It's just debug logging. The GPU finds a solution to a smaller problem and then that solution is checked against the real network difficulty. You can tell it's working properly, because if it weren't you wouldn't see a hash with the leading 0s like that.

Also, it logs stats every few seconds which reports the number of errors (which should be 0 unless you're overclocking your GPU to the hilt and it's inducing hardware errors).

[username-rand]

Thanks.  Didn’t know about mining channel at the time.  Appreciate you helping me.RandSent from my iPhoneOn Sep 15, 2023, at 1:36 PM, Dave Collins @.***> wrote: Answered in the mining channel, but I'll copy it here too for anyone reading later. That's normal. It's just debug logging. The GPU finds a solution to a smaller problem and then that solution is checked against the real network difficulty. You can tell it's working properly, because if it weren't you wouldn't see a hash with the leading 0s like that. Also, it logs stats every few seconds which reports the number of errors (which should be 0 unless you're overclocking your GPU to the hilt and it's inducing hardware errors).

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>