[ANN] Bitcoin v0.3.23 release candidate available

[jgarzik]

Win32, Linux and source releases for bitcoin v0.3.23rc1 have been uploaded to
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/test/

This is another quick bugfix release, trying to deal with the influx of new bitcoin users.

Main items of note:

• P2P connect-to-node logic changed to reduce timeout a bit.  The network saw a huge influx of new users, who do not permit incoming connections.  This change is a short-term hack, to more quickly hunt for useful P2P connections.  Better "leaf node" logic is in the works, but this should let us limp along until then.
• Transaction fee reduced to 0.0005 for new transactions (see note below)
• Client will relay transactions with fees as low as 0.0001 BTC (see note below)

NOTE:  There has been some fee confusion recently.  Free transactions are supported and relayed as they always have been, according to special anti-spam rules.  See https://en.bitcoin.it/wiki/Transaction_fees for details.

Full git changelog:

Dean Lee (1):
      Updated Chinese Simp translation

Doug Huff (3):
      Fix rfc1918 and rfc3927 compliance for ignoring non-internet-routable host
      Add common temp files to .gitignore.
      Demystify a few magic numbers.

Han Lin Yap (2):
      Added Swedish translation
      Remove unused variable

Jeff Garzik (4):
      Bump version to 0.3.23.
      Reduce minimum TX fee for new transactions, to 0.0005.
      Lower minimum relay TX fee to 0.0001 (from 0.0005) BTC.
      Add minimal release process docs.

Matt Corallo (1):
      Fix CPU Usage bug when using -nolisten and have no connections.

Nils Schneider (1):
      create keypool in LoadWallet()

Pieter Wuille (3):
      Update transactions already in the wallet when rescanning.
      Fix for small change outputs
      Faster timeout when connecting

[jgarzik]

Note to self -- actually compile the newly updated translations.

[jgarzik]

SHA1 sums for rc1:
5ca82c5b694fc432b4b342dde5cd1b145e265f13  bitcoin-0.3.23rc1-linux.tar.gz
8853206ec4d9e48bb41a0482ac1367f6fb01bcad  bitcoin-0.3.23rc1-src.tar.gz
12952b1c4a15ce55564500dace18ee22eb2feaa8  bitcoin-0.3.23rc1-win32-setup.exe

PGP signature of same: http://paste.pocoo.org/raw/405066/

[Garrett Burgwardt]

Does this version allow opting out of the fee, whether recommended or not?

[jgarzik]

Does this version allow opting out of the fee, whether recommended or not?

For normal transactions yes.  For spam transactions no.  Quoting,

Free transactions are supported and relayed as they always have been,

[jgarzik]

MacOSX -rc1 binary uploaded.  Updated sums:

5ca82c5b694fc432b4b342dde5cd1b145e265f13  bitcoin-0.3.23rc1-linux.tar.gz
cdf6f76a41c880ebac53455e373fa78602da7be7  bitcoin-0.3.23rc1-macosx.zip
8853206ec4d9e48bb41a0482ac1367f6fb01bcad  bitcoin-0.3.23rc1-src.tar.gz
12952b1c4a15ce55564500dace18ee22eb2feaa8  bitcoin-0.3.23rc1-win32-setup.exe

PGP signed: http://paste.pocoo.org/raw/405159/

[Garrett Burgwardt]

Does this version allow opting out of the fee, whether recommended or not?

For normal transactions yes.  For spam transactions no.  Quoting,

Free transactions are supported and relayed as they always have been,

Right, I get that. But for example in 3.22 when trying to send a very low priority tx, you were forced to pay a fee. Do you now have the option to not send with a fee even though it will likely take a long time to be confirmed?

[jgarzik]

But for example in 3.22 when trying to send a very low priority tx, you were forced to pay a fee. Do you now have the option to not send with a fee even though it will likely take a long time to be confirmed?

No, you have to hack the client in order to send spam.

In the future, people are considering a checkbox to avoid the recommended fee.

[LightRider]

Can you display the full 8 decimal places in the Balance field? I don't like having a hidden amount of value left in my wallet.

[tabshift]

MacOSX -rc1 binary uploaded. 

Thanks for getting the Mac version out quickly!

[Prze_koles]

Can you display the full 8 decimal places in the Balance field? I don't like having a hidden amount of value left in my wallet.

Or at least 4 decimal places. 2 are not enough these days...

[ripper234]

Funny, I just headed over here to ask when is 0.3.23 due ... great timing

[ripper234]

Why does it still say "Fee 0.01 recommended"? (under settings->options)

[Maged]

Can you display the full 8 decimal places in the Balance field? I don't like having a hidden amount of value left in my wallet.

What you see is what you have. The full decimals will appear if you receive a transaction that has fractions of a bitcent.

[LightRider]

Can you display the full 8 decimal places in the Balance field? I don't like having a hidden amount of value left in my wallet.

What you see is what you have. The full decimals will appear if you receive a transaction that has fractions of a bitcent.

This is not true. I have received several full precision deposits, the full value of which is not reflected in the balance.

[kr105]

I'm using this beta and it shows 8 decimal places on the balance field 

[jgarzik]

Why does it still say "Fee 0.01 recommended"? (under settings->options)

Hum... good question...

[Ian Maxwell]

Everything looks okay from here. I'm seeing my full 8 digits of precision. As others have noticed, a 0.01 transaction fee is still "recommended", but that's just cosmetic.

Another cosmetic request: given the new fee schedule, could the minimal number of decimal digits displayed be either increased to 4, or decreased to 0?

[LightRider]

[Ian Maxwell]

LightRider: 0.44370502 + 0.07668922 - 2.17039424 = -1.65 exactly.