Bitcoin-Qt / bitcoind version 0.8.0 released

[debianlinux]

Wow, so my datadir went from ~7GB to ~13.5GB.

Is there any of this that is deprecated and can be pruned? I regularly backup the entire datadir and having it double in size in one day as opposed to over a couple of years is kind of harsh.

[Gabi]

It doubled because the old blockchain is still there?

[debianlinux]

It doubled because the old blockchain is still there?

well, I seriously doubt that there is a new blockchain, lol
also it didn't run long enough to download a duplicate, it just reindexed
surely some of this can be deleted but I am unsure what is safe to delete.

[deepceleron]

Wow, so my datadir went from ~7GB to ~13.5GB.

Is there any of this that is deprecated and can be pruned? I regularly backup the entire datadir and having it double in size in one day as opposed to over a couple of years is kind of harsh.

You can remove blk0001.dat, blk0002.dat, blk0003.dat and blkindex.dat from the data directory after a reindex is complete and you are caught up with the blockchain (and you don't plan on going back to an older version). Only blkindex should actually be using disk space, as the old BLK000x data are moved upon upgrade, and the blk000x.dat files you see there are hardlinks (shortcuts) on any filesystem that supports hardlinking.

[Pieter Wuille]

You can remove blk0001.dat, blk0002.dat, blk0003.dat and blkindex.dat from the data directory after a reindex is complete and you are caught up with the blockchain (and you don't plan on going back to an older version). Only blkindex should actually be using disk space, as the old BLK000x data are moved upon upgrade, and the blk000x.dat files you see there are hardlinks (shortcuts) on any filesystem that supports hardlinking.

Correct.

Technically, you don't even need to wait for the reindex to complete (as reindexing uses the block files in blocks/blk* to build chainstate and blocks/index).

[DannyHamilton]

As a benchmark for those who are interested, I installed 0.8.0 on a 5 year old 2.4 GHz Intel Core 2 Duo MacBook Pro with 4 GB 667 MHz DDR2 SDRAM and a NVIDIA GeForce 8600M GT 256 MB graphics processor running Mac OS X Lion 10.7.5.  The total synchronization time starting on 2013-02-19 was 22 hours, and the total disk space used is 6.4 GB

Disk usage:

Code:

$ pwd; du -h
~/Library/Application Support/Bitcoin
 31M    ./blocks/index
6.2G    ./blocks
193M    ./chainstate
10.0M   ./database
6.4G    .

[Dabs]

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?

[keystroke]

Do I need to update if I'm already running 0.8 rc1?

Yes there were some small changes.

[notme]

Does anyone know when the Ubuntu PPA will be updated?

I would ask the PPA maintainer.

[Technomage]

I've had major problems with this release on my 2nd computer. It's a 5 year old laptop with Windows Vista.

On the first reindex both the blockchain and the wallet got corrupted. On the first sync from nothing (I deleted the blockchain) the blockchain got corrupted. On the second sync from nothing I get this message that the transactions I'm seeing might not be valid, and that either me or the other nodes need to upgrade. It got stuck in 3354 blocks left. In the debug log it says something about an invalid chain.

I don't really know what to do other than stop running Bitcoin-Qt with this PC. I've had no other issues with the computer so it's kinda strange. The 0.7 version worked great as well.

[kwaaak]

Running well on Mac OS X 10.8.2 but the context menu entries when right-clicking on the Dock-item are gone for whatever reason.

[wachtwoord]

Network upgrade status

Wow people upgrade fast >71% of the network are running 0.7.x.. I'm still running at 0.6.3, may be time to upgrade to 0.7.x (I don't like running just released version for something that manages my money )

[Morblias]

Network upgrade status

Wow people upgrade fast >71% of the network are running 0.7.x.. I'm still running at 0.6.3, may be time to upgrade to 0.7.x (I don't like running just released version for something that manages my money )

That's why I make multiple backups when I upgrade. I mean, I trust the devs... but... 

[Rampion]

Running well on Mac OS X 10.8.2 but the context menu entries when right-clicking on the Dock-item are gone for whatever reason.

Same thing here. If you click on "close window", then you are unable to open it again. You close the window, you have to quit the client and restart.

In the old version, if you closed the window you could open it again just right clicking on the Dock-item and selecting "send bitcoins", "receive bitcoins" or whatever you wished to do.

[Rampion]

Another question: I see that now the client recommends a transaction fee of 0,01 per KB. That's quite an increase compared to the prior "recommended fee", which was 0,0005 if I my memory is not failing. What do you think about this? Personally I will set up the client that way, I like miners getting fair rewards for processing transactions.

Now a "n00b" question: is there a quick way to calculate how many kb will have your transaction?

[DannyHamilton]

Another question: I see that now the client recommends a transaction fee of 0,01 per KB. That's quite an increase compared to the prior "recommended fee", which was 0,0005 if I my memory is not failing. What do you think about this? Personally I will set up the client that way, I like miners getting fair rewards for processing transactions.

Now a "n00b" question: is there a quick way to calculate how many kb will have your transaction?

Unfotunately no.  There isn't even a way to configure the coin selection routine to optimize for minimum fee for the current transaction vs. maximum efficiency in consolidating small outputs.

[cypherdoc]

i don't see it in the PPA

[dooglus]

Now a "n00b" question: is there a quick way to calculate how many kb will have your transaction?

If you know how many inputs and outputs your transaction will have, then yes:
  http://bitcoin.stackexchange.com/a/3011/659

Else no.

[vapourminer]

nice!

took about 45 minutes on my win7x64/intel 3570k@4.4/8 gig/intel G2 SSD to resync the blockchain.

all in all, a pretty painless upgrade.

thank you.

EDIT: corrected the time.

[mb300sd]

Another question: I see that now the client recommends a transaction fee of 0,01 per KB. That's quite an increase compared to the prior "recommended fee", which was 0,0005 if I my memory is not failing. What do you think about this? Personally I will set up the client that way, I like miners getting fair rewards for processing transactions.

Now a "n00b" question: is there a quick way to calculate how many kb will have your transaction?

Unfotunately no.  There isn't even a way to configure the coin selection routine to optimize for minimum fee for the current transaction vs. maximum efficiency in consolidating small outputs.

I've noticed that lately, 90% of the transactions I've sent have been through the raw-tx api. You have full control over fees, outputs, change, etc.