Re: [ANN][DRK|Q2C|QRK|MYR] sph-sgminer - multi-algo GPU miner | MYR groestl added!
because maybe pool owners corrected their settings?
Problem with current sgminer is that is spams stratum server with lots of shares - If I change settings to accept those shares you will see that from one AMD280 card you have like 100MHash which is of course wrong. Few months ago there was the same problem with quark cpu miner - someone "corrected" miner source code which also spammed stratum with incorrect shares and if pool was not set up correctly that guy had huge hashrates there however almost never finding blocks.
Actually there are two guys who may help here as well (I finished my C++ programming 20 years ago
) - murraypaul who actually discovered the problem with "corrected" Quark miner and also reorder who fixed similar problem with his cgminer implementation for Skeincoin. I will send them PMs to look at this thread...
feeleep
EDIT: Just looked at supernova pool and someone pointed350 (now) 550 MHash there (1/3 of the network more or less) but still did not find a block - you guys still think it is valid?
Problem with current sgminer is that is spams stratum server with lots of shares - If I change settings to accept those shares you will see that from one AMD280 card you have like 100MHash which is of course wrong. Few months ago there was the same problem with quark cpu miner - someone "corrected" miner source code which also spammed stratum with incorrect shares and if pool was not set up correctly that guy had huge hashrates there however almost never finding blocks.
Actually there are two guys who may help here as well (I finished my C++ programming 20 years ago
) - murraypaul who actually discovered the problem with "corrected" Quark miner and also reorder who fixed similar problem with his cgminer implementation for Skeincoin. I will send them PMs to look at this thread...feeleep
EDIT: Just looked at supernova pool and someone pointed
Pool and miner should agree on diff1 target, or it will not work because the target is sent in compact format in stratum. Ideally, but not necessarily, it should also match the wallet diff1 to prevent confusion.
However, sgminer may not be consistent in how it calculates this (or so it seems): it does not ajust truediffone for modified diffone here:
https://github.com/prettyhatemachine/sph-sgminer/blob/master/sgminer.c#L2967
Please compare it with cgminer which has an adjustment (diff1 is 0x0000FFFF for scrypt):
https://github.com/Kalroth/cgminer-3.7.2-kalroth/blob/master/cgminer.c#L3306
Yes, I agree, this matches the earlier problem with the Quark miner that feeleep mentions above.
Scrypt difficulty needs to be scaled by 65535, if this is not done then you will be submitting shares below the actual difficulty target.
If the pool code has a similar bug, it will accept the shares and credit you with the work, but the shares have no chance of solving a block, so you will be taking an unfair portion of any pool reward for blocks found, compared to miners that only submit correctly scaled shares.
In short, the new miner may report very impressive hash rates, but these are spurious, and do not reflect actual useful work.