Alright I will go ahead and get the next block mined and tell you if it readjusts!
Russ should approve it in a few hours.
I do have prior experience in working on coins. So, I am sure this will help in the future as long as immediately. However, we need atleast 1 more person on the network to help me do the test.

Edit, think it was my browser cache? Did an CTRL+5 and now I got a file with another MD5 hash.
So I think this time he got it right  


Problem was on my side, don't understand what happened but second time I downloaded it, it was different.

Old client hash: 69084E87510442FCD13C92B7ABB9243D
New client hash: A33C67AF3780E585A97043079A3E33B5

Here are the changes made in the code. If the difficulty adjustment is changed I think we can do something better than this but am not volunteering  

justin7674, consider paying more attention to the comments detail. There are two spots where you did not update the comments with the correct values.

Original
justin7674

Original
justin7674 (need to fix the comments to say "look at 6 times the retarget")


Original
justin7674 (need to change "400%" comment to "200%")

+1 for that.

As soon as I can pull this from the official craftcoin repository I'll be happy to move forward with it.

It would be best if you point your miner at : http://198.50.233.9:8830/static/

The update changes the diff calculations.  It updates faster than before.  However, there is still a need to actually find the next few blocks at (relatively) high diff.

There still hasn't been an official confirm, just that the change will be looked at.

+1 should be about 10 more blocks and it readjusts. After this it will readjust every 36 blocks. We repaired the max mint every day because the previous wasn't matching the amount of blocks generated every day.

Until these 2 sites get updated with the "new" wallet I will not be doing any downloading of the files.

https://github.com/craftcoin/craftcoin

http://craftcoin.net/download.html

http://crc.scryptmining.com will update whenever official github is updated.


Watching this thread.

+


+



It's pretty (very) obvious that you do not really know what's going on. Essentially anyone on this forum could have implemented your 'fix', it's a temporary measure at best and needlessly introduces potential risks. Releasing the client and attempting to gain hashrate without approval is definitely on the edge of malicious.



"Your loss." Hm right, because those who do not decide to join your little fork would be left with devalued coins. Nice.

Forgive me if I do not find your references very impressive, especially after your baseless little outburst.


Anyways, as SaltySpitoon already mentioned,  nodes with a seemingly better height are going to be seen by the client and they will not be rejected immediately. The lack of node consensus is  not going to help anything, as such an insignificant edit means this will not be the last crc fork and the needless division of non-malicious network hashrate is entirely counter-productive. 

I say that you should all wait for a *real* fix, not a simple reduction in adjustment period.  Empirical evidence has already shown such a simplistic change is not a long-term solution to the problem of highly variable hashrate and introduces new potential risks.

Anyways, I hopefully didn't need to point any of the above out and you are all aware of what highly irregular coin generation can do to small economies.