[ANN] GameCoin (GME) - Current version = v0.8.4.2

[Petr1fied]

Lets try not to invite further attacks please. I've seen the suggestion by BCX and I've chosen to stay on the course that I have set. I have no intention to keep releasing clients every other day and labelling them as mandatory updates. This is as annoying for me as I'm sure it is for everyone else. Just once I'd like to release a client that only has minor changes like checkpoints added.

There are at least 50+ coins using 1 minute block times or less and the only reason GameCoin is more vulnerable than any of these coins is because there is very little miner support for GME which makes it easy to overwhelm. If you want it to survive then stop following coinchoose to the most profitable coin and actually mine GME. It really is that simple.

If you guys think the plan of action is not correct then just stick with GameCoin v0.8.2.1 and you can continue along the original fork at block 64,000. The miners will ultimately decide the way forward and whether or not GME will survive.

[1714286327]

1714286327

[1714286327]

1714286327

[1714286327]

1714286327

[bluestang]

Lets try not to invite further attacks please. I've seen the suggestion by BCX and I've chosen to stay on the course that I have set. I have no intention to keep releasing clients every other day and labelling them as mandatory updates. This is as annoying for me as I'm sure it is for everyone else. Just once I'd like to release a client that only has minor changes like checkpoints added.

There are at least 50+ coins using 1 minute block times or less and the only reason GameCoin is more vulnerable than any of these coins is because there is very little miner support for GME which makes it easy to overwhelm. If you want it to survive then stop following coinchoose to the most profitable coin and actually mine GME. It really is that simple.

If you guys think the plan of action is not correct then just stick with GameCoin v0.8.2.1 and you can continue along the original fork at block 64,000. The miners will ultimately decide the way forward and whether or not GME will survive.

+1

Mine, not whine please!

[Miner-TE]

Lets try not to invite further attacks please. I've seen the suggestion by BCX and I've chosen to stay on the course that I have set. I have no intention to keep releasing clients every other day and labelling them as mandatory updates. This is as annoying for me as I'm sure it is for everyone else. Just once I'd like to release a client that only has minor changes like checkpoints added.

There are at least 50+ coins using 1 minute block times or less and the only reason GameCoin is more vulnerable than any of these coins is because there is very little miner support for GME which makes it easy to overwhelm. If you want it to survive then stop following coinchoose to the most profitable coin and actually mine GME. It really is that simple.

If you guys think the plan of action is not correct then just stick with GameCoin v0.8.2.1 and you can continue along the original fork at block 64,000. The miners will ultimately decide the way forward and whether or not GME will survive.

For the record, I'm behind you and support your decision.  I'll keep mining GME on the V0.8.3.1 client/chain.

BitcoinEXPres: My hats off to you sir.  You wield great power and knowledge. 

[Oldminer]

Only 13 blocks to go..(the hardfork was brought forward to 62,400 correct?)

Is StevenLam in the house?  

[erk]

According to the blockchain we are on block 63382  

You can thank a couple of us from the Crypsty chat box ( me and bluestang) that decided to start mining GME about 7 hours ago! Nobody was mining it that was why it was stuck on block 63381

[Oldminer]

According to the blockchain we are on block 63382 

You can thank a couple of us from the Crypsty chat box that decided to start mining GME about 7 hours ago! Nobody was mining it that was why it was stuck on block 63381

That's so wrong its laughable.


~BCX~

You on the wrong chain now BE? Waste hash much? 

[erk]

Only 13 blocks to go..(the hardfork was brought forward to 62,400 correct?)

Is StevenLam in the house?  

I thought the hard fork was moved to block 64,000 so it's over 600 blocks away.! I will keep mining, but it would be nice to see the GME community make an effort.

According to the blockchain we are on block 63382  

You can thank a couple of us from the Crypsty chat box that decided to start mining GME about 7 hours ago! Nobody was mining it that was why it was stuck on block 63381

That's so wrong its laughable.


~BCX~

Check the payout address on the block explorer for the last half a dozen block mined, it's all the same it's http://gme.crypto-expert.com/ and I am the top hash rate contributor with just 500kH/s. I only registered there about 8hr ago. Now if I could just figure out how to get the pool to payout into my brand new GME wallet!

[ahmed_bodi]

erk it wont payout yet, im still auditing the blocks which has become a lengthy process even if its only for the next 4k blocks left

[erk]

erk it wont payout yet, im still auditing the blocks which has become a lengthy process even if its only for the next 4k blocks left

No worries, not fussed, I just keep getting these warning messages when I refresh the page that tell me:

You have exceeded the pools configured GME warning threshold. Please initiate a transfer!

It's not assigning the name of the miner to the blocks either, I think the pool mined the same block numbers on the wrong fork a few days ago and can't handle repeat block numbers.

Might be a good idea to create a new wallet address for the pool, as the old one has had too many transactions so the block chain explorer page wont display it! Makes it hard to audit the wallet.

[bluestang]

Alright, enough already people!

Live and learn...then shut the fuck up and mine the coin you want to support.  I don't know about the rest of you, but this isn't a hobby for me...I actually need this shit right now to get back on the exchange.

[erk]

Alright, enough already people!

Live and learn...then shut the fuck up and mine the coin you want to support.  I don't know about the rest of you, but this isn't a hobby for me...I actually need this shit right now to get back on the exchange.

This is very easy to understand.

1. The coin is currently being attacked.
2. We can make the changes to the code that the attacker has suggested, or continue on and let the attack persist.
Or
3. Ignore every word from the attacker and continue to think that we are progressing on the correct chain.

Words from the attacker:

