Someone exploited the fact that BIP 16 isn't active to steal 0.004 BTC from someone who tried to use it. rc1 is enforcing BIP 16 unless you use -pushtoscripthashtime (see some other thread for what to set it to). In short, this problem is because 0.6.0rc* includes BIP 16 support before it is accepted by the Bitcoin network (as an attempt to force BIP 16 despite objections).
Disclaimer: BIP 17 would have the same problem if it were included in the client before network acceptance.
Edit: To clarify, the person who lost 0.004 BTC in this exploit must have intentionally modified his client to allow him to create such an insecure transaction.
Topic: Version 0.6 release candidate 1 - page 2. (Read 13469 times)
rc2 works so far.
Code:
received block 000000000000047e131d
SetBestChain: new best=000000000000047e131d height=170058 work=256371172561403830047
ProcessBlock: ACCEPTED
received block 00000000000003bd2bf5
SetBestChain: new best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ProcessBlock: ACCEPTED
received block 00000000000002dc756e
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
InvalidChainFound: invalid block=00000000000002dc756e height=170060 work=256384031705835696153
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : ConnectBlock failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 0000000000000abd377c
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=0000000000000abd377c height=170061 work=256390461278051629206
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 0000000000000a53cae4
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=0000000000000a53cae4 height=170062 work=256396890850267562259
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000001e8d049
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=00000000000001e8d049 height=170063 work=256403320422483495312
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 000000000000053f9bc9
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=000000000000053f9bc9 height=170064 work=256409749994699428365
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000006a2e732
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=00000000000006a2e732 height=170065 work=256416179566915361418
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000004c5954e
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=00000000000004c5954e height=170066 work=256422609139131294471
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
InvalidChainFound: WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 0000000000000867c28f
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=0000000000000867c28f height=170067 work=256429038711347227524
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
InvalidChainFound: WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block 00000000000008353651
REORGANIZE
ERROR: ConnectInputs() : 6a26d2ecb6 VerifySignature failed
ERROR: Reorganize() : ConnectBlock failed
InvalidChainFound: invalid block=00000000000008353651 height=170068 work=256435468283563160577
InvalidChainFound: current best=00000000000003bd2bf5 height=170059 work=256377602133619763100
InvalidChainFound: WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
0.5.2 works fine.
Also stuck on 170059.
Can't get past 170059.
Restarted bitcoin-qt 0.6.0-rc1, still stuck on 170059.
Gonna re-install 0.5.2.
Gonna re-install 0.5.2.
So, every single one of my rc1 nodes is stuck on block 170,059 and refuse to move forward. While I'm compiling rc2, does anyone know if this is a known problem?
Ditto.
Just shut it down, and restarting it.
So, every single one of my rc1 nodes is stuck on block 170,059 and refuse to move forward. While I'm compiling rc2, does anyone know if this is a known problem?
Possible fix for GUI freezing on Windows after a crash:
I started an in depth investigation and used Sysinternals Procmon.exe for this. I wanted to know which files or registry keys the client processes and one folder came to my attention.
Nice! Thank you very much for looking deeply into this; it looks like the inter-process-communication doo-hickey bitcoin uses to handle bitcoin: URLs was left behind when you blue-screened, and that's making startup fail the next time around. I started an in depth investigation and used Sysinternals Procmon.exe for this. I wanted to know which files or registry keys the client processes and one folder came to my attention.
By the way, is the IRC method for finding peers "deprecated" and should not be used anymore or what were the reasons to default that switch to 0.
Dia
Dia
thanks for your great job.
If it works I'm happy that I invested some hours into it
.Dia
thanks for your great job.
Possible fix for GUI freezing on Windows after a crash:
I started an in depth investigation and used Sysinternals Procmon.exe for this. I wanted to know which files or registry keys the client processes and one folder came to my attention.
C:\ProgramData\boost_interprocess\Select LastBootUpTime from Win32_OperatingSystem
This one contained 2 files, 1 which consisted of 32 "random" characters and looks like a hash and a BitcoinURL file of size 0. The files were still there after "killing" the client!
I'm working in IT, so call it luck or experience ... I deleted the whole C:\ProgramData\boost_interprocess folder, restarted the client, removed the database logs from the datadir and now everything works again! After I shutdown 0.6 RC2 these files disappear, so perhaps the former bluescreen with 0.6 RC1 made these files persistent, which freezes GUI after a Client re-start, because these 2 files can not be written to. I'm not sure, if 0.5.2 had this files, too ... so perhaps that's why 0.5.2 always worked!
Perhaps others should try this and perhaps this one is solved. But can any developer shed some light in here, what these folder or files have to do with the BC client?
Dia
I started an in depth investigation and used Sysinternals Procmon.exe for this. I wanted to know which files or registry keys the client processes and one folder came to my attention.
C:\ProgramData\boost_interprocess\Select LastBootUpTime from Win32_OperatingSystem
This one contained 2 files, 1 which consisted of 32 "random" characters and looks like a hash and a BitcoinURL file of size 0. The files were still there after "killing" the client!
I'm working in IT, so call it luck or experience ... I deleted the whole C:\ProgramData\boost_interprocess folder, restarted the client, removed the database logs from the datadir and now everything works again
! After I shutdown 0.6 RC2 these files disappear, so perhaps the former bluescreen with 0.6 RC1 made these files persistent, which freezes GUI after a Client re-start, because these 2 files can not be written to. I'm not sure, if 0.5.2 had this files, too ... so perhaps that's why 0.5.2 always worked!Perhaps others should try this and perhaps this one is solved. But can any developer shed some light in here, what these folder or files have to do with the BC client?
Dia
I should have read this thread from the beginning, as this is the behaviour I observed, too! Any info on this?
Unfortunately, no. There have been a rather large number of bugfixes since 0.6.0rc1 however, and 0.6.0rc2 will be created very soon. I hope this problem is fixed by now.
If not I will help debugging it for sure!
Dia
It would be great if someone could create a windows installer for release candidates, like Luke-Jr did with the next-test branch here. Would bring in a lot more testers I'm sure.
Is this not satisfactory?http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/
Oops, sorry about that. I read through the first post a bit too quickly.
I should have read this thread from the beginning, as this is the behaviour I observed, too! Any info on this?
Unfortunately, no. There have been a rather large number of bugfixes since 0.6.0rc1 however, and 0.6.0rc2 will be created very soon. I hope this problem is fixed by now.
It would be great if someone could create a windows installer for release candidates, like Luke-Jr did with the next-test branch here. Would bring in a lot more testers I'm sure.
Is this not satisfactory?http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/
It would be great if someone could create a windows installer for release candidates, like Luke-Jr did with the next-test branch here. Would bring in a lot more testers I'm sure.
Yesterday my pc crashed for no aparent reason (just went like what seemed to be standby, then after 10 seconds rebooted). When i started bitcoin client it took about 2-3 minutes to load before the gui popped up.
After the gui shows it just freezes, can't click anything, task manager claims it's not responding, also RPC doesnt reply to commands.
I did a chkdsk but all seems fine there...
Also, all seems good when reverting back to 0.5.2.
Can't really explain it or reproduce the crash exactly, all i know is that 0.6rc1 now freezes whenever i start it. Used to work just fine before.
After the gui shows it just freezes, can't click anything, task manager claims it's not responding, also RPC doesnt reply to commands.
I did a chkdsk but all seems fine there...
Also, all seems good when reverting back to 0.5.2.
Can't really explain it or reproduce the crash exactly, all i know is that 0.6rc1 now freezes whenever i start it. Used to work just fine before.
I should have read this thread from the beginning, as this is the behaviour I observed, too! Any info on this?
Dia
Jump to: