Topic: [ANN] New Crypto Currency - GameCoin (GME) - page 7. (Read 54317 times)
Wednesday Thursday Friday.
WTS 36K GME PM with offert. Accept LTC / BTC / PPC
Placing this in a thread where it just turned out that whatever you got may get lost any time might not be the strategically wisest move :-)
WTS 36K GME PM with offert. Accept LTC / BTC / PPC
hahahaha what a load of shit, i have ten thousand coins, i dont kno if its blk1, 2 3 or the new fork, either way tz a "forking" waste of my time, the only value of this coin is trading it for lols with the trollbox gang. Shit, shitcoins everywhere
has any1 tried putting it's wallet.dat in feathercoin folder? since we were blockchain skipping, it might just hook you up some feathers, hehehe, that would hold the record for these scam coins, all of sudden someone will have 100k "new" feathers
has any1 tried putting it's wallet.dat in feathercoin folder? since we were blockchain skipping, it might just hook you up some feathers, hehehe, that would hold the record for these scam coins, all of sudden someone will have 100k "new" feathers
Looks like the originator disappeared...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
As the genesis block is the same as from [lite|feather]coin all it takes is for someone to drop blk0001.dat, blkindex.dat and the database folder from their %Appdata%\[lite|feather]coin folder and as it's a longer chain the peers are more likely to believe it is genuine unless there are specific checkpoints that it can refer to to know that it is not the correct blockchain.
I've currently compiled a daemon with the changes I posted above (I can't compile the wallet on Windows for some reason) and am running that as a test. There has not been a new block for about 25 minutes now so I guess it's essentially dead.
now... i am wondering... is it an intentional attempt that try to sabotage feathercoin blockchain?
This is what happens when you use the same genesis block as another coin.
Let this garbage die.
Let this garbage die.
Remove the nodes from your config file, delete your blockchain and let it re-download.
After some syncing time my coins are showing up again. Not sure if it's an actual fix, or just false hope.
After some syncing time my coins are showing up again. Not sure if it's an actual fix, or just false hope.
worked for me too, thanks
Remove the nodes from your config file, delete your blockchain and let it re-download.
After some syncing time my coins are showing up again. Not sure if it's an actual fix, or just false hope.
After some syncing time my coins are showing up again. Not sure if it's an actual fix, or just false hope.
worked for me too, thanks
I hope no-one actually spent $$ buying this altcoin ;-)
I managed to dump 25 blocks that I mined overnight for 5LTC
Declare that one dead and move on ...
Yeh, relax, tomorrow again a couple of new ***coins wil be annouced.
Declare that one dead and move on ...
I hope no-one actually spent $$ buying this altcoin ;-)
Someone is still mining the original only 51% attacked once chain. It just went up to 19270. 
My gamecoind also still sticks to it, though it reports lots of "orphan blocks" - right now at 19274.
Yup, I get the same. There were 4 blocks found right after I posted it seems. The only way it can really be saved is for enough people to use a wallet/daemon compiled with the changes above. Otherwise it's as good as dead.
Someone is still mining the original only 51% attacked once chain. It just went up to 19270.
My gamecoind also still sticks to it, though it reports lots of "orphan blocks" - right now at 19274.
Code:
C:\gamecoin-master\src>gamecoind getinfo
{
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 31000.00000000,
"blocks" : 19270,
"connections" : 8,
"proxy" : "",
"difficulty" : 1.00000000,
"testnet" : false,
"keypoololdest" : 1368365183,
"keypoolsize" : 58,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"unlocked_until" : 0,
"errors" : ""
}
Someone is still mining the
Looks like the originator disappeared...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
As the genesis block is the same as from [lite|feather]coin all it takes is for someone to drop blk0001.dat, blkindex.dat and the database folder from their %Appdata%\[lite|feather]coin folder and as it's a longer chain the peers are more likely to believe it is genuine unless there are specific checkpoints that it can refer to to know that it is not the correct blockchain.
I've currently compiled a daemon with the changes I posted above (I can't compile the wallet on Windows for some reason) and am running that as a test. There has not been a new block for about 25 minutes now so I guess it's essentially dead.
Looks like the originator disappeared...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
I already noticed yesterday that it seems like the github fork of the sources was only a few hours before the release....
I still don't get how the gamecoind/gamecoin-qt gets into contact with the feathcoin(or whatever) blockchain to be in this situation in the first place - since they use different ports.
Or somebody deliberately connected a feathercoin(or whatever) node to the gamecoin node network?
And why does it say something about 3xxxxx blocks? That's litecoin, not feathercoin...
51% TWICE
still think you can make profits ?
still think you can make profits ?
Code:
$ gamecoind getmininginfo
{
"blocks" : 352269,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 596.88735373,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 18524321047,
"pooledtx" : 193,
"testnet" : false
}
Code:
$ gamecoind getinfo
{
"version" : 60300,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 352269,
"connections" : 125,
"proxy" : "",
"difficulty" : 596.88735373,
"testnet" : false,
"keypoololdest" : 1368341225,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
Looks like Litecoin chain.... 51% --> GME is dead
The original blockchain does seem to be winning the fight but if anyone can compile a new gamecoin-qt.exe, an addition of some checkpoints to src/checkpoints.cpp should help.
Current:
Changed to add extra block hashes:
Source of above additions:
Current:
Code:
static MapCheckpoints mapCheckpoints =
boost::assign::map_list_of
( 0, uint256("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2"))
( 15000, uint256("0xdb0386f2b3c77be8406e5f6e0b0f17d116a20e44ab312d81c78cabdb0a25fdfa"))
;
Changed to add extra block hashes:
Code:
static MapCheckpoints mapCheckpoints =
boost::assign::map_list_of
( 0, uint256("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2"))
( 15000, uint256("0xdb0386f2b3c77be8406e5f6e0b0f17d116a20e44ab312d81c78cabdb0a25fdfa"))
( 15500, uint256("0x5d056501ff02bf9220fb92f8ef6c5b18f4427216bf0c3e9c0de0ea26a78d6b1c"))
( 16000, uint256("0x1238760df809ed04c7c835f2ccc2230f1a12060c4af4ccf4a5076c43b3ec00f6"))
( 16500, uint256("0xc1aa0164d8262d606a5345e0b329af0833b1931c066e6ae0cd514d7943fc6e49"))
( 17000, uint256("0xa9b9ce5ab12059921ee9fab0e2ede9947181a924e36de5bbb9701e31408c92e3"))
( 17500, uint256("0x7ef8701746335ee4ab4c69173aacba0cf17ddce96cdcc8557962e9bc499e76f7"))
( 18000, uint256("0x500c4a1edf9ca19a3d7abff3338d45a7e76d28b324dbb212dc5d4dee1cb07cc9"))
( 18500, uint256("0x181d8fb8bb94ca4f1147c9d8b3d7ea56d5bcc4145f853e6a4333eb7eb791e812"))
( 19000, uint256("0x285c6caac0624e68279cbd60695dccc0f43a69b1be70776dd694befdcc21cac7"))
( 19100, uint256("0x47373775b7db1213a9027a741b5225e5b96ef1c2932ba04e9ff178b951838ed1"))
( 19200, uint256("0xaebd1cb984fe55090254fbd766275d007863f02a4327a0d655f881e7b8fe5bdd"))
( 19264, uint256("0xa8ea7f271fd5c0430df91c9e62604932624bbac96eb8fc015faf284f6a712c4b"))
;
Source of above additions:
Code:
17:38:15

getblockhash 15500
17:38:15

5d056501ff02bf9220fb92f8ef6c5b18f4427216bf0c3e9c0de0ea26a78d6b1c
17:38:39

getblockhash 16000
17:38:39

1238760df809ed04c7c835f2ccc2230f1a12060c4af4ccf4a5076c43b3ec00f6
17:39:55

getblockhash 16500
17:39:55

c1aa0164d8262d606a5345e0b329af0833b1931c066e6ae0cd514d7943fc6e49
17:40:13

getblockhash 17000
17:40:13

a9b9ce5ab12059921ee9fab0e2ede9947181a924e36de5bbb9701e31408c92e3
17:40:29

getblockhash 17500
17:40:29

7ef8701746335ee4ab4c69173aacba0cf17ddce96cdcc8557962e9bc499e76f7
17:40:55

getblockhash 18000
17:40:55

500c4a1edf9ca19a3d7abff3338d45a7e76d28b324dbb212dc5d4dee1cb07cc9
17:41:16

getblockhash 18500
17:41:16

181d8fb8bb94ca4f1147c9d8b3d7ea56d5bcc4145f853e6a4333eb7eb791e812
17:42:03

getblockhash 19000
17:42:03

285c6caac0624e68279cbd60695dccc0f43a69b1be70776dd694befdcc21cac7
17:42:56

getblockhash 19100
17:42:56

47373775b7db1213a9027a741b5225e5b96ef1c2932ba04e9ff178b951838ed1
17:43:13

getblockhash 19200
17:43:13

aebd1cb984fe55090254fbd766275d007863f02a4327a0d655f881e7b8fe5bdd
17:52:57

getblockhash 19264
17:52:57

a8ea7f271fd5c0430df91c9e62604932624bbac96eb8fc015faf284f6a712c4b
Jump to: