The inability of NLG to be used for wallet to wallet transactions is starting to sour me on this coin. Yesterday the network was stuck at a diff of 777 for well over 2 hours, and again this morning the network was stuck for over an hour at a diff 497, during which time it is impossible to transfer NLG from wallet to wallet.

It is all fine and good that LiteBit? approves NLG transactions immediately regardless of network status, but for NLG to not be useable for wallet to wallet transactions is killing NLG.

The dev team must assess and address this immediately, there are plenty of coins that are using retargeting algos that are effective when dealing with network hashrate spikes. This is not rocket science, the dev team seems to burying their collective heads in the sand and hoping for the best.

DGW3 is not working, find a solution. Now!!!

For those interested in some daily mining statistics about NLG, feel free to head over to http://nlgstats.iblogger.org  (appologize for the crude html, not my thing).  This has been my scratchpad to learn about interact with the blockchain.  Will gladly try my best to add any additional info to the daily stats if it will help.  Just shoot me a PM with ideas.  If additional products are needed I'll see what I can do.  There is also an NLG richlist (top 100 addresses) for those interested in those types of things.  I'll update at least daily, just remember to refresh (F5?) for the latest info.  Chrome likes to cache.

RE: Long block gaps:  In my humble opinion regarding large scrypt multi-pools, I'm against IP blocking.  In the immediate short term let's reach out to clevermining and try to tweak their NLG targeting to avoid these long block gaps?  Based on his previous posts they seem reasonable and willing to work with us.  It is probably is more efficient for clevermining to have a dialog with one 1 NLG rep (dev?) and hopefully the information coming out of those talks will flow here in a timely fashion?   Appreciate the NLG devs are being cautious and providing more frequent updates on progress.  Investigations, simulation and analysis take time if done properly and nobody has unlimited free time. 

We apologize if we gave the impression we bury our heads in the sand or didn't inform properly about the current situation. We recognize your frustration and are fully aware that DGW3 is not fixing the issue of multipools. This is still our number one priority and we are investigating other algo's, but its simply not a matter of copy paste, as other coins have different configurations and the scenarios are different. So we have to investigate, run simulations and even think about custom made algo's, as you can imagine something like that will take time.

Also to be aware of what is happening we've spend a lot of time developing tools like explorer.guldencoin.com and seeds.guldencoin.com. These tools can help us now and in the future to get the information we need to find a good solution. The crypto landscape is always changing and Guldencoin is a long term project, so tools like these are very important as they provide us a clear overview of what's happening.

The fact that LitePaid approves NLG transactions immediately is NOT a solution, but it means that merchants won't notice these current spikes and can do business like they expect and demand. LitePaid is a third party company that provides merchants with a service and for merchants to even consider accepting crypto we need services like LitePaid, for now that is. I can't think of one serious merchant for NLG or BTC that doesn't work with a third party payment provider. In the future when Guldencoin is a more recognized payment method, merchant will choose to accept Guldencoin directly, instead of converting directly to EUR. Currently some merchants are getting paid in Guldencoin through LitePaid instead of EUR.

So yes its a very serious and frustrating issue which needs to be addressed immediately and we doing everything in our capability to do so, but we don't have the solution yet. So like before we implemented DGW3 the community helped us a lot by discussing different algo's, I would like to ask the community to help us again. We all want to solve this quickly. So when you look into other coins with working algo's, please also compare the other factors.

DGW3 is not the solution, we are doing everything in our capability to find the solution. Let's work together on this and get the network healthy.

I understand miners quit the Guldencoin and now we have a problem with multipools? why? I thought that multipools are also miners but they are switching between the most pofitable coins. What is the problem with that?

I just sent a message to Terk asking if he can take a look at the amount of hashrate thrown at NLG.

DGW3 does better re-adjustment than KGW, but as we can see it's not good enough.
DGW3 calculates diff based on the 24 last blocks.
When there's a long blocktime, and then someone mines 1 block, then clevermining takes 23 blocks, the long blocktime block is not taken into the calculation anymore, and the diff spikes.
Now I hear you say: "why don't we increase the number of blocks taken into the DGW3 calculation". Well, I did some simulations and I believe in the end that will only affect the number of blocks clevermining gets before the diff spikes.

So we need something clever (no pun intended).

There are two methods:
- create a re-adjustment algorithm that is actually pretty smart, detecting patterns, applying penalties if a lot of blocks were mined in short time.
- work out how a block reward based on block time. e.g.: `reward = 1000 * (secsSinceLastBlock/150)` with a max of, say, 3000 (after 3x the target blocktime).

Best would be: both.

Please let me know what you think about this!
I'll work out more details this evening (CEST).