NA

[pijpenstelen]

So excited for this change, we will be one of top alts value wise if this digi change has good effects. It will make everything about this coin good.

[1714647570]

1714647570

[1714647570]

1714647570

[1714647570]

1714647570

[1714647570]

1714647570

[sven22]

For crying out loud people. Focus on the main issue...  And that is replacing the current broken algo with one that keeps MPs at bay.  

It is currently a real struggle to convince those in charge to move from DGW3 to Digi.  It shouldn't be a struggle as just about anything would be preferable to what we have now, but it is a struggle.  They seem to be coming around but will it be before or after Terk kills the coin?  Time will tell.

So.......  Forget about cpu mining, multi pow mining, etc.  It ain't going to happen.  You are just polluting the thread with "fairies at the bottom of the garden" non-solutions.  NLG will be a scrypt coin for the foreseeable future.  It has built up a devoted base of scrypt miners like myself and a change would mean 99% of current miners would go elsewhere.  That would help the coin? NOT.  

BAM! Good words, love it!

Thanks for implementing DIGI, GJ you can breathe more easily now

[LTEX]

I'm glad we didn't blow a "Fuse" with all this "Spanning" 

[sven22]

I'm glad we didn't blow a "Fuse" with all this "Spanning" 

I guess you meant "tension"? Fuse will be most delighted when he wakes up!! Fuse if you really are that happy, I can give you my NLG adress

[CIG]

Good to hear the decision has been taken.

[LTEX]

I'm glad we didn't blow a "Fuse" with all this "Spanning" 

I guess you meant "tension"? Fuse will be most delighted when he wakes up!! Fuse if you really are that happy, I can give you my NLG adress

The Dutch word is better, for it relates to electricity as well, where tension relates to newtons 

[bram_vnl]

15 more days.....

3 days?

[veertje]

Nederlands

De afgelopen weken hebben we de discussie omtrent de difficulty readjustment van dichtbij gevolgd en het is duidelijk geworden wat de volgende stap moet zijn. Nu is het tijd om die stap te zetten. De komende dagen zullen wij meer informatie hierover verstrekken. We zullen nauw samenwerken met ontwikkelaars in de community om ervoor te zorgen dat het een soepele overgang wordt.

Als je zorgen of bezwaren hebt, maak ze bekend op het officiele forum: https://forum.guldencoin.com/index.php?topic=745.0

English

For the last weeks we’ve been following the difficulty readjustment discussion closely and it is clear what the next step should be. Now its time to take that next step. In the coming days we will provide more information about this. We will work closely with developers in the community to make sure it will be a smooth transition.

If you have any concerns or objections please make them known at the official forum: https://forum.guldencoin.com/index.php?topic=745.0

Bump, because of new page and the most important topic today ofcourse  

[ny2cafuse]

I'm glad we didn't blow a "Fuse" with all this "Spanning" 

I guess you meant "tension"? Fuse will be most delighted when he wakes up!! Fuse if you really are that happy, I can give you my NLG adress

I'm glad to hear that the DIGI solution is being implemented.  But let me say this- this isn't a win for me.  My team and I just took the time to test the solution we thought would work, and it worked.

The win here belongs to the community.  While everyone might not have the same ideas, we came together and made a decision as a whole.  Sure, I really pressed hard for the decision to favor my team's findings, but we made a decision none the less.

Actions speak louder than words.  Today we spoke.


That being said, I would love people to look over the code to make sure I didn't miss anything.  /GJ will be looking at it, but a second or third set of eyes would be good to make sure we're solid going into the transition.  I know I missed adding a checkpoint in my git pull, but I figured I'd let the devs make the checkpoint additions.  The code, the way I submitted it, was the code used to get the graph results I presented, minus the change from 20% to 25%.  Our results with 25% were very aggressive, but still effective.  I don't have charts for the 25% tests, but I can say that they were similar in movement.  Either way, we're not going to overshoot the sweet spot, and we're not going to drop to a false low.

-Fuse

[sven22]

I'm glad we didn't blow a "Fuse" with all this "Spanning" 

I guess you meant "tension"? Fuse will be most delighted when he wakes up!! Fuse if you really are that happy, I can give you my NLG adress

I'm glad to hear that the DIGI solution is being implemented.  But let me say this- this isn't a win for me.  My team and I just took the time to test the solution we thought would work, and it worked.

The win here belongs to the community.  While everyone might not have the same ideas, we came together and made a decision as a whole.  Sure, I really pressed hard for the decision to favor my team's findings, but we made a decision none the less.

Actions speak louder than words.  Today we spoke.


That being said, I would love people to look over the code to make sure I didn't miss anything.  /GJ will be looking at it, but a second or third set of eyes would be good to make sure we're solid going into the transition.  I know I missed adding a checkpoint in my git pull, but I figured I'd let the devs make the checkpoint additions.  The code, the way I submitted it, was the code used to get the graph results I presented, minus the change from 20% to 25%.  Our results with 25% were very aggressive, but still effective.  I don't have charts for the 25% tests, but I can say that they were similar in movement.  Either way, we're not going to overshoot the sweet spot, and we're not going to drop to a false low.

-Fuse

