search

uraymeiviar / burst-miner

Burstcoin C++ Crossplatform Miner
http://uraymeiviar.github.io/burst-miner/
GNU General Public License v3.0
18 stars 14 forks source link

Repeated Submission of Same Nonce #2

Open bsom opened 10 years ago

bsom commented 10 years ago

Compiled latest commit 5368854 for Windows using VS2013 Express. A single nonce will sometimes be resubmitted many times:

UFHH-6HQC-76AR-4A87L best deadline 18 days 18:31:26 using nonce 18010062 submitting nonce 18010062 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2406226593392} confirmed deadline for UFHH-6HQC-76AR-4A87L : 27849844 days 19:56:32 submitting nonce 18010062 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2406226593392} submitting nonce 18010062 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2406226593392} plot read done. 2960210911709443567_5000000_100032_100032 100032 nonces submitting nonce 18010062 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2406226593392}

uraymeiviar commented 10 years ago

it is because of same issue you posted here https://github.com/uraymeiviar/burst-miner/issues/1

if pool confirmed deadline is higher than miner's calculated deadline, miner re-submit the nonce because it the nonce has better deadline than last confirmed deadline, but apprently the result does not give better deadline, you should check if your plot is un-altered or un-optimized, since its not yet fully tested with optmized plot which usually the stagger size is equal to nonce number so your plot does not have stagger

bsom commented 10 years ago

I'm plotting some new plots right now to test this out. Thanks.