Quote from: thsminer on September 28, 2014, 06:56:55 PM

You are amongst many people who say "rejecting blocks seems a bad idea" At first I got a little tired but thats not in the interest of the coin so I will explain why its not so strange...
I will refer to pooled mining. When you join a pool and start hashing on the current block, you get a diff from the pool that's less as the network diff. So you start hashing and find a matching block. You submit it to the pool and because it's hashed at a lower diff, good chance it does not comply with the network diff. And then comes the fun... your block gets rejected by the pool!
So your machine starts again and again and again, until you or another pooled miner finds a block that matches the network diff. At that moment the block is send onto the network and is accepted by the network.
So when you enter a pool you are hashing for John Doe most of the time and you get reject on reject. Your work however is recorded because the pool has to calculate how much effort you put in finding the block. The latter is the reason pools work this way otherwise they don't know how much effort you put in hashing.

I said it sounds bad Wink

Your reference to pooled mining did help a lot so I am now able to hopefully describe better what I ment with my vague words of "resending blocks with a corrected diff sounds far better".
Acting like a pool saying 'try it again with this higher diff' if block times are too short.
A bit more complicated on the other side, when block times are getting to long. 'Try it gain with this lower diff" doesn't work here. But with an intelligent algo we should be able to keep the upper block times limited too.

DGW3 still adjusting? We are at 1760 new blocks now, 1760 calculations to adjust. I can't see any reason in the code why it could take that long.

On the bride site: Looks like the heavy dump of ~900k coins this morning cleared the way to a nice price improvement during the last hours. Monday still coming, so there is something to look forward to during the coming week.