Here are some proposed changes from the Nibble developer from a previous thread:
All, I am the dev of "Nibble" - my coin has been near the top of coinchoose.com on and off for the last few weeks. I can do whatever you want really with this coin. Some ideas I have are to change the fork to 20,950 - its currently set to fork at 21k. you guys will have to spread the word of the update, get cryptsy to install it and all that.
I would change the block time to 1 minute, make the difficulty retarget something like 250 blocks, make the max difficulty adjustment around 110% (makes attacks or spikes less effective or impacting), and change the coin maturity to 50 confirms - the current 100 for a coin with so few miners is insane. I would keep the block reward at 500 but have it 1/2 every x amount of blocks (way out in the future)
These are not things the dev did wrong - its just that no coin is ever intended to be mined with under 10 mH/s total.
I can make these changes immediately and have a build for you tonight - I have dealt with gldcoin (we swapped nodes to improve both networks) and he told me that he will let me take over his dev duties. He said that he just has no time at the moment, he's swamped at work, swamped at home or something.
It is too late to change the fork to be earlier IMO. I don't think I agree with your other changes proposed. The protocol was never meant for short block times. You can get away with it on smaller networks but it will bite you if you grow later. Also, for what happens to a coin with shorter block times take a look at i0coin. Till better solutions to the issues caused are created I would hold off increasing block times. As for caping the increase at 110% all the does is extend the time that the coin can be mined at a rate exceeded the designed for parameters without it readjusting to compensate. The reduction in confirms due to the low mining power is just madness. The purpose of the confirms is to make sure that block is locked in. With low mining power and miners able to switch power easily, you actually need more confirms not less.
What the dev did wrong was already create a fork with the new client release. This probably is what caused a lot of the issues seen since then.
You are probably right on the 1 minute blocks, I was just throwing its out there as it was mentioned before by a few other people.
The problem i think is that you are failing to see the past history of the coin. This coin was attacked last minute to push up the difficulty to the current 7.34. This coin was in the scopes of many people since the beginning, and will surely be the target of future attacks. The cap I was suggesting would prevent these attacks from causing any huge spikes in difficulty. It will not extend the period a coin can be mined at a faster rate - the block re-targets are 504.
Here is some simple math:
4 difficulty changes of 110 % (440%) are actually more than 1 difficulty change at a original max 400% every 2016 blocks (which is what this coin was set to originally).
As for the confirmations, these numbers were pulled out of thin air. 120 is no safer than 60 confirmations once a coin is over difficulty 1. Do you really think that 120 wasn't just an arbitrary number in Litecoin and/or Bitcoin? I have had blocks waiting to mature for 4 days now - at its worst last week, it took 1 entire week for a block to mature. Now thats madness.