Code:

BitcoinEXPres574: @Stouse49: Because I have one locked down in a time warp at 63381 and the other is advancing. When you guys mine about a 1000 blocks, I will drop about 400 mhs on the time warped chain and pass you, becoming the longer chain and invalidating everything behind me for a 1000 blocks. Pretty cool huh?

BitcoinEXPres574: Ok you guys wanna know how to fix GME?
BitcoinEXPres574: @mullick: All time warps require a coin with less than 2 minute block times, anything longer it's almost impossible.

BitcoinEXPres574: 2.5 minutes is on the extreme edge, I would move target time to 3 minutes.

BitcoinEXPres574: Solution for GME to live: rollback to 63380, 3 minute target times and set retarget for every 25 blocks. Just a suggestion. Nothing more.

BitcoinEXPres574: any "fast coin" less than 2.5 min block time is exploitable in multiple ways.

BitcoinEXPres574: @ mullick: Tell harbinger if he will fix his coin and cease with his BS, I'll consider not killing it. he's got four days.

 

The attacker is obviously not doing much as the block count wasn't increasing since the checkpoint update a couple of days ago until a couple of us started mining, so firstly I don't see a chain with an extra 1,000blocks, and secondly I don't see a chain that is locked down at 63,381

[Miner-TE]

Alright, enough already people!

Live and learn...then shut the fuck up and mine the coin you want to support.  I don't know about the rest of you, but this isn't a hobby for me...I actually need this shit right now to get back on the exchange.

This is very easy to understand.

1. The coin is currently being attacked.
2. We can make the changes to the code that the attacker has suggested, or continue on and let the attack persist.
Or
3. Ignore every word from the attacker and continue to think that we are progressing on the correct chain.

Words from the attacker:

Code:

BitcoinEXPres574: @Stouse49: Because I have one locked down in a time warp at 63381 and the other is advancing. When you guys mine about a 1000 blocks, I will drop about 400 mhs on the time warped chain and pass you, becoming the longer chain and invalidating everything behind me for a 1000 blocks. Pretty cool huh?

BitcoinEXPres574: Ok you guys wanna know how to fix GME?
BitcoinEXPres574: @mullick: All time warps require a coin with less than 2 minute block times, anything longer it's almost impossible.

BitcoinEXPres574: 2.5 minutes is on the extreme edge, I would move target time to 3 minutes.

BitcoinEXPres574: Solution for GME to live: rollback to 63380, 3 minute target times and set retarget for every 25 blocks. Just a suggestion. Nothing more.

BitcoinEXPres574: any "fast coin" less than 2.5 min block time is exploitable in multiple ways.

BitcoinEXPres574: @ mullick: Tell harbinger if he will fix his coin and cease with his BS, I'll consider not killing it. he's got four days.

 

The attacker is obviously not doing much as the block count wasn't increasing since the checkpoint update a couple of days ago until a couple of us started mining, so firstly I don't see a chain with an extra 1,000blocks, and secondly I don't see a chain that is locked down at 63,381

It is possible that the "Attacking" chain is isolated on a private network and hashing away.  If/When it is longer than the "Legit" blockchain it can be put online and invalidate any of our work.

You may not be able to see the "attacking" chain now but it might exist.

The only real defense against this would be to have more hashpower on the "legit" chain than any attacker would have. 

[erk]

It is possible that the "Attacking" chain is isolated on a private network and hashing away.  If/When it is longer than the "Legit" blockchain it can be put online and invalidate any of our work.

You may not be able to see the "attacking" chain now but it might exist.

The only real defense against this would be to have more hashpower on the "legit" chain than any attacker would have.  

Or keep a record of the valid block id's and reverse the attack with a checkpoint if it happens.


Meanwhile some Overclockers Australia (OCAU) members have chucked 30MH/s of gear onto mining GME for a little while to help the blocks tick over a bit quicker to the next diff lowering, just in case you are wondering why the sudden block rate pickup.


/UPDATE the difficulty just changed at block a little while ago from  Difficulty: 3.078 down to  0.769 which should help reach the 64,000 target a bit quicker.

[ahmed_bodi]

However if you disable the irc and addnode features and only connect to specific nodes im pretty sure you could ensure you would be on 1 specific chain, which is currently our setup

[elend]

According to the blockchain we are on block 63382 

You can thank a couple of us from the Crypsty chat box that decided to start mining GME about 7 hours ago! Nobody was mining it that was why it was stuck on block 63381

That's so wrong its laughable.


~BCX~

You on the wrong chain now BE? Waste hash much? 

to prevent this, simply use a pool

[erk]

The GME diff just went down again, at block 63456 now Difficulty: 0.192

Someone is trying to fork the chain at block 63484 with a fast block injection attack.

This is where selecting peers carefully comes into play.

[elend]

something is going on ...

the actual difficulty is 0.00024414

[Oldminer]

So what should the current block be?

This is the chain I'm on


{
"blocks" : 68026,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 708553,
"pooledtx" : 0,
"testnet" : false
}

[usahero]

After block 64k, difficulty dropped and no increase of difficulty since then. Looks like there is some bug in the new version.

[erk]

After block 64k, difficulty dropped and no increase of difficulty since then. Looks like there is some bug in the new version.

No as I pointed out there was a fast block injection well before block 64k, I assume an attack as there was no payout address on the mined blocks. You can see after block 64k that most of the blocks were still paying out 1,000 coins meaning is was an old or hacked client.

I would say that block 63485 onward was a forked chain and we need another checkpoint release if it doesn't correct itself. I certainly wouldn't be doing any transactions.