Topic: [ANN] GameCoin (GME) - Current version = v0.8.4.2 - page 23. (Read 71774 times)
Locked and loaded here as well.
Updated and waiting.
New clients have been posted in the first post courtesy of shakezula and maxpower respectively.
You will need to delete everything from %Appdata%\Gamecoin (or equivalent on other OS) except wallet.dat and gamecoin.conf and then start your client. It should then proceed to download 63,999 blocks at which point it will stop.
Block 64,000 was mined over 24 hours ago and is a required checkpoint so you will be unable to mine right now. This block will be released onto the network at 23:00 (GMT) on 8th September 2013 at which point mining will be able to recommence. This is to allow as many people as possible time to update and of course ensure that the relaunch is fair with nobody having an unfair advantage with the initial lower difficulty blocks.
Currently tyrion70 has signalled that his pool and block explorer is standing by at block 63,999 and ahmed_bodi is up to date but still requires some time to make some further updates to his pool. At the moment I haven't heard back from ortchi but I am hopeful everyone will be ready to go by the time block 64,000 is made available.
You will need to delete everything from %Appdata%\Gamecoin (or equivalent on other OS) except wallet.dat and gamecoin.conf and then start your client. It should then proceed to download 63,999 blocks at which point it will stop.
Block 64,000 was mined over 24 hours ago and is a required checkpoint so you will be unable to mine right now. This block will be released onto the network at 23:00 (GMT) on 8th September 2013 at which point mining will be able to recommence. This is to allow as many people as possible time to update and of course ensure that the relaunch is fair with nobody having an unfair advantage with the initial lower difficulty blocks.
Currently tyrion70 has signalled that his pool and block explorer is standing by at block 63,999 and ahmed_bodi is up to date but still requires some time to make some further updates to his pool. At the moment I haven't heard back from ortchi but I am hopeful everyone will be ready to go by the time block 64,000 is made available.
Allright, pool at http://gme.p2pool.nl and blockexplorer (http://gme.p2pool.nl/chain/Gamecoins) are up again..
Hope the lastest changes work and fix everything.
Cheers
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block chain?
Regarding above question, I have no idea if and why it was at a different chain. It appeared to be stuck with the following messageCode:
09/07/13 19:02:04 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
09/07/13 19:02:04 ProcessMessage(ping, 0 bytes) FAILED
09/07/13 19:02:04 ProcessMessage(ping, 0 bytes) FAILED
Hope the lastest changes work and fix everything.
Cheers
Please publish an authoritative node we can use for syncing
Nothing is going to be published until extensive tests have been run to determine the next version of GameCoin will run as anticipated. The restart block will only be available on the network once the code has been pushed to GitHub, the pools are updated and new clients are in place. Nobody is going to have a head start on it. Also, don't expect those 0.00024414 blocks to last long when we are ready to go. The difficulty should be up to ~0.25 by block 64,068 after which it'll increase/decrease by a maximum of 110% every 12 blocks.
If you want to get synced to block 63,999 and you can self compile then take the current code on GitHub and add these 2 lines under the current checkpoints in src/checkpoints.cpp:
Code:
( 63999, uint256("0x09e6e091b78ef2b790aba6ea7cdc37a2cb125bc217a1fbeda52538e76141ad98"))
( 64000, uint256("0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"))
( 64000, uint256("0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"))
Compile it and then delete everything from %Appdata%\Gamecoin (or equivalent on other OS) except wallet.dat and gamecoin.conf and then sync with any peer out there. It'll get to block 63,999 and go no further, close down your client and wait for the next version. That's as prepared as you can make yourself for now.
That sucks.
Literally lost all my coins whilst sending to cryptsy when the block chain messed up.
Literally lost all my coins whilst sending to cryptsy when the block chain messed up.
No ... if the transaction was after block 64000, when the blockchain rolls back they will reappear in your wallet.
That sucks.
Literally lost all my coins whilst sending to cryptsy when the block chain messed up.
Literally lost all my coins whilst sending to cryptsy when the block chain messed up.
It's already been stated that there will be a new completely independent fork. As I've seen very little objection to a new block 64,000 being the starting point that is where we will be starting from.
Currently I am the only person with this newly mined block 64,000 and it won't be made available until the new client is ready and the pools signal that they have updated to the latest code. (When ready and tested)
If you're mining right now you're wasting your time. Any coins generated past block 63,999 will not exist.
Currently I am the only person with this newly mined block 64,000 and it won't be made available until the new client is ready and the pools signal that they have updated to the latest code. (When ready and tested)
If you're mining right now you're wasting your time. Any coins generated past block 63,999 will not exist.
Please publish an authoritative node we can use for syncing
It's already been stated that there will be a new completely independent fork. As I've seen very little objection to a new block 64,000 being the starting point that is where we will be starting from.
Currently I am the only person with this newly mined block 64,000 and it won't be made available until the new client is ready and the pools signal that they have updated to the latest code. (When ready and tested)
If you're mining right now you're wasting your time. Any coins generated past block 63,999 will not exist.
Currently I am the only person with this newly mined block 64,000 and it won't be made available until the new client is ready and the pools signal that they have updated to the latest code. (When ready and tested)
If you're mining right now you're wasting your time. Any coins generated past block 63,999 will not exist.
My pool made it to block 102177, I'm guessing they'll be orphaned. It would be great to see a fix so the pool can mine GME and I don't get the flack for mining going to waste 
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block chain?
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.
damn... Ive found like 5002 blocks
Its pointless mining this atm
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block chain?
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.
damn... Ive found like 5002 blocks
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block chain?
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.
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block chain?
Who knows, despite many requests, nobody will publish the IP of a node that's on the right chain to sync to.
So this block chain explorer (http://gme.p2pool.nl/chain/Gamecoins) is pointing to the wrong block 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?
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?
I've not examined every single block but I've only noticed 1 block which appears to go back in time by a matter of a few seconds, we're not talking hours here as would be expected if someone just dumped blocks on the network. All of the rest appear to go in sequence albeit getting generated ever faster due to the rapidly dropping difficulty.
There is an error in the code which allowed it to go to the absolute bare minimum difficulty and stay there. I have confirmed as much myself in testing. That is what has caused the massive number of blocks so yes I am going to validate the blocks up to 63,999 as this is the point that all clients agree on before going their separate ways.
There is an error in the code which allowed it to go to the absolute bare minimum difficulty and stay there. I have confirmed as much myself in testing. That is what has caused the massive number of blocks so yes I am going to validate the blocks up to 63,999 as this is the point that all clients agree on before going their separate ways.
What is the payout address that mined almost all the 500+ blocks between 63486 and 63999 in less than 20min?
It was most likely a GME address associated with ortchi's pool as I think there was a rally to mine there last night.
For what it's worth I have zero problem with invalidating everything all the way back to the last checkpoint I added to checkpoints.cpp which was 63380. It makes no difference to me as I didn't mine any of those blocks. Everyone should state which block they believe it should be rolled back to and I'll go with the majority.
The core problem is there is an error in the code and that needs to be resolved before a new client can be released and I'm still testing different settings.
I switched from ahmed's to ortichi's yesterday since I knew (at least thought) he was on the correct chain and had 1600 kh/s on it so that may have well been me finding all the blocks.
Either way, make it 64000 like you have planned and make that the starting point.
Cheers,
bluestang
PoolMiner: I'm not changing the block time at all any longer, it is staying at 2.5 minutes. Any change to the block time also needs a change to the coin supply to maintain balance. At 4 minute blocks I'd have to change the subsidy to 1600 GME and the coin will be constantly at a much higher difficulty in general.
I've not examined every single block but I've only noticed 1 block which appears to go back in time by a matter of a few seconds, we're not talking hours here as would be expected if someone just dumped blocks on the network. All of the rest appear to go in sequence albeit getting generated ever faster due to the rapidly dropping difficulty.
There is an error in the code which allowed it to go to the absolute bare minimum difficulty and stay there. I have confirmed as much myself in testing. That is what has caused the massive number of blocks so yes I am going to validate the blocks up to 63,999 as this is the point that all clients agree on before going their separate ways.
There is an error in the code which allowed it to go to the absolute bare minimum difficulty and stay there. I have confirmed as much myself in testing. That is what has caused the massive number of blocks so yes I am going to validate the blocks up to 63,999 as this is the point that all clients agree on before going their separate ways.
What is the payout address that mined almost all the 500+ blocks between 63486 and 63999 in less than 20min?
It was most likely a GME address associated with ortchi's pool as I think there was a rally to mine there last night.
For what it's worth I have zero problem with invalidating everything all the way back to the last checkpoint I added to checkpoints.cpp which was 63380. It makes no difference to me as I didn't mine any of those blocks. Everyone should state which block they believe it should be rolled back to and I'll go with the majority.
The core problem is there is an error in the code and that needs to be resolved before a new client can be released and I'm still testing different settings.
You are all wrong.
The problem started before block 63485, it started during the time warp. The coin is still under attack!!
Please take off your blinders and quit holding on to old resentments and realize that these minor fixes are creating more problems. Rollback to 63380, and remove the block time from 1 minute and change it to 4 minutes, change the confirmations to 5 instead of 6.
Read the code noob, the block time 1min doesn't kick in until block 64k it had nothing to do with the problem I pointed out.The problem started before block 63485, it started during the time warp. The coin is still under attack!!
Please take off your blinders and quit holding on to old resentments and realize that these minor fixes are creating more problems. Rollback to 63380, and remove the block time from 1 minute and change it to 4 minutes, change the confirmations to 5 instead of 6.
Code:
else if(pindexLast->nHeight >= 63999)
{
nTargetTimespan = 120; // 2 minutes
nTargetSpacing = 60; // 1 minute
nInterval = nTargetTimespan / nTargetSpacing;
{
nTargetTimespan = 120; // 2 minutes
nTargetSpacing = 60; // 1 minute
nInterval = nTargetTimespan / nTargetSpacing;
Jump to: