NA

[wargo]

http://www.e-waluty.net.pl

Better link to pool subdomain. And explorer available.

That link is broken for me, can you please confirm it Wargo.

Yes, use without www. Thanks.

[1714487554]

1714487554

[1714487554]

1714487554

[1714487554]

1714487554

[1714487554]

1714487554

[ocminer]

https://nlg.suprnova.cc is updated too !

[investeerder]

Hey Guys,

I stalk a lot of forums and chats, rarely to I join one. I specifically joined this one for Guldencoin, I just actually want to get involved in the community. I will be 100 percent, I am in crypto mostly for pump and dump, because thats what 95+ percent of coins are on any of these exchanges. NLG is my only investment where i actually feel like this coin has potential to be adopted and I want to first of all give the dev's and this strong community credit for achieving the rare feat of creating a real coin, which can be scaled and adopted, even if just at a regional level.

Okay, so kissing all your asses aside, with the recent disabling in Bittrex i feel like we will have a drop in the NLG price. I am getting together some BTC to buy in depending on the overhype of this event, as a disabling almost always causes huge spike downward before a correction.

I know it sounds kind of basic but i wanted to get a feeling of how many of you are in the same boat? And if not, why have you lost confidence in NLG, to my newbie tech understanding this disabling was relatively minor and the devs reaction should instill confidence. Also just in general, why specifically do you believe or do not believe in  NLG as a future significant crypto currency? What trends are you seeing in the trading, as i see a constant volume with a pretty good trading opportunity as the price is constantly cyclical, with an upward trend usually. Also what are your thoughts on the latest pump, does anyone have an idea of distrubition of the coins between groups, devs, whales, etc?

Hope these aint some basic bitch questions for y'all on my first post, but again I literally have no other coin in my alt crypto (obviously BTC is the other one) portfolio that I am long in and am not just p and d'ing. So just really interested in what you guys think, and if possible to get a clearer and more detailed understanding of the future plan for NLG, it's selling points, trading strategies, etc.

Thanks for any feedback guys, yadadadadda yeeeeeee

No confidence lost with me, this has made me more confident because it makes it clear that NLG is a threat to other coins and they want to destroy us. Tamilee made a suggestion to hit back at other coins if we attacked again and crush the whole of the crypto market for good. This way we all lose and not just Gulden investors and fiat wins. Then the fucks that attacked us can rejoice for taking down the only chance we had at a fair currency. Destroy so many alt coins that it makes news and destroys reputation of all cryptos including bitcoin.

These attackers must be very happy I don't have the knowledge our dev team has of taking revenge.

Do this only after Gulden has done it's own fix. After a 3rd attack it might be the only deterrent to hit back, start with coins that are most likely involved until the attacker/s own up.

The new wallets being released today?

What is the channel/s on IRC used for Gulden ? I have a few friends with high level access that owe me some favors. Has anyone owned up to the attack?

[sunsofdust]

CoinWarz just posted on Twitter that they updated the wallet as well.

https://twitter.com/CoinWarz/status/667063360463073280

[bram_vnl]

http://www.e-waluty.net.pl

Better link to pool subdomain. And explorer available.

update guldenlinks.com

add new gulden block explorer

http://explorer.e-waluty.net.pl/NLG

[MaNI]

What is the channel/s on IRC used for Gulden ?

We are in #gulden on freenode - however it is rather small, the slack community is much larger.

[fredeq]

Someone named "Di Cabrio" requested a wallet update from my site and to report back here.
Just for the record my site does not host wallets, but uses external stats (suprnova pool in this case), so no update is required.

Thank you for the notification though, whoever you are
As far as I can see, we are not changing any specs? Just a security update?

[investeerder]

What is the channel/s on IRC used for Gulden ?

We are in #gulden on freenode - however it is rather small, the slack community is much larger.

Any other channels I must ask them to look into?

[Dutchyyy]

What is the channel/s on IRC used for Gulden ?

We are in #gulden on freenode - however it is rather small, the slack community is much larger.

Any other channels I must ask them to look into?

#bittrex was the exchange the attack took place.

[veertje]

As far as I can see, we are not changing any specs? Just a security update?

Indeed no change of specs. Thanks for updating. All (most) wallets, pools and services need to be on 1.5.4. to have effect, as i understand. That's why it is important that the nodes are on 1.5.4. soon. But i am not that technical though, maybe MaNI can explain better.

[investeerder]

What is the channel/s on IRC used for Gulden ?

We are in #gulden on freenode - however it is rather small, the slack community is much larger.

Any other channels I must ask them to look into?

#bittrex was the exchange the attack took place.

Can I get date and time ?

[veertje]

Because of new page.

[patrickkivits]

Guldenhash wallet is updated to 1.5.4: http://pool.guldenhash.com:8000

[Chris Sokolowski]

The Prohashing scrypt mining pool is updated to version 1.5.4

[WaterLooDown]

Thanks @Patrick and @Chris for updating here.

[wargo]

What kind of issue and does it require code changes in future? Can it happen again?

[WaterLooDown]

What kind of issue and does it require code changes in future? Can it happen again?

We will be released version 1.5.5 later this evening to resolve the issue.

[dbkeys]

The code on github, https://github.com/Gulden/gulden-official  (master) version, although it does show the latest commit to be within the day, is not explicit in proclaiming it's version 1.5.4.  It would be reassuring to see that version number, or in the case of going to 1.5.5,  _that_ version number.  (The only version numbers visible when you go to there are 1.5.1 and 1.5.2)

[MaNI]

What kind of issue and does it require code changes in future?

After testing I did a final code review, the check-pointing code we used as a base for ours had while loops without control braces which is not something that is usually recommended and causes warnings with many compilers, so I re-factored this to put control braces.Due to some weird white space and  tiredness/stress I accidentally got the one set of braces wrong and slightly changed how the code worked. This has caused the checkpoint to reject valid blocks if activated in some cases.

I should have known better than to do any refactoring even if it seemed really trivial as main testing had already been done, unfortunately when resources are stretched thin and stress levels are high sometimes these things happen.

We have been working hard on improving our testing - one of the lesser publicised changes about 1.5.4 is that we now have a permanent live public testnet, and we want to work on getting more community members involved in helping us test in future, so hopefully we can grow the team in a way that helps prevent these things in future.

Can it happen again?

Anything is possible but it is not likely, I've now triple checked that the code is the same as what we had when testing and am doing some retesting to be sure, the new builds are on the way and will work.


Apologies to everyone for the extra hassle here.

[MaNI]

The code on github, https://github.com/Gulden/gulden-official  (master) version, although it does show the latest commit to be within the day, is not explicit in proclaiming it's version 1.5.4.  It would be reassuring to see that version number, or in the case of going to 1.5.5,  _that_ version number.  (The only version numbers visible when you go to there are 1.5.1 and 1.5.2)

They are tagged, however I will make a point of including it in the commit message as well in future.