NA

[vesperwillow]

Ok, I've been pretty quiet, just watching from the sidelines for many months. After seeing what's begun to happen, I can't just sit down any longer, and I have to wonder what's going on, because something doesn't add up. I'm not sure what it is, but something is starting to smell foul in the kitchen.

There's this never-ending mantra that it's up to the community to decide where things are going to go. You have apt people, from within the community--several of which are heavily invested, and several of which are purely doing it to support the coin--taking it upon themselves to expel resources to determine what is possibly the best path to go down. They then provide the results for the community to examine, and like all results, it just needs a little polishing to really be a great product.

What then happens is someone from on high searches through a haystack to find a needle, and point out how this is a huge issue and isn't worthwhile. Others from the community then pop up and point out how it just needs a little tweak, but is otherwise a good idea, and if nothing else is more effort than has been put forth by anyone else--including the official development team.

If things aren't bad enough, now--despite the community being told they're in control of NLG destiny--the topic is forcibly moved to a non-English speaking forum, a very damning approach. It seems to me that someone doesn't want the community as involved as they claim--the reasons for this are unknown, and I won't speculate on them.

This is a crucial period in time for NLG, whether anyone likes it or not there's a fork in the road coming up and you're going to have to go one way or the other. It appears that things are starting to slowly creep down the same path of coins in the past, where critical indications are ignored and crucial decisions are poorly made, usually too late. Once this coin becomes more popular, hits more coin-presence-tracking websites, you're going to wish you had something in place to handle the ten or fifty-fold increase in hashrate.

These recent developments do not bode well in the eyes of investors who are keeping watch.

[1714751731]

1714751731

[1714751731]

1714751731

[1714751731]

1714751731

[veertje]

you're going to wish you had something in place to handle the ten or fifty-fold increase in hashrate.

That is why the team works on the simulator to get the best algo to handle pooljumps and big waves. https://github.com/GeertJohan/diffsim

It is being worked on. Question is wether there should come a temporary solution by implementing Digi as suggested by Fuse first and later on the custum made algo. This should have been done a few days ago, but there were found some mistakes, that could have made it more worse.

There was some kind of consensus about implementing Digi first without the tests on the sim. The team agreed on that, but was canceled because of some errors. That is the situation we are now atm.

[ArieNLG]

Considering the conversation has been taken to the Dutch section of the Gulden forum, I'm going to take it that my input isn't welcome anymore.

Either way, if Google translate is halfway correct and I'm reading it right, Rijk and the team will look at ready to pull Git code.  So I updated the git-pull, correcting the errors that /GJ noted.  

https://github.com/nlgcoin/guldencoin/pull/8

Stop making excuses, stop dragging your feet, and just fix the damn algorithm already.

-Fuse

+1

The coin is bleeding too long already, use the premine to hire some helping hands please!


Here is a good starter https://www.pexpeppers.com/

[strataghyst]

Considering the conversation has been taken to the Dutch section of the Gulden forum, I'm going to take it that my input isn't welcome anymore.

Either way, if Google translate is halfway correct and I'm reading it right, Rijk and the team will look at ready to pull Git code.  So I updated the git-pull, correcting the errors that /GJ noted. 

https://github.com/nlgcoin/guldencoin/pull/8

Stop making excuses, stop dragging your feet, and just fix the damn algorithm already.

-Fuse

Your input is still very welcome Fuse really! No negative words regarding you or your team.

[vesperwillow]

you're going to wish you had something in place to handle the ten or fifty-fold increase in hashrate.

That is why the team works on the simulator to get the best algo to handle pooljumps and big waves. https://github.com/GeertJohan/diffsim

It is being worked on. Question is wether there should come a temporary solution by implementing Digi as suggested by Fuse first and later on the custum made algo. This should have been done a few days ago, but there were found some mistakes, that could have made it more worse.

There was some kind of consensus about implementing Digi first without the tests on the sim. The team agreed on that, but was canceled because of some errors. That is the situation we are now atm.

I'm fully aware of what occurred, and the issues could've been resolved instantly before initiating change. I find it underwhelming that the team couldn't simply agree to deploy the temporary solution, having been tweaked. What happened is what's been happening, the ongoing delay.

Simulators are wonderful, I've dealt with them in the past, I'm very familiar with difficulty projection. They are long-term goals however. You need a short-term solution right now, and the fact I even have to emphasize this is unfortunate, because it shows lacking foresight on part of whoever is claiming to lead this. This should never have been an issue from the start.

I believe this is why there's mounting frustration, because the need to take action has long passed, and yet, there is no action. I don't mine this coin and have never bought into it, but have been keeping an analysis on it. I believe it has great capability, but things are taking a swift turn for the worse lately.

I'm merely trying to say, from a non-invested analytical point of view, you are in a very dangerous spot right now, and ignoring the need for immediate action by focusing on a long term goal, is quite possibly the worst thing that could be done.

[ny2cafuse]

That is why the team works on the simulator to get the best algo to handle pooljumps and big waves. https://github.com/GeertJohan/diffsim

It is being worked on. Question is wether there should come a temporary solution by implementing Digi as suggested by Fuse first and later on the custum made algo. This should have been done a few days ago, but there were found some mistakes, that could have made it more worse.

There was some kind of consensus about implementing Digi first without the tests on the sim. The team agreed on that, but was canceled because of some errors. That is the situation we are now atm.

2 points to make here:

