Topic: NA - page 34. (Read 893616 times)

Question,

Looking at your commits, (not a programmer so bear with me) ,
it looks like what you patched was the timewarp attack discovered by presstab a few months ago.
Is that accurate?
or
did i misunderstand, because the comments about stopping a 51% attack made no sense to me.
51% attacks can happen anytime to a PoW coin if someone brings 51% or more computation power to a coin's network.
But since you made a sotfware fix, it does not seem likely it was a 51% attack.
So what exactly was fixed.
Thanks.

Outstanding work team!

http://nlg.smarterhash.com updated to 1.5.5

Prohashing is now updated to version 1.5.5

guldenpool.nl has been updated to 1.5.5 as well!
Enjoy the special "0x0a update fee" of just 0.5% while you can! (Note: it won't change, so you have all the time in the world.)

73.9% already on version 1.5.5  

deguldenmijn.eu also update to 1.5.5 happy mining

Suprnova is updated

New multipool that pays out in Gulden. You can mine there most profitable sha256 coins and get paid in Gulden (NLG). Also scrypt coins, but i will keep my scrypt hash at the dedicated Gulden pools for the moment.

http://hashgoal.com/

Always put .NLG behind your address, that you are mining with as username.

I am using my old sha256 usb miner again to get paid in Gulden Someone who wants to join me there hashing sha256?

Update wallet 1.5.5

Send tweet @gulden_fan https://twitter.com/Gulden_fan/status/667358729558470657
Dutch ANN https://bitcointalksearch.org/topic/ann-gulden-nlg-guldencomnl-886372
Reddit http://reddit.com/r/gulden
google+ https://plus.google.com/u/1/103372380374548751151
wallet links update http://guldenlinks.com

Hell you boys work fast! New wallet downloaded and fantastic job finding a solution to 51% attack so damn fast!!

Firstly I would like to thank everyone for their patience during this trying time of securing the Gulden blockchain. Unfortunately there was a issue with the 1.5.4 version released yesterday which has been resolved. These types of things are bound to happen when you making changes that would have a development cycle of 3 months squeezed into less then 5 days.
I am extremely proud of the work the dev team has done especially MaNI and the community who has helped spread the news to various sites and services, Thank you!

Please update to version 1.5.5 ASAP


Latest version: v1.5.5.0 (19-11-2015)
Source: https://github.com/gulden/gulden-official
Apps: https://developer.gulden.com/apps

Hi BlockEruptor,

We are in the process of building new wallets and once we have confirmed all is working and we happy with the implementation, bittrex deposits will be turned on again. Thank you for your patience.

The attackers have hurt various miners profits with the downtime on Bittrex exchange. We would like to fork a few coins in response to this that are not on our list of coins we mine. Please send a message to me on which other coins would attack Gulden and we will inflict some pain.

They are tagged, however I will make a point of including it in the commit message as well 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.

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.

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)

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

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

Thanks @Patrick and @Chris for updating here.