[GPUC] GPU Coin | Mandatory Wallet Update

[miaC]

getblockcount is 68093.
is that correct?

[waldistons]

Wallet seems OK. My wallet version is v0.8.7.2-g88e2a2e-beta and current block is 68104

Maybe check transaction id from pools in blockchain explorer.

[miaC]

thank you waldistons!
I checked a few transactions of these and it show's not yet redeemed. my adress is GSwVxqR1Pqp1DWPiFujk8sNFnAmupZeecC
you can check here http://explorer3.sancrypto.info/t/6JAEtywPGy
what does this mean?

[waldistons]

I'm not sure what that means, but if You check Your address in explorer here http://explorer3.sancrypto.info/address/GSwVxqR1Pqp1DWPiFujk8sNFnAmupZeecC

then you will see that at block 67233 at 2014-04-24 19:51:23 time, 8458.773762 coins have been sent to Your wallet address, and address balance after that transaction is 865341.36733982 GPUC.

[miaC]

yes you're right but these pictures speak the truth. My balance is 142353.316232 GPUC and not 865341.36733982 as it should be.

https://s3-eu-west-1.amazonaws.com/affingo.123.info/poze+gpu/Capture.PNG

https://s3-eu-west-1.amazonaws.com/affingo.123.info/poze+gpu/Capture2.PNG

I run the command rescan for the wallet and the amount didn't changed.
I don't know what shoud  I do anymore...

[Lanc]

Can someone tell us what block is good now?

As far as i know there is 2 forks now. Hashfever have been 20+ blocks behind my wallet and other pools.

On the other side I send 480k GPUC to poloniex and they never receive it - but I check blockexplorer and they should receive it. So there is something fucked up now.

[vesperwillow]

Multiple forks could be the case, especially with the low nethash. I warned about this a week or 2 ago.

[kahir]

Poloniex Exchange @Poloniex
GPUC frozen while some issues with the network are sorted out.

[waltsmith]

Well, this is a very troubling development.

waltsmith

[micryon]

Multiple forks could be the case, especially with the low nethash. I warned about this a week or 2 ago.

It's not the low nethash rate, it's because we hard forked at 65535.. those who did not update are on a completely different network/different fork.

[micryon]

hello there.

i am running gpucoin p2pool node at http://p2pool.kosmoplovci.org:9404 and noticed a problem with network since yesterday evening which i was able to fix with small change in gpucoin network config in p2pool/bitcoin/networks.py file. in short, p2pool network seem to have 2 blockchains running in paralel on different p2pool nodes, one that is still presuming block rewards are 20000 and another which adopted block halving and is looking like the proper chain to me.

You cannot use that as the fix.. as that was not the only change to the latest code.  The original reason for hard fork was to fix the KGW timewarp vulnerability.  The problem is the official blockexplorer, and some p2p pools have not updated to the actual tot github code.. and causing a second fork of the chain. 

Reverting the code change will only make the situation worse, as most users have updated to the "real" blockchain, however not all pools and service tools have made the upgrade.  Anyways the best thing to do is to be on the latest github code without any changes.. and hope that the alternate forked nodes all gets updated.

But surely some people will lose their mined coins if they are on a pool that did not update.

[richiela]

What is the proper blockheight suppose to be?  Is the blockexplorer to be trusted?  I've resynced the blockchain multiple times and end up on a different blockchain than the blockexplorer.

We are diabling GPUC markets/currencies at bittrex as well until this is sorted out.

Thanks,
Richie

[micryon]

What is the proper blockheight suppose to be?  Is the blockexplorer to be trusted?  I've resynced the blockchain multiple times and end up on a different blockchain than the blockexplorer.

We are diabling GPUC markets/currencies at bittrex as well until this is sorted out.

Thanks,
Richie

Current "official" blockexplorer CANNOT be trusted.  It is on the wrong chain.

If you updated github in the last 2 weeks with mandatory wallet update, then you are on the right chain.

The majority of the hashpower IS on the right fork.  

RIGHT fork (gpucoind version: v0.8.7.2):

{
    "blocks" : 68780,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 0.35755985,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 28818280,
    "pooledtx" : 3,
    "testnet" : false
}


WRONG fork:

{
"blocks" : 68709,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.15970902,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 13147052,
"pooledtx" : 0,
"testnet" : false
}

[richiela]

What is the proper blockheight suppose to be?  Is the blockexplorer to be trusted?  I've resynced the blockchain multiple times and end up on a different blockchain than the blockexplorer.

We are diabling GPUC markets/currencies at bittrex as well until this is sorted out.

Thanks,
Richie

Current "official" blockexplorer CANNOT be trusted.  It is on the wrong chain.

If you updated github in the last 2 weeks with mandatory wallet update, then you are on the right chain.

The majority of the hashpower IS on the right fork.  

RIGHT fork (gpucoind version: v0.8.7.2):

{
    "blocks" : 68780,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 0.35755985,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 28818280,
    "pooledtx" : 3,
    "testnet" : false
}


WRONG fork:

{
"blocks" : 68709,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.15970902,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 13147052,
"pooledtx" : 0,
"testnet" : false
}

Thank you so much for the quick clarification!  Bittrex.com looks to be at the right place.. reopening back up...

   "version" : 80702,
   "protocolversion" : 70003,
   "walletversion" : 60000,
   "blocks" : 68792,

Thanks,
Richie

[micryon]

If you suspect your pool is on the wrong fork, please get off of it.  Throwing away hashing power.

Right fork is on block 68802 now.

[supernem]

Interesting concept. Too bad the marketcap is low.

[Kennar]

Well that explains my missing 2.2mil gpucoins.

 

[vesperwillow]

Multiple forks could be the case, especially with the low nethash. I warned about this a week or 2 ago.

It's not the low nethash rate, it's because we hard forked at 65535.. those who did not update are on a completely different network/different fork.

I thought you guys had planned to not hard fork?

The correct chain has even less hashpower than the last time I looked. If I'm reading that right, my network could fork the coin, much less folks with real hashpower. This project is in the dumps unfortunately.

[c275]

how is the best exchanger?

[micryon]

Multiple forks could be the case, especially with the low nethash. I warned about this a week or 2 ago.

It's not the low nethash rate, it's because we hard forked at 65535.. those who did not update are on a completely different network/different fork.

I thought you guys had planned to not hard fork?

The correct chain has even less hashpower than the last time I looked. If I'm reading that right, my network could fork the coin, much less folks with real hashpower. This project is in the dumps unfortunately.

It is ok for natural forks to occur due to hashrate.  That's just normal.

The problems are caused by hard forks.. which we did decide was a necssity due to KGW timewarp issue.  Exchanges were blacklisting coins without the security patch.. which is why the majority of coins are updating in the last month.

Anyways yeah obviously due to coin prices and lack of CEO direction hashrate has dropped to all time low...