I look at it like this, the circle represents the whole nethash and difficulty with 2 miners competing for 288 blocks a day.
The right circle is what it should be.
miner A with big hashrate with fixing timestamp
miner B(honest) with small hashrate, sync time and uses public release miner. (1ghs)
nethash 10gh/s
(1ghs/10ghs)x288 = 28 blocks for miner B
This left circle is the reality.
Miner A pushes difficulty, goes up and up and as network detect blocks so close – this means the hashrate is also going up on explorer let say 20ghs
(1ghs/20ghs)x288=14 blocks for miner B.
less and less if difficulty goes very high for the honest. Pls pardon if logic is flawed but the distribution of blocks is skewed towards miner A in this situation. This is why im pushing timestamp bug fixed.
Please comment if the logic is really flawed. Now fairpool, are you going to be next nanopool?
Published at Sat, 04 Mar 2017 12:05:43 +0000
[wpr5_ebay kw=”bitcoin” num=”1″ ebcat=”” cid=”5338043562″ lang=”en-US” country=”0″ sort=”bestmatch”]