I know Fuse, but I was thought because of this change, if someone would be most delighted about this, it would be you!!

Off course this is a win for the community, we all pressed for a change!

[strataghyst]

Nederlands

De afgelopen weken hebben we de discussie omtrent de difficulty readjustment van dichtbij gevolgd en het is duidelijk geworden wat de volgende stap moet zijn. Nu is het tijd om die stap te zetten. De komende dagen zullen wij meer informatie hierover verstrekken. We zullen nauw samenwerken met ontwikkelaars in de community om ervoor te zorgen dat het een soepele overgang wordt.

Als je zorgen of bezwaren hebt, maak ze bekend op het officiele forum: https://forum.guldencoin.com/index.php?topic=745.0

English

For the last weeks we’ve been following the difficulty readjustment discussion closely and it is clear what the next step should be. Now its time to take that next step. In the coming days we will provide more information about this. We will work closely with developers in the community to make sure it will be a smooth transition.

If you have any concerns or objections please make them known at the official forum: https://forum.guldencoin.com/index.php?topic=745.0

Bump, because of new page and the most important topic today ofcourse  

Really exited to see this!

[ny2cafuse]

I know Fuse, but I was thought because of this change, if someone would be most delighted about this, it would be you!!

Off course this is a win for the community, we all pressed for a change!

Don't get me wrong... I'm freaking ecstatic lol.  We'll finally take back our chain from CM.  Me this morning:



-Fuse

[BioMike]

So, how long before we can download the new client? And the block where DIGI goes into effect?

[BioMike]

Hmm, one more problem when Clever gets kicked off the chain... Criptoe will get >50% of the hash rate.

[Frais]

Hmm, one more problem when Clever gets kicked off the chain... Criptoe will get >50% of the hash rate.

Maybe we can block their ip address! 

[sven22]

Hmm, one more problem when Clever gets kicked off the chain... Criptoe will get >50% of the hash rate.

Hahaha

I know Fuse, but I was thought because of this change, if someone would be most delighted about this, it would be you!!

Off course this is a win for the community, we all pressed for a change!

Don't get me wrong... I'm freaking ecstatic lol.  We'll finally take back our chain from CM.  Me this morning:



-Fuse

Laughed even louder hahaha!

[veertje]

For clearance about the change with Digishield:

So testing has been done with Digishield with 150 sec. blocktime and 1000 blockreward, am I right, Fuse?
Or has 75 sec. blocktime with 500 blockreward been tested as well, as 24Kilo suggested to do with Digishield? That would even be better or am I wrong in this? Which one will it be, is that clear yet?

• reducing the block time to 75sec cuts transaction times by greater than 50%, speeding up transactions
• reducing the block reward to 500NLG maintains the current number of NLG minted per 24hrs
• increases the number of diff increments by 100% per 24hrs, from 576 to 1152
• reduces the number of blocks a high-hash-rate attacking miner/multipool can mint by 80%
• these changes support the community vision of NLG becoming a daily use currency
• the only down side of this proposal is that the block chain storage requirement would double, but still be less than most alt-coins

[xtrix]

Thumbs up for DigiShield!    

[ny2cafuse]

For clearance about the change with Digishield:

So testing has been done with Digishield with 150 sec. blocktime and 1000 blockreward, am I right, Fuse?
Or has 75 sec. blocktime with 500 blockreward been tested as well, as 24Kilo suggested to do with Digishield? That would even be better or am I wrong in this? Which one will it be, is that clear yet?

We did not test the shorter block time.  All testing was done with our current values.  The numbers Kilo has stated are mathematical inferences that can be derived from the proposed changes.  See my reply to /GJ about these numbers for clarification.

The change in block time is not a priority, nor is it a necessity.  It was an additional suggestion that would be beneficial in the long run, and something we can discuss at a later date.  It's a suggestion I fully stand behind though.  The Criptoe team will most likely test this in the future as well, and we'll provide data if it's requested by the dev team.

Hmm, one more problem when Clever gets kicked off the chain... Criptoe will get >50% of the hash rate.

This is a concern for sure, but there are at least 3 other active NLG pools, including the coiniumserv pool that was announced recently.  Understand this though... I don't have an interest in running away with the network.  Unlike CM, we don't need to worry if my pool breaks 50%... we just need to readjust and spread the hashes.

Recently, 24Kilo has expressed interest running pools.  Another member of our team, Vesperwillow, has run pools for testing and private mining.  I'll see if I can help either one of them get a pool up and running to give the community additional options.

-Fuse

[veertje]

For clearance about the change with Digishield:

So testing has been done with Digishield with 150 sec. blocktime and 1000 blockreward, am I right, Fuse?
Or has 75 sec. blocktime with 500 blockreward been tested as well, as 24Kilo suggested to do with Digishield? That would even be better or am I wrong in this? Which one will it be, is that clear yet?

We did not test the shorter block time.  All testing was done with our current values.

The change in block time is not a priority, nor is it a necessity.  It was an additional suggestion that would be beneficial in the long run, and something we can discuss at a later date.  It's a suggestion I fully stand behind though.  The Criptoe team will most likely test this in the future as well, and we'll provide data if it's requested by the dev team.

Ok, that makes it clear.