From: Jeff Garzik <jgarzik@exmulti•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] [ANN] Bitcoin v0.3.23 release candidate available
Date: Sun, 12 Jun 2011 00:48:10 -0400 [thread overview]
Message-ID: <BANLkTineGhQW33aZ0oLvGf9vJY8XLxjxPg@mail.gmail.com> (raw)
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 (NOTE: free
transactions are, of course, still supported as they always were)
* Client will relay transactions with fees as low as 0.0001 BTC
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
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
reply other threads:[~2011-06-12 4:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTineGhQW33aZ0oLvGf9vJY8XLxjxPg@mail.gmail.com \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox