Bitcoin version 0.3.21

[Gavin Andresen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Binaries for Bitcoin version 0.3.21 are available at:
  https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/

Changes and new features from the 0.3.20 release include:

* Universal Plug and Play support.  Enable automatic opening of a port
for incoming connections by running bitcoin or bitcoind with the
- -upnp=1 command line switch or using the Options dialog box.

* Support for full-precision bitcoin amounts.  You can now send, and
bitcoin will display, bitcoin amounts smaller than 0.01.  However,
sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so
you can send 1.0001 bitcoins without a fee, but you will be asked to
pay a fee if you try to send 0.0001).

* A new method of finding bitcoin nodes to connect with, via DNS A
records. Use the -dnsseed option to enable.

For developers, changes to bitcoin's remote-procedure-call API:

* New rpc command "sendmany" to send bitcoins to more than one address
in a single transaction.

* Several bug fixes, including a serious intermittent bug that would
sometimes cause bitcoind to stop accepting rpc requests.

* -logtimestamps option, to add a timestamp to each line in debug.log.

* Immature blocks (newly generated, under 120 confirmations) are now
shown in listtransactions.


SHA1-checksums for the binary files are:

54254cba039b02a2f49fdc98b8fe820d0fd4e410  bitcoin-0.3.21-linux.tar.gz
3f94d6a8b08c455a7886561089270247eaada7b4  bitcoin-0.3.21-win32-setup.exe
f9a39404433b01b5a22225855f42275c1c902c26  bitcoin-0.3.21-win32.zip
(mac version should be ready soon)

Thanks to all those who contributed to this release:

Dan Helfman
Dan Loewenherz
devrandom
Eric Swanson
gjs278
Jeff Garzik
Luke Dashjr
Matt Corallo
Matt Giuca
Nils Schneider
ojab
Pieter Wuille
sandos
Santiago M. Mola
Sven Slootweg

Gavin Andresen   gavinandresen@gmail.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAk24UbsACgkQdYgkL74406jQlwCeOPf1avdfugmzfiVtuT0hUacm
4DEAoJcAR0ha8VKQ8Mu6QoG9ywDLvwjI
=DRxu
-----END PGP SIGNATURE-----

[theymos]

Are you going to put the source on SourceForge SVN?

[Gavin Andresen]

Are you going to put the source on SourceForge SVN?

Yup.  I think this might be the last release I do that, though...

EDIT: Done, svn revision 251.

[ribuck]

Many thanks to all the developers who make this happen!

[bitcoinex]

Cool!

[AtlasONo]

However,sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so
you can send 1.0001 bitcoins without a fee, but you will be asked to
pay a fee if you try to send 0.0001).

I tried sending .01001 and i still got prompted for a fee, same with .10001. Is this quote misleading or is this a bug?

[theymos]

Yup.  I think this might be the last release I do that, though...

EDIT: Done, svn revision 251.

Thanks.

I thought the idea of using SVN for "release candidate" code was good. Stability and security are very important for Bitcoin, so there needs to be a long testing period before stable releases are made.

[bitcoinex]

However,sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so
you can send 1.0001 bitcoins without a fee, but you will be asked to
pay a fee if you try to send 0.0001).

I tried sending .01001 and i still got prompted for a fee, same with .10001. Is this quote misleading or is this a bug?

May be we must want before 1/2 of all bitcoind been updated to this version?

[dacoinminster]

I really want to try out sendmany, but I'm a little nervous about being the unlucky person to find the corner-case bug that sends all your bitcoins to satan. Maybe I'll try it on another PC first.

[WakiMiko]

I noticed that bitcoind has to be explicitly started with -daemon in order for it to fork. Was that change intentional?

Also, how do i use the new -dnsseed parameter? -dnsseed=domain.here ? Regardless of what server I specify, the client doesn't seem to connect to it, although it does find other peers somehow, even with domains that are definitely not running a bitcoin client.

