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

Inflated Deadline Displayed after Submission #1

Open bsom opened 9 years ago

bsom commented 9 years ago

Compiled latest commit 5368854e13 for Windows using VS2013 Express. I'm seeing some odd numbers for deadlines in the logs:

plot read done. 2960210911709443567_222222222_100032_100032 100032 nonces UFHH-6HQC-76AR-4A87L best deadline 71 days 05:35:43 using nonce 6205982 submitting nonce 6205982 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2805214427438} confirmed deadline for UFHH-6HQC-76AR-4A87L : 32467759 days 13:50:38 UFHH-6HQC-76AR-4A87L best deadline 62 days 12:47:05 using nonce 5501199

Not sure how to read these numbers or if I am misinterpreting what they are trying to tell me.

bsom commented 9 years ago

This problem persists in the latest build: UFHH-6HQC-76AR-4A87L dl:13 days 13:10:12 n:149259966 submitting nonce 149259966 for UFHH-6HQC-76AR-4A87L {"result":"success","deadline":2031791465334} confirmed dl. for UFHH-6HQC-76AR-4A87L : 23516104 days 22:08:54

uraymeiviar commented 9 years ago

it is because pool's deadline and miner's deadline is different, could be because of difference in plot data format, wrong plot filename, others also report this if their plot is "optimized" with a tool, i never tested this miner with "optimized" plot since i never optimize my plot

bsom commented 9 years ago

I do, in fact, have some optimized plots.

bsom commented 9 years ago

OK, I removed all optimized plots and it happens far less, but it still happens. Any ideas?

bsom commented 9 years ago

Well, I guess I spoke too soon. With all new plots, I still get ridiculously mangled deadlines about 90% of the time. 1 Day turns into 20960235087 Days. This essentially makes mining Burst useless since I only get reliable credit for about 10% of my nonces. I'm going to try the Java mining tool to see if the same holds true.

bsom commented 9 years ago

Been mining with the Java tool for 5 days now. No inflated deadline problems. Go back to this tool, inflated deadline problem. :-( Guess I'll stick with the Java tool so I get credit for everything.

rhkarls commented 9 years ago

I have the same problem, and looking at deadlines for other miners I can see they have the same issues. I don't think it has to do with the plot files. It seems to happen when blocks are found rather quickly, and problem persists until one block last long enough so that all plot reads are done. Seems it submits nonces intended for previous block(s). Should it not start reading the plot files again on new blocks, instead of continuing on the previous?