|
Lucky me, Just got one.
[2013-09-08 16:40:32] Accepted 00009a1e Diff 109K/19833 BLOCK! GPU 0 pool 1
|
|
|
|
This party is late....  |
|
|
|
where is the block?  |
|
|
|
Exactly 12blocks will be mined at the starting diff.
Seriously, you really think a 110% increase every 12 blocks is going to slow down 400+ mhs? ~BCX~ No. Not for long ... I'm still hopeful to get a block. Maybe two... Honestly I don't know if I will but DAYUM these guys are pushing for a fight they cannot win, period. ~BCX~ I really don't want to be a part of this pissing contest but have to admit I'm enjoying the show. A battle played out in the blockchain ... Attack/defense .... It's really interesting. Anyone taking notes ... need to be at least a sub plot in a movie.... I would like to see this coin back on an exchange. So just don't kill it. |
|
|
|
Exactly 12blocks will be mined at the starting diff.
Seriously, you really think a 110% increase every 12 blocks is going to slow down 400+ mhs? ~BCX~ No. Not for long ... I'm still hopeful to get a block. Maybe two... |
|
|
|
My bad, I thought it was white.  Either way, I was unable to acquire one. |
|
|
|
|
Does anyone have White?
Of the original colors, that is what I'm missing.
|
|
|
|
Who knows, despite many requests, nobody will publish the IP of a node that's on the right chain to sync to. All my peers (only 5) appear to be on the 102K blockchain. I'd guess to be on the other chain would require disabling DNS/IRC and only connecting to a "Good" known node that is unknown to us. We will need to wait for the new client and probably download the blockchain again .... Any chain/mining we doing now is going to be wiped with the new client and checkpoint. We might as well be on the testnet ... were not doing any good on this chain. |
|
|
|
64,000 is OK with me.... Just want to get back to mining this coin. Looks like I'll loose a small payout from coin-base.net pool but no worries. Thanks for the hard work getting us through this. Any ETA on a re-launch? |
|
|
|
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: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. |
|
|
|
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.  |
|
|
|
|
I've also been mining the 63381 blockchain all this time with the latest client and still haven't found a block.
This is really a bad luck streak or something else is preventing the blockchain from advancing.
|
|
|
|
|
I have to agree, 1 min block times does not sound like a good idea.
Every coin has growing pains. Changing the fundamental base of the coin without really good reasons is a mistake IMO. If difficulty is high, we just need to wait it out. If users believe in this coin, they can support it by mining it. If you want the your transactions to confirm, mine them.
That being said .... is anyone mining this anymore? I'm feeling alone out here but that is how it is mining solo.
difficulty : 3.07812949 does not sound so hard. No block for ~16 hrs on the network is a problem.
|
|
|
|
The client seems stuck at block 63381...
Same here ....  |
|
|
|
Block 62400 has passed.  |
|
|
|
|
Yippie, found +1 block for the pool.
|
|
|
|
Wow, It's been 3 days of mining/supporting this coin and not a single block. Rotten luck on my part. Donations welcome GXsSHYzdW5iBJ5xcGBarHyPP3X7dKXJZXe Time to switch to the pool.... Anyone care to throw some hash to gamecoin? Please do ... and help get us over the hump and out of this high diff. |
|
|
|
|
Show Posts
