|
1PFYcabWEwZFm2Ez5LGTx3ftz
|
 |
September 10, 2013, 09:59:18 PM |
|
Sorry for silly question, but would it not be better to release 0.8.5 version with this bug fixed, than to give instructions for workaround? Version 0.8.3 also had just one fix added, so why not do the same?
|
|
|
|
|
|
|
|
According to NIST and ECRYPT II, the cryptographic algorithms used in
Bitcoin are expected to be strong until at least 2030. (After that, it
will not be too difficult to transition to different algorithms.)
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
gmaxwell (OP)
Staff
Legendary
 Offline
Activity: 4158
Merit: 8382
|
|
September 11, 2013, 04:45:07 AM |
|
I encountered this problem this morning before I was aware of this thread, but in my case reindexing, although it took all day, was successful.
Indeed, reindexing will now work if after the reindex you leave the node running long enough to process the trigger block and the next ~100 blocks. However if more of these transactions get mined it will break again. It's ~mostly harmless to have the check level down, it just changes the checking at startup. ... it means _if_ you suffer disk corruption your node may eventually produce a bad block if mining or get stuck processing the chain in the future. That said, after this we may rename the checklevel knob in the next version just to turn it back to the normal level for people who've stuck in this workaround. Sorry for silly question, but would it not be better to release 0.8.5 version with this bug fixed, than to give instructions for workaround? Version 0.8.3 also had just one fix added, so why not do the same?
0.8.4 had three-ish changes, but they also had at least three weeks of testing (more much more for some of them). Partially this was possible because we were able to keep the bug that triggered the release a secret until publishing the fixed version. Because of the workaround is basically as good as the fix and factors mentioned above getting a fixed version out is slightly less urgent than it was for the first day after the issue happened, and I'm not inclined to rush out a version which isn't thoroughly tested. The fix for this is now merged in the git development branch. There will be an updated release soon. |
|
|
|
|
|
jwzguy
|
|
September 11, 2013, 08:41:04 PM |
|
Is it known who submitted these transactions, and with what client?
|
|
|
|
|
gmaxwell (OP)
Staff
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
September 12, 2013, 05:29:04 AM |
|
Is it known who submitted these transactions, and with what client?
I do. They were created by Genjix and his SX wallet software. Looks like it was due to a failure to initialize the version numbers in transactions. I was able to determine this because they spent funds send to the well known and oft reused libbitcoin donation address two hops back, so I sent Genjix an email to ask and he confirmed and tracked down his bug. |
|
|
|
|
|
|
|
|
BTC100
Newbie
Offline
Activity: 39
Merit: 0
|
|
September 13, 2013, 06:23:31 AM |
|
Thanks for the post, it's very helpful~
|
|
|
|
|
gmaxwell (OP)
Staff
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
September 13, 2013, 07:10:09 AM |
|
Is this the bug I reported back in March?
No, absolutely not. Your database was corrupted and needed reindexing. If you are on a mac, your issue may have been fixed in 0.8.4. |
|
|
|
|
|
World
|
|
September 13, 2013, 11:12:23 AM |
|
Is it known who submitted these transactions, and with what client?
SX wallet software This means that each experiment (SX wallet,mastercoin...etc)touch Tx can corrupted thousand users databases in Bitcoin-Qt? |
Supporting people with beautiful creative ideas. Bitcoin is because of the developers,exchanges,merchants,miners,investors,users,machines and blockchain technologies work together.
|
|
|
gmaxwell (OP)
Staff
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
September 13, 2013, 05:04:22 PM |
|
On my side reindexing fixed the problem. I'm using v0.8.3 Coin Control client on WinXP SP3. It will, sort of, if the problem transactions are not in the last 100-288 blocks or so and you leave it up after the rescan long enough catch up. But no need to now as 0.8.5 is out which fixes it. This means that each experiment (SX wallet,mastercoin...etc)touch Tx can corrupted thousand users databases in Bitcoin-Qt?
Thats why unusual transactions are normally filtered out by the network, but permitted on the separate testnet. The corruption in this case was inconsequential, but tripped up the start-time sanity checking. This particular issue is fixed now. |
|
|
|
|
bitcoinchecker
Full Member
Offline
Activity: 182
Merit: 100
Provider of Bitcoin products and services
|
|
September 13, 2013, 07:34:26 PM |
|
I didn't install the update the other day when the bug surfaced but after reloading the blockchain (it took 20hours) everything worked fine.
I have used the client to carry out many transactions since then with no problem. But this afternoon it "crashed" again and I am currently having to reload again. A pain in the arse and I will try to do everything correctly next time.
But what I want to know is why does (approx) 96% of the blockchain reload in about an hour and the last 4% take several hours?
|
|
|
|
LightRider
Legendary
Offline
Activity: 1500
Merit: 1021
I advocate the Zeitgeist Movement & Venus Project.
|
|
September 13, 2013, 10:14:47 PM |
|
But what I want to know is why does (approx) 96% of the blockchain reload in about an hour and the last 4% take several hours?
The checkpoint. |
|
|
|
OldDutchman777
Newbie
Offline
Activity: 46
Merit: 0
|
|
September 14, 2013, 02:45:37 AM |
|
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
|
|
|
|
|
Arto
Donator
Full Member
Offline
Activity: 213
Merit: 100
|
 |
September 14, 2013, 03:16:21 AM |
|
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me. |
|
|
|
OldDutchman777
Newbie
Offline
Activity: 46
Merit: 0
|
|
September 14, 2013, 03:54:14 AM |
|
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me. Thanks for the reply and I should have read this thread before posting. One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help. |
|
|
|
|
Arto
Donator
Full Member
Offline
Activity: 213
Merit: 100
|
|
September 14, 2013, 03:58:54 AM |
|
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me. Thanks for the reply and I should have read this thread before posting. One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help. I didn't go this route myself, but it sounds fine. It'll just take a good long while until it completes, so the "Abort" option would have been faster. Anyhow, one ought to always keep a backup copy of the wallet.dat file somewhere else, and with that in hand there's not much reason to worry; in the worst case you can always start over. |
|
|
|
OldDutchman777
Newbie
Offline
Activity: 46
Merit: 0
|
|
September 14, 2013, 04:55:18 AM |
|
Just got this message with Qt: "Corrupted Blockchain Detected do you want to rebuild". Advice please. TIA
Click "Abort" and upgrade to Bitcoin-Qt 0.8.5 before restarting the app. That sorted the problem for me. Thanks for the reply and I should have read this thread before posting. One more question: When this first occurred, I selected the option to begin re-indexing. Then decided I'd better research this matter before continuing and aborted the re-index at about 67 weeks remaining. I have now downloaded and installed 0.8.5. When I run the new version it is continuing the re-indexing from the abort point. Any problem, risk with allowing this to continue? Thank you, I really appreciate your help. I didn't go this route myself, but it sounds fine. It'll just take a good long while until it completes, so the "Abort" option would have been faster. Anyhow, one ought to always keep a backup copy of the wallet.dat file somewhere else, and with that in hand there's not much reason to worry; in the worst case you can always start over. Thanks again for the excellent info. Best |
|
|
|
|
|
Beans
|
|
September 14, 2013, 02:03:34 PM |
|
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
|
|
|
|
|
gmaxwell (OP)
Staff
Legendary
Offline
Activity: 4158
Merit: 8382
|
|
September 15, 2013, 01:06:22 AM |
|
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
If your database is actually corrupted then thats an unrelated issue. Database corruption can happen for many reasons unrelated to this. |
|
|
|
|
Bitcollector
Member
Offline
Activity: 65
Merit: 10
|
|
September 15, 2013, 02:40:06 AM |
|
I upgraded to 0.8.5 and tried to -checklevel=2 method. It's still asking to rebuild.
Mine is not asking to rebuild. Mine is just simply frozen and will not go passed the 23 behind. It says that its synchronizing with network, but its not doing anything. I had 0.8.1 this morning when I realized it was beginning to reload the whole block chain again. I got scared because I thought some virus screwed up my computer and I stopped the syncing. Then I saw someone suggested that to up grade to 0.8.5. This was a mistake because now nothing is happening and its frozen at 23 weeks behind. I have done the -checklevel=2 in the conf file. It did nothing. Then I put it in the properties of the start up ... still nothing. So, my question is ... of course, what do I do? delete everything except the wallet.dat file and reinstall? |
|
|
|
|
|
