[ANN] Gold Coin Hard Fork - Update your Binaries Immediately

[gldcoin]

.

[Hazard]

No explanation? Seems legit 

[BitshireHashaway]

No explanation? Seems legit 

It was to decrease the difficulty update time, which was too high. when people attacked the networks to jump the difficulty, it was taking to long for the difficulty to come down. as a result high difficulty meant a long time for transactions and such.

[Hazard]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

[BitshireHashaway]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

Depends. We decided in this case not to do that due to the risk of attacks which could slow down the time it takes to reach a fork if we wait for a certain block to be reached. Therefore we decided to give it to the exchanges/cryptsy and then release it at one time in order to decrease the chance of such an attack. There was risk involved in this, however, the coin was dying without a fork due to the high difficulty.

[smoothie]

Miners, users, traders, pool operators etc - update your binaries immediately.

The Binaries are here:

Windows: https://docs.google.com/file/d/0B5Jeb5kpOWshVVM1ZVFCV0RpSmM/edit?usp=sharing
Linux: https://docs.google.com/file/d/0B5Jeb5kpOWshekxOUnIzb2pXNkE/edit?usp=sharing
Source: https://github.com/gldcoin/gldcoin

INSTRUCTIONS:

1) Backup your wallet! File>Backup Wallet
2) Add this into your config file:

addnode=72.11.149.185
addnode=207.12.89.2
addnode=208.115.109.157
addnode=80.229.2.127

3) Install the update (replace gldcoin-qt.exe OR install using the installer)
4) Start gldcoin-qt (or daemon etc)
5) It will NOT sync until the next block is mined.  Once the next block after running it is mined, it will sync.
6) DO NOT ever run an older version of this software as it will corrupt your wallet!!!  Be sure its backed up.

Please notify any GLDcoin pool operator of this update.

NO list of changes...good job. No reason...just update now lolz

[kr4x]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

It was decided as a community to keep this hard for private until released

[smoothie]

No explanation? Seems legit 

It was to decrease the difficulty update time, which was too high. when people attacked the networks to jump the difficulty, it was taking to long for the difficulty to come down. as a result high difficulty meant a long time for transactions and such.

This is the exact same problem FTC had.

These new alt coins need to come up with a different POW. Then at least the development of new GPU mining software will take time to implement.

Fixing these things by lowering the diff in a hard fork or capping max diff adjustments is a result of poor planning and foresight.

Trash IMHO.

[seleme]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

Anyone interested knew that hard fork is coming for days  

Fixing these things by lowering the diff in a hard fork or capping max diff adjustments is a result of poor planning and foresight.

Agree with this though. People should never start with such big adjustments after TRC, FTC or CNC problems.

[Hazard]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

Anyone interested knew that hard fork is coming for days  

All 6 of you that still care about this coin?

As for the "risk of attack", do you really think anyone gives a shit enough to attack this premined garbagecoin? Let's be honest here.

[seleme]

Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.

I'm grabbing my popcorn and waiting for the shitstorm to play out.

Anyone interested knew that hard fork is coming for days  

All 6 of you that still care about this coin?

I certainly don't care what you care about, I'll be fine with other stuff 

[Hazard]

I'm sure you guys informed users that a hard fork was coming using the Alert System to ensure a smooth transition.

Oh wait, you didn't, because I looked at your source code and it's using the Litecoin master keys. Maybe if coblee is nice, you can get him to broadcast a message for you

[seleme]

Can someone post current conf file please, haven't saved it 

[seleme]

I'm sure you guys informed users that a hard fork was coming using the Alert System to ensure a smooth transition.

Oh wait, you didn't, because I looked at your source code and it's using the Litecoin master keys. Maybe if coblee is nice, you can get him to broadcast a message for you

I can alert all 20 or so people easily lol...  no need for all that

It's 5, not 20 

[BitshireHashaway]

Can someone post current conf file please, haven't saved it 

rpcuser=1
rpcpassword=1
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0

addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=208.115.109.157
addnode=80.229.2.127

[seleme]

Cheers  

Eh, what was it's name - gldcoin.conf or goldcoin.conf

[bobbix]

is this about to happen or has it already happened....the fork?

[BitshireHashaway]

is this about to happen or has it already happened....the fork?

Already happened... download the new client!

[BitshireHashaway]

is this about to happen or has it already happened....the fork?

Already happened... download the new client!

Well already released... the fork is some blocks in the future!

[AZIZ1977]

 

[BitshireHashaway]

Has the difficulty dropped yet?

[AZIZ1977]

Has the difficulty dropped yet?

we still need 150 blocks.

[BitshireHashaway]

Has the difficulty dropped yet?

we still need 150 blocks.

Its getting there:)

[AZIZ1977]

 

[BitshireHashaway]

Over 500 given away today, lets get this show on the road w/ new recruits!

[seleme]

at what block it kicks in?

[akumaburn]

at what block it kicks in?

Block 21,000 -I think.

[seleme]

than we'll hit it in day or two I guess.. yesterday we were at middle 2070s and if it is 150 more than it's 2 days max.

[akumaburn]

than we'll hit it in day or two I guess.. yesterday we were at middle 2070s and if it is 150 more than it's 2 days max.

Right now we are at 20766

We seem to be solving 25 blocks minimum a day so about 9 more days maximum.

Bring more miners if you can.

[BitshireHashaway]

than we'll hit it in day or two I guess.. yesterday we were at middle 2070s and if it is 150 more than it's 2 days max.

Right now we are at 20766

We seem to be solving 25 blocks minimum a day so about 9 more days maximum.

Bring more miners if you can.

Nah, were speeding up... 11 in the past few hours.

[BitcoinFX]

Can someone post current conf file please, haven't saved it  

rpcuser=1
rpcpassword=1
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0

addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=208.115.109.157
addnode=80.229.2.127

You must use a Random (and long) password for these settings and a different user name or you can have your .wallet 'hacked'...

Following this post I saw numerous network access attempts, from known 'bad' IP ranges, scanning rpcport 8122 probably for this very purpose.

Please read this post: https://bitcointalk.org/index.php?topic=205789.msg2362993#msg2362993