Bitcoin-Qt / bitcoind version 0.8.0 released

[blockbet.net]

Great work guys, can't say how grateful I am for the work you're doing. I have a question though:

Zero-confirmation transaction vulnerability: accepting zero-confirmation transactions (transactions that have not yet been included in a block) from somebody you do not trust is still not recommended, because there will always be ways for attackers to double-spend zero-confirmation transactions. However, this release includes a bug fix that makes it a little bit more difficult for attackers to double-spend a certain type ("lockTime in the future") of zero-confirmation transaction.

I assume this means only transactions sent from 0.8.0? So that an attacker can just keep using the older version for his purposes, regardless of if the receiver has the latest version. Not saying that it still isn't a very important fix to have for the future.

Also, yesterday I saw some very quick confirmations on a lot of transactions, even no-fee transactions were generally confirmed in less than 10 minutes, which is very good for business. Does that have something to do with this update or is it just a coincidence?

[Xenland]

Nice job on 0.8.0 guise.... Everything is super quick -- LOVE IT!

[Joshwaa]

What are all the sst files for? Also you might want to post what can be cleaned up after the install since the install does not do it. Also during install it would be nice if you could let the user specify the datadir rather than using a command line flag.

[jgarzik]

Also, yesterday I saw some very quick confirmations on a lot of transactions, even no-fee transactions were generally confirmed in less than 10 minutes, which is very good for business. Does that have something to do with this update or is it just a coincidence?

Just a coincidence.  ASIC miners are rapidly coming online, which increases block production until difficulty changes to compensate.

[burger]

I am using Windows XP SP3.

H:\Bitcoin>dir
 Volume in drive Q is BITCOIN
 Volume Serial Number is XXXX-XXXX

 Directory of Q:\Bitcoin

2013-02-21  09:31 AM    <DIR>          .
2013-02-21  09:31 AM    <DIR>          ..
2012-09-18  10:19 AM                 0 .lock
2012-09-18  13:57 PM         3,850,240 addr.dat
2012-09-27  12:05 PM           131,072 backup.dat
2012-09-18  13:25 PM     2,097,384,811 blk0001.dat
2013-01-04  10:34 AM     2,097,346,788 blk0002.dat
2013-02-20  22:13 PM     1,561,011,203 blk0003.dat
2013-02-20  22:18 PM     1,809,104,896 blkindex.dat
2013-02-20  22:28 PM    <DIR>          blocks
2013-02-21  09:22 AM    <DIR>          chainstate
2013-02-20  22:18 PM    <DIR>          database
2012-09-24  08:41 AM                 0 db.log
2013-02-21  08:31 AM           564,356 debug.log
2013-02-21  09:31 AM           956,384 peers.dat
2013-02-21  09:18 AM           172,032 wallet.dat

What can I safely delete? I highlighted in bold and color what I think can be deleted. Can someone confirm this?

You can safely delete those that you highlighted. As the new files is in the "blocks" directory.

Easiest way for you to check is to close the bitcoin client, move those files to another directory and then start the client again and check if it starts downloading the blockchain again.

[stevegee58]

Too bad bitcoin-qt can't use your GPU to accelerate re-indexing the block chain.  It's already using multiple CPU cores if they're available.

[Offthechain]

Working nicely on Windows 8... where is the PPA for some Linux love?

[pointbiz]

0.8.0 is great. Thanks to all the developers!!

Much faster when catching up with the blockchain.

[Turbor]

What is causing this ? I'm having a hard time to get 0.8.0 up to date. Win7 32. 2 PCs, same troubles. 0.7.2 was working flawless.

Code:

ERROR: CScriptCheck() : 8c57009daa VerifySignature failed
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a  height=217275  work=730573305004647527300  date=2013-01-20 11:41:29
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a  height=217275  work=730573305004647527300  date=2013-01-20 11:41:29
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ERROR: SetBestBlock() : ConnectBlock 00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
InvalidChainFound: invalid block=000000000000026e70652663fd4a5e3a1c38cfdf0c1b2666308c3816d9c21321  height=217276  work=730587261926805361411  date=2013-01-20 11:54:13
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002602d8d5f70644e63c7a769f703b538fb360de81c79640aacb1  height=217277  work=730601218848963195522  date=2013-01-20 12:10:44
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002f4ac17297159fd95b2635cf58e07a3ee32d883431fb91fd17b  height=217278  work=730615175771121029633  date=2013-01-20 12:12:51
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000001aecaa201b51744d687a607aa2bd16a671c0016936c8909001d  height=217279  work=730629132693278863744  date=2013-01-20 12:34:11
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004c2691dc97dceae2ec9c03e201e5894b6fc9a3c9793b978ac1a  height=217280  work=730643089615436697855  date=2013-01-20 12:37:08
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004d3a906d8e8582c4bdb9605b04553b869345c33499767145c92  height=217281  work=730657046537594531966  date=2013-01-20 12:38:24
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

[Technomage]

What is causing this ? I'm having a hard time to get 0.8.0 up to date. Win7 32. 2 PCs, same troubles. 0.7.2 was working flawless.

Code:

