I think that network hash rate is calculated through DIFFICULTY and BLOCK GENERATION SPEED.
so it's impossible that a "bad" config influence network hashrate.
Bitcoin Example:
expected_blocks = 144
difficulty = 11187257.461361 # this is on May 22nd 2013
blocks_found = 155 # Also May 22nd 2013
hash_rate = (blocks_found/expected_blocks*difficulty * 2**32 / 600)
MED example:
HASHRATE = DIFF * 2^32 / BLOCKTIME
HASHRATE = (100000 * 2**32) / 60
HASHRATE = 7,1582788 * 10^12 = 7,15 THS
ok, Last 24 Hours , ibipot has found 1188 valid block out of 24*60=1440 ? that is 82,5 %
according to formula above ibipot pool hash should be: (1188/1440*102449 * 2**32) / 60 = 6.05 THS
ok, I'b fine with that, I could revise that php-mpos formula, but when I do this, pool will also report, that single BE will do 1.8GHS ? width that I'm not fine.. because my bfgminer will show 309 MHS... I'm bit confused.. scrypt will not add that much hashrate...
Another thing is pool luck.. but this is unreal that ibipot luck is so good all the time...
dev's what are your thoughts?