The simulator, until proven against a live chain or testnet data, is still theoretically unproven.  If you want to take emotion out of the technical discussion, take the emotional attachment of the simulator out of the equation as well.  Finish the simulator, test it against live data, and publish the results for peer review.  Once proven accurate against a live mining simulation, I will accept any and all suggestions to base future decisions on the simulator.  This isn't about my stance vs. your stance, this is us saying that if you want to be accurate and verifiable, then be accurate and verifiable.

Second, the error was minor, it was identified by /GJ, and it could have been rectified by the simple code changes I just posted to GIT.  If /GJ was so confident in not needing the DIGI dev's input, and if the changes were easy to implement, then why have we still not implemented them?  The error was identified, yet I'm still the one to correct it.

I'll let you know that you're losing faith in this community with some very dedicated members.  I have received numerous PMs in the last week regarding this issue.  The community isn't happy about the development cycle, the communication, and the unwillingness to correct obvious problems, temporary or otherwise.  There needs to be a turning point, and it needs to happen soon.

-Fuse

[veertje]

I find it underwhelming that the team couldn't simply agree to deploy the temporary solution, having been tweaked. What happened is what's been happening, the ongoing delay.

The team wanted to deploy the temporary solution, but there where found some mistakes. Now Fuse has just made a new pull request. https://forum.guldencoin.com/index.php?topic=745.msg9522#new  

The one 9 days ago was not good to implement as it seemed.  I think all of us want a quick temporary solution and there was consensus about that.

(I am not a member of the team by the way, just giving the way things went by last 2 weeks)

https://forum.guldencoin.com/index.php?topic=745.msg9522#new, so looking good on that being discussed again.

@ Fuse: I was pro temporary fix, I think most of us were. As I understand now, problems for temporary fix with Digi were minor. Let's wait what GJ has to say tonight.

[LTEX]

I have already stated earlier why I am in alignment with Fuse on this. I do however understand the position of our Dev team as well and respect their judgement, even if I'm not capable enough to comprehend.

I chose not to participate in this discussion just jet, for the simple reason I feel I have more insights on it tomorrow...

[strataghyst]

I also back Fuse in this one fully simply because algorithm change is needed rather now then tomorrow! As there is no time frame given for the simulator and algo change. Don't get me wrong this is not a problem but we need a solution in the meantime.

As Clevermining is breaching the security of this coin and keeping price down.
By doing this it keeps new investors away old one leaving, making it not profitable for new miners to join
and so staying in this vicious circle

[Dutchyyy]

I also back Fuse in this one fully simply because algorithm change is needed rather now then tomorrow! As there is no time frame given for the simulator and algo change. Don't get me wrong this is not a problem but we need a solution in the meantime.

I have gone through the last 100s of pages again and also to catch up on what I have missed.

As much as I don't like Investerdeers attitude he was right all along about the delay the simulator would have on the changes needed. I think a Digi solution would be good now and then the team can focus on the simulator again like Veertje said. Thanks to people like fuse who push things.

edit: Ok Investerdeer I see you giving away your 20 000 towards development of NLG, maybe I am wrong about you.

[bram_vnl]

sometimes you need a break , but you are doing well with the discussion

https://www.youtube.com/watch?v=VH2HfaLDzAs

[ny2cafuse]

sometimes you need a break , but you are doing well with the discussion

https://www.youtube.com/watch?v=VH2HfaLDzAs

+1000 to this post.

-Fuse

[LTEX]

sometimes you need a break , but you are doing well with the discussion

https://www.youtube.com/watch?v=VH2HfaLDzAs

+1000 to this post.

-Fuse

But please... "G-J, do not click on the link!!!!!!"  

[/GeertJohan]

sometimes you need a break , but you are doing well with the discussion

https://www.youtube.com/watch?v=VH2HfaLDzAs

+1000 to this post.

-Fuse

But please... "G-J, do not click on the link!!!!!!"  

zzzzzZZZZZZzzzZZZZZ hmm what!??  zzzzzZZZZZZzzzZZZZZ So relaxing music!

Let me counter that post with some DOWORK music: https://soundcloud.com/toofutureshop/too-future-guest-mix-014-snbrn

(I'm working on Digi in the coin, fuse already provided new code, will post an update here today!)

[Youghoor]

sometimes you need a break , but you are doing well with the discussion

https://www.youtube.com/watch?v=VH2HfaLDzAs

+1000 to this post.

-Fuse

Breaks are always necessary to keep going.

[ny2cafuse]

Breaks are always necessary to keep going.

Unless you're part of the upcoming robot army.  They never take a break... the bastages.



-Fuse

[/GeertJohan]

Fuse, can you join the chat channel at http://chat.guldencoin.com ?
Would like your opinion on some algo related stuff.
Ofcourse, everyone else is also very welcome in the chat!

[bram_vnl]

Fuse, can you join the chat channel at http://chat.guldencoin.com ?
Would like your opinion on some algo related stuff.
Ofcourse, everyone else is also very welcome in the chat!

fuse we miss you  http://chat.guldencoin.com

[Halofire]

Fuse, can you join the chat channel at http://chat.guldencoin.com ?
Would like your opinion on some algo related stuff.
Ofcourse, everyone else is also very welcome in the chat!

*** You are banned from Tweakers (Session limit exceeded) Email kline@tweakers.net for more information.
13:40:50
Disconnected from the IRC network

[ny2cafuse]

Fuse, can you join the chat channel at http://chat.guldencoin.com ?
Would like your opinion on some algo related stuff.
Ofcourse, everyone else is also very welcome in the chat!

*** You are banned from Tweakers (Session limit exceeded) Email kline@tweakers.net for more information.
13:40:50
Disconnected from the IRC network

Server hiccup, I was bounced too.  You should be able to get back in though.

-Fuse