I really want to try out sendmany, but I'm a little nervous about being the unlucky person to find the corner-case bug that sends all your bitcoins to satan. Maybe I'll try it on another PC first.

Feel free to use my receiving address for testing :3

[Raulo]

I really want to try out sendmany, but I'm a little nervous about being the unlucky person to find the corner-case bug that sends all your bitcoins to satan. Maybe I'll try it on another PC first.

Sendmany works. One of the pool operators (slush I think) uses it for pool payments. And there is always testnet if you feel uneasy.

[SmokeTooMuch]

One thing I like to mention:

There is a display issue with the German version (only German ?) when setting the font-size to 125% in Win7.


Bitcoin then looks like that:

Note the Number in the lower right corner. Afaik it is the Number of total transactions but the label isn't fully shown.

Also, when you click on ->sending (->Überweisen) you get this error message:


And when you finally get to the transfer dialog, it looks like that:

Pretty messed up. You have to resize the window to get to the "transfer" and "cancel" button.

And since the "settings window" can not be resized like all the other ones, I cannot change the transaction fee:

This sucks.

I know this only affects like <1% of the bitcoin userbase but anyways,
can this be fixed somehow ?

[toffoo]

ummm ... Mac binary?     /Apple-flavored tears     

[grondilu]

* Support for full-precision bitcoin amounts.  You can now send, and
bitcoin will display, bitcoin amounts smaller than 0.01.  However,
sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so
you can send 1.0001 bitcoins without a fee, but you will be asked to
pay a fee if you try to send 0.0001).

Hang on.  Am I the only one who thinks this is big news?

[xf2_org]

I noticed that bitcoind has to be explicitly started with -daemon in order for it to fork. Was that change intentional?

Can you describe exactly what behavior you are seeing?  Include OS/platform details.

"bitcoind" should default to being a daemon server; "bitcoin" does not do this.

Also, how do i use the new -dnsseed parameter? -dnsseed=domain.here ? Regardless of what server I specify, the client doesn't seem to connect to it, although it does find other peers somehow, even with domains that are definitely not running a bitcoin client.

The DNS seeds are pre-compiled into the binary, just like the static IP address 'seed' node list that has existed for many versions.

[allinvain]

gavin, any idea when the bitcoin client will have a wallet.dat encryption feature?

[WakiMiko]

Can you describe exactly what behavior you are seeing?  Include OS/platform details.

"bitcoind" should default to being a daemon server; "bitcoin" does not do this.

It happens for me both on Debian Squeeze and Ubuntu 10.10. After starting bitcoind from a terminal it doesn't fork and I can cancel out of it with ^C (or by closing the terminal). Starting bitcoind with the -daemon switch results in the old behaviour and the process forks/detaches from the terminal and runs in the background after printing "bitcoin server starting".

[kseistrup]

* Universal Plug and Play support.

Which version of libminiupnpc4 is required?  I have libminiupnpc4 1.4, and get the following errors when compiling bitcoind (even with USE_PNP=0) on Linux:

Code:

g++ -c -O2 -Wno-invalid-offsetof -Wformat -s -m64 -mtune=core2 -march=core2 -fomit-frame-pointer -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -DUSE_UPNP=0 -o obj/nogui/net.o net.cpp
net.cpp: In function ‘void ThreadMapPort2(void*)’:
net.cpp:916: error: ‘struct IGDdatas’ has no member named ‘first’
net.cpp:930: error: ‘struct IGDdatas’ has no member named ‘first’
make: *** [obj/nogui/net.o] Error 1

Cheers,

[kseistrup]

Code:

[…] -DUSE_UPNP=0 […]

Could it be that -DUSE_UPNP=0 triggers ‘#ifdef USE_UPNP’ (it is def'ed, although set to zero)?  If tried replacing ‘-DUSE_UPNP=0’ with ‘-UUSE_UPNP’, and everything compiled smoothly. 

Cheers,

[LightRider]

Will there be an x86-64 client?