ERROR: CScriptCheck() : 8c57009daa VerifySignature failed
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a  height=217275  work=730573305004647527300  date=2013-01-20 11:41:29
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
InvalidChainFound: invalid block=00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a  height=217275  work=730573305004647527300  date=2013-01-20 11:41:29
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ERROR: SetBestBlock() : ConnectBlock 00000000000000e788455adcba11a49a452acd5298e3a26d2db4cb9fcc050d1a failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
InvalidChainFound: invalid block=000000000000026e70652663fd4a5e3a1c38cfdf0c1b2666308c3816d9c21321  height=217276  work=730587261926805361411  date=2013-01-20 11:54:13
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002602d8d5f70644e63c7a769f703b538fb360de81c79640aacb1  height=217277  work=730601218848963195522  date=2013-01-20 12:10:44
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000002f4ac17297159fd95b2635cf58e07a3ee32d883431fb91fd17b  height=217278  work=730615175771121029633  date=2013-01-20 12:12:51
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000001aecaa201b51744d687a607aa2bd16a671c0016936c8909001d  height=217279  work=730629132693278863744  date=2013-01-20 12:34:11
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004c2691dc97dceae2ec9c03e201e5894b6fc9a3c9793b978ac1a  height=217280  work=730643089615436697855  date=2013-01-20 12:37:08
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
ProcessBlock: ACCEPTED
InvalidChainFound: invalid block=00000000000004d3a906d8e8582c4bdb9605b04553b869345c33499767145c92  height=217281  work=730657046537594531966  date=2013-01-20 12:38:24
InvalidChainFound:  current best=00000000000000299acb81780e28cb8c04d0e96b29193b65ae70fe7eb8135702  height=217274  work=730559348082489693189  date=2013-01-20 11:25:02
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

Your problem seems almost identical to what I'm experiencing on my second PC. The computer itself works quite fine but I've still been completely unable to get 0.8 to sync till the end successfully. I've had corrupted blockchain and wallets, and the latest try resulted in similar errors that you posted, somewhere around 3500 blocks left. With 0.7 I had no problems.

On this PC however, I've had no problems with 0.8.

[Turbor]

Reindexing helps me getting closer to the end of the chain. But it's slow as hell One step forward, two steps back.

Edit: going back to 0.7.2. Hope future releases take care of this problem.

[Mike Hearn]

That sounds a lot like some kind of hardware failure.

[Turbor]

That sounds a lot like some kind of hardware failure.

On two machines ? Very unlike.

[Mike Hearn]

Re-indexing the block chain is unusually intensive. If there are minor faults being introduced by your HDD then most apps probably wouldn't detect them for a long time but Bitcoin is very sensitive to it. If it's not hardware related why are you seeing signature check failures (can only be caused by bad hardware, pretty much) and other machines are working fine?

[Technomage]

I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.

Maybe I need a new laptop.

[paraipan]

I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.

Maybe I need a new laptop.

Or just a new drive for it.

http://en.wikipedia.org/wiki/Solid-state_drive

[ColdHardMetal]

After finally absolutely having to upgrade from my oldschool 0.3.16 or something version, I have to say this is looking way more polished. Nice work all around

[deepceleron]

I agree with Mike Hearn that this is likely the cause. The PC I had this problem with is a 5 year old laptop which just might be breaking down slowly but surely. It's not a problematic PC otherwise but I guess LevelDB is intensive enough to be problematic if there is even a small flaw with the HD.

Maybe I need a new laptop.

Or take it apart and clean out five years worth of lint and fuzz and put new thermal compound on the CPU cooler:

[ProfMac]

I'm running Ubuntu 12.04, all upgrades applied, in a VirtualBox.  Almost all networking is IPv6.  The VirtualBox has 512 MB (<--small, I know) RAM.
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4

I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin.  I used ssh to copy the ~/.bitcoin directory over from the 0.7 installation.

My bitcoin.conf file includes
  connect=<my 0.7 installation address>
  onlynet=IPv6
  logtimestamps=1
  server=1

At startup, 0.8 seemed to index about 10-15 blocks / second.  I started it mid-day and the projections were that it would finish by 8PM last night.

At about 6AM this morning, it was still about 2,000 blocks from being indexed.  The speed had slowed to about 10-12 seconds / block.

With block 223,261 now onboard and everything current, and after erasing the old blockindex.dat file, du . shows 6,842,184 bytes.  This includes some logfiles that include timestamps.

One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted.  If the window is maximized, these items show up again.

[deepceleron]

I'm running Ubuntu 12.04, all upgrades applied, in a VirtualBox.  Almost all networking is IPv6.  The VirtualBox has 512 MB (<--small, I know) RAM.
The host machine is a dell Optiplex GX620, XP-SP3, 4 GB ram, 3.00 GHz pentium 4

I created a new virtual machine, created a disk specifically for bitcoin, and mounted it on ~/.bitcoin...

Congrats on running a 11 month old OS, on a 11 year old OS on a 10 years old computer (P4 3.0GHz release April 2003). There weren't many people trying to use a 1991 computer (pre CD-ROM) in 2001 (post-Google).

Is this progress or a lack of progress?

I'm running Ubuntu 12.04,
One thing I notice is that the menu (File, Help, & such) does not seem to display if the program is shut down, and then restarted.  If the window is maximized, these items show up again.

You are not the first to report strangeness with Unity (the bastard pile of MacOS wannabe move-the-menu-to-the-top bs that Ubuntu slapped on Gnome in order to keep up with Windows 8 in the stupidifying of GUIs). There is an official issue here: https://github.com/bitcoin/bitcoin/issues/1242 where you can add your steps to replicate on 0.8.0.

The workaround is sudo apt-get install kubuntu-desktop.