Quote from: Cor2 on March 18, 2014, 10:24:34 PM

Quote from: s4w3d0ff on March 18, 2014, 10:00:33 PM

Quote from: polmax on March 18, 2014, 09:52:35 PM

Quote from: Cor2 on March 18, 2014, 09:38:16 PM

Quote from: polmax on March 18, 2014, 09:05:57 PM

Quote from: s4w3d0ff on March 18, 2014, 07:38:50 PM

We are there! Has anyone forked? I really hope not!

good good good excellent all at the pool we already have 1/4 found/amount

Ever since passin block 64k I see the following:
- about 3 times more blocks found reported on pools (which previously ignored zero-reward blocks) (this is expected)
- I see many blocks being rewarded 0.33 CGA, but there seems to be *no* relation to the difficulty of that block!
Several blocks have very low difficulty (1.11 or 1.16 or 1.60) and have a *lower* reward (0.23, 0.22, 0.16)
while I also see blocks found with diff larger than 3 which *do* have 0.33 rewards!
It appears that the reward is not calculated from the actual diff at the moment of block finding, or the pool is mis-reporting it?

So, I went to the block explorer and checked one suspect: block 64090:
difficulty 1.10575869
TX Value 0.22609161
Oh-oh...

Block Time: 40 seconds
Difficulty Refresh: 80 seconds/2 blocks
1/diff next 2 block

Ya the diff will reflect the next block not the current one... I'm not sure how to change such a thing.

Ah, that clarifies.
The block finding time is now 60 sec (30 blocks found in 30 mins from block 64115 to 64145) so still not near the designed 40 sec.
The diff seems not to jump as high as before any more, but apparently still enough to cause some blocks to take several minutes to be found, slowing the average down quite a bit.

This will continue until the network hash gets a bit higher. Like I said before we had Kimotos Gravity Well before but there are exploits that involve nTime, until someone comes up with a better solution, the only thing that will stabilize the block time is more people mining. So spread the word!