Bitcoin version 0.3.22

[Veldy]

So, should the rest of us downgrade?  Meaning those of us using 64-bit operating systems or only using the client for wallet management.  The reason that I ask is because of some of the network changes on the back end (not visible in the user interface).  It seems to be working for me, but I thought it would be worth asking in any event.

[1715235958]

1715235958

[1715235958]

1715235958

[1715235958]

1715235958

[xf2_org]

So, should the rest of us downgrade?  Meaning those of us using 64-bit operating systems or only using the client for wallet management.  The reason that I ask is because of some of the network changes on the back end (not visible in the user interface).  It seems to be working for me, but I thought it would be worth asking in any event.

No.  This only impacts miners on Windows.

[AtlasONo]

No wallet encryption???

[Matt Corallo]

I get the dreaded 'problems communicating with rpc server' with this version and it never connects. Old version works fine.

This is a result of the Windows lockup on getworks.  If you call getwork, RPC thread will lock and stop responding.  Thus your miner is timing out.  As stated, Windows users who mine from a windows-hosted Bitcoin should not upgrade until 0.3.23 comes out.  There are no other known problems with this release. Sorry about that, my fault.

[xf2_org]

MAC OSX version of 0.3.22 uploaded to SF (see top post for URL).  Thanks laszlo!

Code:

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

5798efd33d38d530428d22aa4edf37e99731072e  /g/g/tmp/bitcoin-0.3.22-macosx.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIVAwUBTe/SUtodwg8tvwyoAQItrA//ZofOQ4OfMZALNwqeJka3uNbBj0wfySkS
v3JULVdCCWrWeNeGa4BPs/0ESoGYKpcIHh3R79f+E7EVig7DMYbsjvVkvS519eaQ
fTdYqUimHIALWVs9F3eunn4nVzrorwvQtIq+pSJ13Af6AMdV5ICU0Mfxpwuxagvy
xMss5+CllINMh1Cdqm3VzcRs4mE+9C9i6SJB9h//PnxiA9zqz4QruVNb2ayGrzSB
xMcNLOETssL7LAMfUvTB50jc7zBEdrLw3MhgC13AjM7KC1pRmI/DWBPvB2lFERme
j05AnA15ytJFly2xVooOF6fGq0qS7njXqcpUE6XwGuUTY97pM5HBRLFGz0T1himf
g7vbsPbGSvfzJxxRs1Fp6br+62C7epE+yXUjN2YMCkALjHHV8hyidhMM/9pyM32s
nLs9FbDFMqXyltYy5w2wBRR44NNL+YwIhScjLO93bbzO5vqx71dPGeihYUQOAwk2
KudOJMuUu2h5HmKHgJzkoTEJ8hoEx/Z8zmX/Iw0WQ2T/bVnEIGqMdkVdZXewFrOl
onKW4yVgwnLlNycHNkk8l6JOx/pQN23iWE23VSpYLeCJzYcWE0e6SKFo8x/7PbD9
R2a6nMExTZbZKI+821XpZCbT7drghAx3xBsO0pCBVcU6WDTBpTGLe3+DTLMYKpqk
84Qc5vCuurk=
=Ut4V
-----END PGP SIGNATURE-----

[xf2_org]

Updated MAC OSX link on http://www.bitcoin.org/ to point to 0.3.22, rather than 0.3.21.  Sorry I missed that detail, folks.

[xf2_org]

Ok, I upgraded to the new version. But now my client is not showing any connections, so is not downloading any more blocks. Is there a way to get more connections?

It will take a long time, unfortunately (could be a few hours), due to massive influx of new bitcoin users.  We should have that fixed in 0.3.23.

A useful workaround is -dnsseed

[foo]

Okay, it finally found some connections and is updating.

I thought the minimum fee was reduced to .0005 bitcoins? I tried sending some bitcoin and recieved the error message that it requires a transaction fee of .01 due to the complexity, size, or use of recently recieved funds.

0.3.23 will lower the fee.

I am sending >.01 BTC, so the size should be okay. I am just sending from one address to another, so the complexity should be okay. The funds have over 1000 confirmations, so they are not recently recieved (BTW, how recent is recent?, and am I correct that the recentness is measured by confirmations?). What am I missing?

You are probably combining a shitload of tiny coins, thus making a large (in kB) transaction.