|
Actually, I just installed the old version on another PC and it got to 786, it's on the wrong fork, someone has forked the coin with the version of the windows wallet that is incorrect and has been solo mining to it all night it would appear. The new version of the wallet will work but you have to delete everything in the Quebecoin folder inside of %AppData% other than the wallet.dat file.
|
|
|
|
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??
I haven't had any problems with the new wallet since it was released last night. Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet? yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man Could you post your debug.log file on pastebin so we can see where it's failing possibly? 2014-04-20 19:29:30 received block 00000000015d57fd4fae7b56b6d771e5c9c6b38facde6cc7fb460711f78ac6c6 2014-04-20 19:29:30 ProcessBlock: ORPHAN BLOCK, prev=0000000002470cae78f1dfdce05cdc71347519686d7bf8f834c8f725751e7d31 2014-04-20 19:29:31 received block 00000000010a5becc2de4e7af1f48209383924342ed7bbbc822a63df311dc72a 2014-04-20 19:29:31 ERROR: AcceptBlock() : incorrect proof of work 2014-04-20 19:29:31 ERROR: ProcessBlock() : AcceptBlock FAILED 2014-04-20 19:29:31 Misbehaving: 54.86.39.92:44093 (0 -> 100) DISCONNECTING 2014-04-20 19:29:31 disconnecting node 54.86.39.92:44093 2014-04-20 19:30:08 stored orphan tx b84f54a6a1683784660e42cc2cd51d4c60c0c17475c4a01527df81027f57ad2a (mapsz 2) 2014-04-20 19:30:09 stored orphan tx acbfb0365b864e2e2dea807e2c608a567cc48d5059f78bde2b84fa806cb5e1f1 (mapsz 3) 2014-04-20 19:30:10 stored orphan tx 14820c374f913222bd8f0b6a82e10baba8742115a1383a3dc4ada5127053709f (mapsz 4) 2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent 2014-04-20 19:30:12 a1d5cc24e3dd084c5297d273497af1b136ddf7a16704104495263344ad40a2ce from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool 2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent 2014-04-20 19:30:12 fc5823fd849dadb5b8ab839bfa06bc58c60f24299864d0da20d59d31ca07b768 from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool There is probably a part in there that says "INVALID PROOF OF WORK" will need about 10 lines before and after that. |
|
|
|
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??
I haven't had any problems with the new wallet since it was released last night. Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet? yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man Could you post your debug.log file on pastebin so we can see where it's failing possibly? |
|
|
|
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??
I haven't had any problems with the new wallet since it was released last night. Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet? |
|
|
|
Let's go guys, anyone going to take the lead on this? Oh - I forgot, 0.05 BTC to the first person to post a compiled MAC Quebecoin-QT client from the latest Github source at www.github.com/jpgagnon/qbc
Be sure to use the latest OPENSSL 1.0.1g
I'm currently working on it, but it will be my first Mac OSX wallet, so we'll see how successful I am, I wouldn't want to stop anyone else from trying in the meantime though. |
|
|
|
We've found a couple blocks overnight, come join us at http://qbc.cryptoadhd.comStill one of the smaller pools around but we are G ROWING! I didn't realize you are using half of your 1% fee to donate to charity, coming to your pool shortly.  We are also doing 50% of any donations we receive to charity as well, we still have to find the charity and it will be one in Quebec since we like to keep our charity donations close to the focus of the coin when possible. So anyone with charity recommendations feel free to chime in. |
|
|
|
We've found a couple blocks overnight, come join us at http://qbc.cryptoadhd.comStill one of the smaller pools around but we are G ROWING! |
|
|
|
JPGagnon
JPGagnon
Do not remove our pool of links please, Many of the miners mining in our pool, you remove our pool of links are not good for all of Anybody
If you would read through the thread you would see that your pool was removed for the good of the coin, you had over 90% of the total network hashrate yesterday and the hashrate needed to be spread around rather than focused on one pool. And as your pool still has > 50% of the network hash I doubt he'll add it back to the list right now. If and when miners spread out you'll probably be added back. |
|
|
|
Very nice and I'm sure you guys will recover from this nicely, I would like to think I will be able to perform as well as you guys have during the issues you had today. And here's to hoping you won't have to utilize those additional backup measures or go through this again in the future, or any of us for that matter.
Thanks a lot owl. We try to do our best, it is just sad some users just don't understand. No coins are "lost" because our wallets are on separate servers and weren't affected at all! To be honest, I never expected we would pull this off and save the most part of the last 36 hours of data. All the credit goes to CoinFinder who was able to recover most of the corrupted tables! It's definitely made me rethink backup strategy and implement some additional measures as well. |
|
|
|
STATEMENT FROM SUCHPOOL.PW ABOUT DATABASES ISSUES ON 2014-04-19Dear users, Today we have had a quite noticeable interruption in our services. Please note that our Quebecoin pool was noticeably less affected than others since the database was much smaller, and somehow has been easier to recover than others. Please take a look at the statement we posted online, detailing the situation and what has been done to ensure the smallest loss possible.
http://suchpool.pw/docs/statementdb.pdfIf you have any questions, you may contact us at admin@suchpool.pw (Make sure to mention which pool it is about, your username, your deposit address) We will verify and credit what has to be credited if applicable. Thanks for mining with us! Very nice and I'm sure you guys will recover from this nicely, I would like to think I will be able to perform as well as you guys have during the issues you had today. And here's to hoping you won't have to utilize those additional backup measures or go through this again in the future, or any of us for that matter. |
|
|
|
[/quote] Where is the wallet stopping? [/quote] It has always looked like this ever since I first downloaded it, and through the different fixes today.  [/quote] ok, at this point create a quebecoin.conf inside of "%AppData%\Quebecoin" that has the following addnode=54.86.39.92 addnode=54.85.54.67 addnode=54.86.58.113 addnode=54.86.60.197 addnode=54.86.60.189 addnode=54.84.203.45 |
|
|
|
Regarding the fixed wallet
"You need to go into your Appdata/Roaming/Quebecoin and delete the Blocks and Chainstate folders before opening the new wallet, It will sync perfectly".
I am still not getting sync after trying this fix either! Where is the wallet stopping? |
|
|
|
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.
Nice reminder I would probably have forgotten. Post your Qbc address I don't have tons but I'd like to send you something for your help. Here's my address QMRALZvwmmfKN9u27fNifpo7M4KQYnuKm1 if anyone feels like donating it will go nicely beside the 2 QBC I have mined so far. I'll be sending you some QBC when I send the IPO funds. A big thanks to your quick response, I really chose the worst moment to catch up on some sleep. I've merged your changes to the Github repo as well. I appreciate it, and it helps that I had seen the issue before so I knew the part of the code where the problem was as soon as it started happening. And anyone else out there that feels like helping out and passing on some hashing power come on over to http://qbc.cryptoadhd.com and you can help us find some blocks and donate via hashing power and get your QBC at the same time. |
|
|
|
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.
Nice reminder I would probably have forgotten. Post your Qbc address I don't have tons but I'd like to send you something for your help. Here's my address QMRALZvwmmfKN9u27fNifpo7M4KQYnuKm1 if anyone feels like donating it will go nicely beside the 2 QBC I have mined so far. |
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
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. |
|
|
|
{
"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. |
|
|
|
{
"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.. |
|
|
|
|
Show Posts
