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.
Topic: [ANN] GameCoin (GME) - Current version = v0.8.4.2 - page 26. (Read 71774 times)
Next Network Block 63385 (Current: 63384)
Last Block Found 63384
Last Block Found 63384
According to the blockchain we are on block 63382 
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.
This is really a bad luck streak or something else is preventing the blockchain from advancing.
A difficulty calculator will merely give you an average, it still comes down to luck. One specific block could take you much less or much more than the average time.
63,381 is the current block, until a couple of days ago the majority of the network was mining at ahmed's pool (http://gme.crypto-expert.com/) but due to my underestimation of reaching the previous hard fork target of 62,250, ahmed updating his daemon after us reaching it and the hard fork being moved to block 64,000. ahmed's pool credited users with blocks that are now orphaned so as such he's had to run a full audit of payments and his pool has been out of service for a couple of days.
I believe he is now open for mining but it will still be some time before the full audit is complete and he can start crediting payments.
ortchi's pool (http://coin-base.net/gamecoin/) should also be updated with the latest version. I've not heard anything from tyrion70 yet but his pool should also be fine to mine on until we get to block 64,000 as his block explorer agrees that 63,381 is the current block.
63,381 is the current block, until a couple of days ago the majority of the network was mining at ahmed's pool (http://gme.crypto-expert.com/) but due to my underestimation of reaching the previous hard fork target of 62,250, ahmed updating his daemon after us reaching it and the hard fork being moved to block 64,000. ahmed's pool credited users with blocks that are now orphaned so as such he's had to run a full audit of payments and his pool has been out of service for a couple of days.
I believe he is now open for mining but it will still be some time before the full audit is complete and he can start crediting payments.
ortchi's pool (http://coin-base.net/gamecoin/) should also be updated with the latest version. I've not heard anything from tyrion70 yet but his pool should also be fine to mine on until we get to block 64,000 as his block explorer agrees that 63,381 is the current block.
From what I gather, 63381 is the correct current block. It's not moving cuz no one's mining it I think. You want it to move and succeed, then mine it consistently.
I punched the difficulty into a calculator, and a single GPU should have found a block in a couple of hours, it's been days! I am certainly mining it.It's only 3.078 difficulty, unless that figure is a lie.
From what I gather, 63381 is the correct current block. It's not moving cuz no one's mining it I think. You want it to move and succeed, then mine it consistently.
to overcome the actual problems,
wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
\wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
All you need is an addnode with the correct IP address in the gamecoin.conf file but so far nobody had provided one. All my clients are on the stuck chain and they are fresh installs on machines that have never run a gamecoin client before.
sure, but, as you said, nobody did provide one until now
and even if some provide their IPs:
1. you can not be sure to be on the strongest tread of the blockchain
2. IPs will change on a regular basis for the average miner sitting behing a dynamic IP-adress
3. its simply the easiest way to use one big pool, isn't it ?
to overcome the actual problems,
wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
\wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
All you need is an addnode with the correct IP address in the gamecoin.conf file but so far nobody had provided one. All my clients are on the stuck chain and they are fresh installs on machines that have never run a gamecoin client before.
sure, but, as you said, nobody did provide one until now
and even if some provide their IPs:
1. you can not be sure to be on the strongest tread of the blockchain
2. IPs will change on a regular basis for the average miner sitting behing a dynamic IP-adress
3. its simply the easiest way to use one big pool, isn't it ?
Does mining still work if the client is out of sync?
to overcome the actual problems,
wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
\wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
All you need is an addnode with the correct IP address in the gamecoin.conf file but so far nobody had provided one. All my clients are on the stuck chain and they are fresh installs on machines that have never run a gamecoin client before.
to overcome the actual problems,
wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
wouldn't it be usefull if all miners would mine on one pool togehter
making the blockchain created from this pool as strong that it becomes the main blockchain
What the fork is going on here guys?
I've downloaded the whole blockchain again with the latest version and my wallet says its still out of sync?
I've downloaded the whole blockchain again with the latest version and my wallet says its still out of sync?
There are two forks, one locked down at 63381 and the other advancing.
~BCX~
Was there any particular reason you decided to fork it?
1 minute block times is a huge mistake.
With re-targeting every other block it highly increases the likelihood of forks especially if a lot of hash rate is dropped at once.
You're effectively optimizing it for attacks.
~BCX~
probably true
1 minute block times is a huge mistake.
With re-targeting every other block it highly increases the likelihood of forks especially if a lot of hash rate is dropped at once.
You're effectively optimizing it for attacks.
~BCX~
probably true
Is there a fork?
Don't know, there is something wrong, the block count is not rising.
Even with my modest mining power, at only 3.078 difficulty I should have found a GME block in a few hours, and I don't believe for a moment I am the only one mining.
Is there a fork?
I just downloaded the source and compiled it on a linux box in the past half hour, and also installed a binary on a Mac. Both are stuck at block 63,381 this seems to indicate the default node are on the wrong fork.
Can we have the IP's of some nodes which are on the correct fork please?
Can we have the IP's of some nodes which are on the correct fork please?
From what i got from harbinger the chain stuck at 63381 is the correct chain. Could have changed since this morning though
The last checkpoint was:
( 63380, uint256("0xb442f0d8bf9cfa9fd1bc102af28c2f6e3aae2099f1417e0358f875f70788f271"))
I just downloaded the source and compiled it on a linux box in the past half hour, and also installed a binary on a Mac. Both are stuck at block 63,381 this seems to indicate the default node are on the wrong fork.
Can we have the IP's of some nodes which are on the correct fork please?
Can we have the IP's of some nodes which are on the correct fork please?
From what i got from harbinger the chain stuck at 63381 is the correct chain. Could have changed since this morning though
I just downloaded the source and compiled it on a linux box in the past half hour, and also installed a binary on a Mac. Both are stuck at block 63,381 this seems to indicate the default node are on the wrong fork.
Can we have the IP's of some nodes which are on the correct fork please?
Can we have the IP's of some nodes which are on the correct fork please?
Jump to: