ERROR - PLEASE HELP ME!
My Bitcoin have this ERROR:
“Warning: displayed transactions may not be correct! you may need to upgrade, or other nodes may need to upgrade”
My bitcoin is in error. I had about 13,000 BTC. I tried to transfer these coins to another computer. But I find the following error. Did not transfer the blocks that are being generated are invalid. What to do?
Dhaw sent me some of his debug.log files. Symptoms I saw:
- In most of the files his block count remains “stuck” at 1698.
- In one file he accepted blocks beyond that, but it went back to 1698 after he restarted Bitcoin.
- Any blocks he receives after 1698 he probably considers invalid. I haven’t seen the actual block rejection (it keeps getting removed by the auto-trim), but his debug.log is full of “block xxx have” messages for blocks that he clearly doesn’t recognize as valid.
- He is connected to real peers. He connected successfully to IRC, and he was able to connect to me with -addnode. I verified at my end that he is successfully sending getblocks messages.
I’m almost sure that Dhaw is not a scammer, and is a victim of some bug. My guess is that every time he restarts Bitcoin, his block database is corrupted.
He speaks ‘Portuguese (Brazilian)’. A translator would be helpful.
Dhaw generated all of these coins on his (her?) own machines.
Unfortunately, either due to a bug or some oddness with Dhaw’s network connections they were all generated on an alternate block chain.
The Bitcoin client really shouldn’t allow coin generation until you have all of the blocks up to the last block checkpoint.
Dhaw sent me some of his debug.log files. Symptoms I saw:
- In most of the files his block count remains “stuck” at 1698.
- In one file he accepted blocks beyond that, but it went back to 1698 after he restarted Bitcoin.
- Any blocks he receives after 1698 he probably considers invalid. I haven’t seen the actual block rejection (it keeps getting removed by the auto-trim), but his debug.log is full of “block xxx have” messages for blocks that he clearly doesn’t recognize as valid.
- He is connected to real peers. He connected successfully to IRC, and he was able to connect to me with -addnode. I verified at my end that he is successfully sending getblocks messages.
What does it take for a client to reject an incoming block from the network? If we know this we can work backwards and find out why he wants to reject every new block. There must be a transaction in the main chain 1699 or prior that his client disagrees with.
In any case, all the 1000s of bitcoins he generated were generated into a chain branch that only he was participating on, so they are worthless on the main chain. He would be generating 50 every 5 minutes being the only participant on that branch. The other curiosity is why he stood at 1698; this should have eventually started going up by 1 every 5 minutes when he recalculated difficulty.
What does it take for a client to reject an incoming block from the network? If we know this we can work backwards and find out why he wants to reject every new block. There must be a transaction in the main chain 1699 or prior that his client disagrees with.
He would have to disagree with 1699, but that is an empty block. There’s no reason he should disagree with that one.
My theory:
His antivirus cuts off files after a certain size. This caused his block database to be limited at 1698 (and maybe he rejects blocks after that due to corruption). However, his block index was not cut off (because it’s shorter), so he ignores incoming blocks as “already have”, even though he doesn’t really have them. Every time he generates a block, it is quickly destroyed by the antivirus, but its confirmations are preserved by the block index for some reason.
dhaw, what kind of antivirus or spyware are you running?
his block count remains “stuck” at 1698.
He was generating invalid blocks at difficulty 1.0. He must have a corrupted entry in his blk0001.dat or blkindex.dat file. He just needs to delete blk*.dat and let it redownload.
The safety lockdown detected the problem and was displaying “WARNING: Displayed transactions may not be correct!” because it saw a longer chain existed that it was unable to accept. The safety lockdown cannot stop generation or it would create an attack possibility.
Quote from: gavinandresen on October 22, 2010, 5:25:14 AM UTCThe Bitcoin client really shouldn’t allow coin generation until you have all of the blocks up to the last block checkpoint.
Good idea, I made a change to make sure it won’t generate before checkpoint block 74000.
He was generating invalid blocks at difficulty 1.0. He must have a corrupted txindex entry in his blkindex.dat file. He just needs to delete blk*.dat and let it redownload.
He already did that, and the same problem occurred right away. So it’s probably an antivirus issue.
OK, if it really won’t get past block 1698 on redownload, then we’re in stranger territory.
Yes, possibly he has antivirus software or even a router or filewall that is pattern matching a sequence of bytes and censoring it.
It would be instructive to get knightmb’s blk*.dat and see if that gets him past that point.
dhaw, what kind of antivirus or spyware are you running?
AVG ANTIVIRUS
Quote from: jimbobway on October 23, 2010, 6:16:49 PM UTCdhaw, what kind of antivirus or spyware are you running?
AVG ANTIVIRUS
Go to the AVG Virus Vault to see what AVG has detected.
And now?? =( More than 3 months lose?
I don’t know if it will make you feel any better, but if you had been working on the real chain the last few months you would only have a few hundred because the difficulty of your personal chain was way lower than real difficulty.