NA

[BlockEruptor]

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.

[1714504896]

1714504896

[WaterLooDown]

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.

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.

[WaterLooDown]

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

[Bluestreet]

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

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

[bram_vnl]

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

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

Update wallet 1.5.5

Send tweet @gulden_fan https://twitter.com/Gulden_fan/status/667358729558470657
Dutch ANN https://bitcointalk.org/index.php?topic=886372
Reddit http://reddit.com/r/gulden
google+ https://plus.google.com/u/1/103372380374548751151
wallet links update http://guldenlinks.com

[veertje]

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?

[ocminer]

Suprnova is updated

[strataghyst]

deguldenmijn.eu also update to 1.5.5 happy mining

[veertje]

73.9% already on version 1.5.5  

[0btc]

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.)

[Chris Sokolowski]

Prohashing is now updated to version 1.5.5

[smarterhash]

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

[Dutchyyy]

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

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

Update wallet 1.5.5

Send tweet @gulden_fan https://twitter.com/Gulden_fan/status/667358729558470657
Dutch ANN https://bitcointalk.org/index.php?topic=886372
Reddit http://reddit.com/r/gulden
google+ https://plus.google.com/u/1/103372380374548751151
wallet links update http://guldenlinks.com

Outstanding work team!

[Buy$Polar]

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.

[WaterLooDown]

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.

Hi Buy$Polar,
Prevent of double spend 51% attacks including a failsafe that was developed by MaNI. We have double prevention for a double spend 51% attack now.

[WaterLooDown]

Bittrex has enabled wallets again.

Time to move forward onto the development we were meant to bring out this week. More on that next week.

[Buy$Polar]

Hi Buy$Polar,
Prevent of double spend 51% attacks including a failsafe that was developed by MaNI. We have double prevention for a double spend 51% attack now.

OK, so you are saying someone did bring more than 51% computation power against the network.
How does the failsafe work in general terms?
Thanks.

[MaNI]

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.

We didn't patch any bugs specifically, as the double spending was not as the result of a 'bug' but rather is just a design limit of how crypto coins work - if you have 50% you can execute double spends.
What we have done is we have added an automated checkpoint system as an extra, this is intended to protect the network against double spends so long as you only deal with transactions that have been checkpointed you will be safe from a double spend.

In the long/medium term we have some better solutions we are considering which will then replace this solution.

Not specifically related to a timewarp attack at all.

[Buy$Polar]

We didn't patch any bugs specifically, as the double spending was not as the result of a 'bug' but rather is just a design limit of how crypto coins work - if you have 50% you can execute double spends.
What we have done is we have added an automated checkpoint system as an extra, this is intended to protect the network against double spends so long as you only deal with transactions that have been checkpointed you will be safe from a double spend.

Not specifically related to the timewarp attack which is mostly a problem for PoS coins.

COOL , 
how would I know when the transaction is checkpointed?
Thanks.

[MaNI]

We didn't patch any bugs specifically, as the double spending was not as the result of a 'bug' but rather is just a design limit of how crypto coins work - if you have 50% you can execute double spends.
What we have done is we have added an automated checkpoint system as an extra, this is intended to protect the network against double spends so long as you only deal with transactions that have been checkpointed you will be safe from a double spend.

Not specifically related to the timewarp attack which is mostly a problem for PoS coins.

COOL , 
how would I know when the transaction is checkpointed?
Thanks.

As a regular user you can just look in your transaction list, transactions will not get a check mark next to them until they are safely behind a checkpoint.

From an API perspective we have modified the 'listtransactions' RPC call to have a new field "secured_by_checkpoint" which will contain "yes" if the transaction is check pointed and "no" if it is not, we have also added a configuration option which can be set if you want 'listtransactions' to only ever return check pointed transactions.
It is up to all services to make use of these if they want to be 100% safe in terms of double spends, however the checkpointing does help quite a bit even if they don't as it makes the attacks a lot harder to execute smoothly anyway.