SlientBit
|
|
April 19, 2014, 11:21:16 PM |
|
JP, I think there's a fork, really ...
Can you double check it real quick, please? with the asymmetry in hash power, it's not going to be pretty to decide witch chain is good ...[/b]
|
|
|
|
|
|
|
|
|
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
fast11
Newbie
Offline
Activity: 23
Merit: 0
|
|
April 19, 2014, 11:22:24 PM |
|
My windows wallet appears stuck at block 404. How fitting that it's 404..
Yes fork at 404....shit I have been at block 404 for quite a while now. Can't confirmed the deposit into my wallet.
|
|
|
|
slasherzx
Member
Offline
Activity: 73
Merit: 10
|
|
April 19, 2014, 11:30:32 PM |
|
Its 7:30am in my country.. I'm worried as hell what will happen in this coins..
|
|
|
|
owlhooter
|
|
April 19, 2014, 11:34:42 PM |
|
My windows wallet appears stuck at block 404. How fitting that it's 404..
Yes fork at 404....shit Just so you know, I don't think it's a fork, it looks like the same issue H2O coin had on their last launch where 32 bit clients get a rounding error and can't match the hash and nonce. Something JP will have to fix in code and recompile wallets for. There will be a fork if people are mining to a 32 bit client though, so make sure you are mining to a 64 bit build you have built yourself on linux or a pool that is using 64 bit. If you solo mine to the windows wallet any blocks you may find would be on a fork. Here is the commit that H2O coin used to fix their issue. https://github.com/h2o-coin/H2Ocoin/commit/9b5d70311ece1c3a52b8f1596aa166e3cb32e4a5#diff-7ec3c68a81efff79b6ca22ac1f1eabba
|
|
|
|
louiseth1
Legendary
Offline
Activity: 924
Merit: 1000
Bitfarms.io
|
|
April 19, 2014, 11:37:38 PM |
|
SuchPool.pw is now entirely operational.
You can come back. Everything has been restored and balances are correct. Cronjobs are running, payouts being done and blocks being found.
http://quebec.suchpool.pw
Again, we deeply apoligize for this downtime. It was totally unexpected, and the damage was really extensive, and affecting all our pools.
Measures are being put in place to ensure quick recovery if this ever happens again on such a large scale.
|
Bitfarms.io - Powering Blockchains with Sustainable Energy
|
|
|
|
Kreativekrypto
|
|
April 19, 2014, 11:39:49 PM |
|
{ "blocks" : 405, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 206.96454566, "errors" : "", "networkhashps" : 3778619710, "pooledtx" : 9, "testnet" : false }
|
|
|
|
owlhooter
|
|
April 19, 2014, 11:44:54 PM |
|
{ "blocks" : 405, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 206.96454566, "errors" : "", "networkhashps" : 3778619710, "pooledtx" : 9, "testnet" : false }
Block 405 means someone mining on a 32 bit client has created a fork..
|
|
|
|
Kreativekrypto
|
|
April 19, 2014, 11:50:35 PM |
|
{ "blocks" : 405, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 206.96454566, "errors" : "", "networkhashps" : 3778619710, "pooledtx" : 9, "testnet" : false }
Block 405 means someone mining on a 32 bit client has created a fork.. This is a grey area for me, can a single person with a 32 bit client create a fork? Or you mean a pool with a 32 bit client.
|
|
|
|
coins101
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
April 19, 2014, 11:51:27 PM |
|
I don't see a fork. You mean one like this?
|
|
|
|
owlhooter
|
|
April 19, 2014, 11:56:24 PM Last edit: April 20, 2014, 12:19:02 AM by owlhooter |
|
{ "blocks" : 405, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 206.96454566, "errors" : "", "networkhashps" : 3778619710, "pooledtx" : 9, "testnet" : false }
Block 405 means someone mining on a 32 bit client has created a fork.. This is a grey area for me, can a single person with a 32 bit client create a fork? Or you mean a pool with a 32 bit client. It could be a single person solo mining to a windows wallet. but the master chain that the pools appear to be on will be the one that prevails when the code is fixed, so unless you are solo mining to a windows wallet or a 32 bit linux wallet your coins should be safe. JP, I think this will fix the code, might want to compile it and test it as I can't compile it right now.https://github.com/owlhooter/QBC/commit/bc61b7615d2ec57c9be2d5866115edb1039a6af6#diff-7ec3c68a81efff79b6ca22ac1f1eabba
Edit: I lied, I'm trying to compile right now to test it out. First attempt didn't work, trying again.
|
|
|
|
JPGagnon (OP)
|
|
April 20, 2014, 12:22:18 AM |
|
Looking into problems right now everyone.
|
|
|
|
owlhooter
|
|
April 20, 2014, 12:26:59 AM |
|
Looking into problems right now everyone.
I think this file will fix it now https://github.com/owlhooter/QBC/src/main.cpp I had just forgot something in my first iteration. it's still compiling though to test. Compile is finished and I'm sync'd up all the way to 456 now, but the repository still has the accent on the e so you might want to recompile without that.
|
|
|
|
coins101
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
April 20, 2014, 12:32:46 AM |
|
Looking into problems right now everyone.
what is the network hash rate?
|
|
|
|
Kreativekrypto
|
|
April 20, 2014, 12:37:15 AM |
|
Looking into problems right now everyone.
what is the network hash rate? 5617 m/h
|
|
|
|
JPGagnon (OP)
|
|
April 20, 2014, 12:39:27 AM |
|
Looking into problems right now everyone.
I think this file will fix it now https://github.com/owlhooter/QBC/src/main.cpp I had just forgot something in my first iteration. it's still compiling though to test. Compile is finished and I'm sync'd up all the way to 456 now, but the repository still has the accent on the e so you might want to recompile without that. Did you compile on windows or linux? I'm getting my station ready it's a bit slow and I'll have the fixed wallet ready unless you have the windows version already which you can post while I merge your change?
|
|
|
|
JPGagnon (OP)
|
|
April 20, 2014, 12:40:32 AM |
|
Looking into problems right now everyone.
what is the network hash rate? 5617 m/h Are you getting that from the pools or your wallet?
|
|
|
|
owlhooter
|
|
April 20, 2014, 12:42:06 AM |
|
Looking into problems right now everyone.
I think this file will fix it now https://github.com/owlhooter/QBC/src/main.cpp I had just forgot something in my first iteration. it's still compiling though to test. Compile is finished and I'm sync'd up all the way to 456 now, but the repository still has the accent on the e so you might want to recompile without that. Did you compile on windows or linux? I'm getting my station ready it's a bit slow and I'll have the fixed wallet ready unless you have the windows version already which you can post while I merge your change? I compiled on windows, but it still has the accents on the e's so will probably have the config file issue you fixed earlier so while mine works it doesn't read the config file so still needs to be compiled again.
|
|
|
|
Kreativekrypto
|
|
April 20, 2014, 12:42:40 AM |
|
Pool, cause wallet is...well you know Lol.
|
|
|
|
owlhooter
|
|
April 20, 2014, 12:43:50 AM |
|
And just so you know, anyone with the windows wallet will need to delete the blocks and chainstate folder when they download the new wallet to get past the small fork.
And I have to run out for a few minutes, but I'll be back in a few.
|
|
|
|
|