Let me correct your citation
With Guldencoin something else is going on. Due to the latest software release blockproduction slowed down significantly from 150 seconds per block to 250 seconds per block, as I mentioned before. If this is not repaired it will not be 40 years before Guldencoin reaches a total of 1.7 billion but 67 years. Also the blockreward-halving with take some more time as a result.
is this true?
Now we know where this is coming from.
Some truth used to construct a case for ppl w/o any knowledge about target time, diff calculation and resulting avg. block times.
"Due to the latest software release blockproduction slowed down significantly" is definitely wrong and only shows that he doesn't know anything about the development here at NLG. Sorry
bitwise-shifted, you should inform yourself better before making comments like that.
Concentrate on EFL instead of steady pointing fingers at NLG.
NLG is not responsable for raise or fall of EFL, the EFL foundation is.
As someone noted to him before, there is a significant difference if you have a stable hashrate or jump pools on your chain.
With a stable hashrate, even the simpliest diff algo can manage that.
With jump pools steady changing your hashrate to multiples of what it is without them, it is a completely different ball game. Those jump pools are coming in with ALOT of hashrate at a low diff to get some quick blocks and leave as soon as the diff adapts, leaving the chain with high diff and far too low hashrate for that diff. That leads to long block times until the lower hash can finally solve that block with this high diff and the algo can slowly adapt to the lower hash again. And at that point the jump pools are coming back again for more quick blocks, driving the diff high again...
We went trough several diff algos w/o success. Worst day was on May 6 with only 23 blocks solved and the longest block lasting many hours
Our own DELTA diff algo became active on May 17 and improoved the situation reasonable. Even with dramatic drops of hashrate we haven't had a blocktime >90m.
The more dedicated hash we have, the better it works naturally. But even with very low dedicated hash (worst case scenario) it acts like expected and keeps the chain running with limited gaps.
Noone said DELTA was the one and only solution, but it is part of it. A diff algo alone can not solve the situation with jump pools on the chain.
More will come, but not in a rush. Every step has be to seriously thought about and the code tested against every exploid we can think about.
It is not a simple copy&paste job that could be done in a very short time!
Someone been in software development will know what I mean.
Look here
http://explorer.cryptoblox.com/chain/Electronic%20Gulden and tell me their block times are that stable. They have shorter and longer times too, like it is normal even with a stable hash and a diff of only 24 - 29. Amazingsystems.nl shows an avg. block time of 1 minute 50 seconds (target is 2 minutes). They are using KGW (window of 512 blocks) as diff algo which is ok for a stable hashrate like they have.
