Pages:
Author

Topic: [GPUC] GPU Coin | Mandatory Wallet Update - page 21. (Read 421398 times)

hero member
Activity: 937
Merit: 1000
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
full member
Activity: 154
Merit: 100
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
}

hero member
Activity: 937
Merit: 1000
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
full member
Activity: 154
Merit: 100
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.

full member
Activity: 154
Merit: 100
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.



full member
Activity: 196
Merit: 100
Well, this is a very troubling development.

waltsmith
legendary
Activity: 1050
Merit: 1000
Poloniex Exchange @Poloniex
GPUC frozen while some issues with the network are sorted out.
hero member
Activity: 616
Merit: 500
Multiple forks could be the case, especially with the low nethash. I warned about this a week or 2 ago.

newbie
Activity: 33
Merit: 0
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.
newbie
Activity: 9
Merit: 0
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...
sr. member
Activity: 294
Merit: 250
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.
newbie
Activity: 9
Merit: 0
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?
sr. member
Activity: 294
Merit: 250
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.
newbie
Activity: 9
Merit: 0
getblockcount is 68093.
is that correct?
newbie
Activity: 9
Merit: 0
gpu.suprnova.cc and  gpu.locl.ca
I've mined on both and it shows that they confirmed the payments to my wallet adresses, but my wallet didn;t received that amount.

I've updated to the new version v08.7.2 i;ve also added config file on appdata and still i'm not on the right way.
sr. member
Activity: 294
Merit: 250
about what pool are You talking about?

EDIT: always check last block time in wallet! (help/debug) I've experienced that wallet says it's synced and clients connected, but last block is couple hours old. This is a bug on some windows wallets AFAIK.
newbie
Activity: 9
Merit: 0
Hi!
I have a problem. My wallet doesn't show the coins the pool send me.

Acctualy it shows it is synced, but I don't have  in the wallet the total amount of coins which are listed on transactions pool section.
What would you suggest?
newbie
Activity: 7
Merit: 0
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.

'bad' chain has a slightly different number of blocks, so it may not be obvious on first looks. fact that 'official' blockexplorer at http://explorer3.sancrypto.info/chain/GPUCoin shows old chain only complicates situation, as it looks like everything is fine when in fact it isnt. so, some p2pool nodes solve blocks from chain one, other nodes solve blocks from chain two, they get accepted/orphaned depending on the version of wallet running on particular node, and blocks found by BOTH chains are displayed on every p2pool node stats page, adding even more to confusion.

it looks like this is happening from yesterday evening when block halving took place. before that everything was working normally on my p2pool, i was getting shares with almost no orphans and regular payouts, and then suddenly large amounts of orhpan blocks started appearing and payments both in my server gpucoind wallet and local gpucoin-qt wallet stopped.

of course, first i checked the wallets, check code updates, restart wallets, even rebuilding blockchain from scratch, wallet always connects to the same blockchain - and not the one visible on mentioned blockexplorer (any other available?). (in fact, if that was the proper chain, i would actually have more GPUC that i actually do in my wallet now)

since my both wallets are compiled from latest sources at github and were working quite fine for past days and weeks, and since they are both on same blockchain (reporting same blocknumber and working cross-send-receive) i assumed this should be the proper blockchain so i proceed to search for a problem in p2pool code.

to cut story short, it appears p2pool code autodetects block reward and display it properly on stats page, however when it comes to accepting share and create block, it orhpans, and payouts are also completelly stopped. to try to fix this, i changed the SUBSIDY_FUNC value in p2pool/bitcoin/networks.py from 20000 to 10000 (to reflect current block reward) and it worked! accepted shares are again generating blocks as it should and p2pool pays out rewards in my wallet as it was doing before all this. the pool still gets lots of orhpan shares, but i think that is because of 2 chains running in parallel and orhpaning each other.

now, so if someone knows better what is going on and how to properly/permantly fix this kind of issues please do. i do hope this analysis may help find the best solution.

here are versions of software i use:
gpucoin-qt 0.8.7.2-g88e2a2e-beta (compiled on ubuntu 12.04 32bit)
gpucoind version 80702 protocolversion 70003 (compiled on debian 7 64bit)
https://github.com/micryon/GPUcoin

p2pool-gpuc
https://github.com/TheoRettisch/p2pool-gpuc

thank you
k
hero member
Activity: 616
Merit: 500
I'm not sure if he works at the local nuke station, but he claims to have been a nuke in the Navy. I'd bet he was kicked out with how things have been going. They don't usually let nukes retire easily unless they don't like them.
sr. member
Activity: 602
Merit: 295
Hail Eris!
Is Jaymes still working as a nuclear reactor operator?

I think his employers should know about his legal scam operation, as they might want to reconsider letting someone like that operate such vital equipment.

Pages:
Jump to: