Bitcoin version 0.3.22

[phants]

0.01 BTC - demands the commission 0.01 BTC
0.10 BTC - hasn't proved to be true yet

Anyway I come back on 0.3.20.2.
At me with it problems aren't present.
Simply it would be desirable "the new" version

[CoinMan]

It would be nice if an admin would update this:
News: Version 0.3.21 is now available.

Thanks!

[alkor]

What about a MacOS version?

[TheMagikarp]

What about a MacOS version?

This.

[Maged]

bitcoin.org and weusecoins.com are still linking to the old version. As a result, in the just last few hours, we've gained ~100 0.3.21 users, and just a handful of 0.3.22 users. We still only have just 189 0.3.22 nodes online - barely more than at the end of RC testing. We need to do a better job of getting the word out.

[LightRider]

Forgot "-Preliminary development of double-secret CIA backdoor and un-anonymizing framework" in the notes.

[AltPluzF4]

Windows 7 Pro x64, RPC command "getwork" causes the rpc server to lock up, thread uses full CPU usage (25% on Q6600.)
Application has to be terminated via task manager.

No issue in 0.3.21, no other rpc commands seem to cause any problems, just "getwork"
First discovered problem by launching a local GPU miner (Phoenix), then verified it was the getwork command by testing with PHP client and just using the bitcoin command line.

Tested in a XP VM, same result.

[qurashee]

Requesting "Eligius" and "0-fee" patched builds for Windows...!

Here you are: a 0-fee sir http://ifile.it/jyzwhpi . I'll talk to luke about the eligius version and make a binary soon.

[AltPluzF4]

Here you are: a 0-fee sir http://ifile.it/jyzwhpi . I'll talk to luke about the eligius version and make a binary soon.

Just out of curiosity, I tested your binary. My 'getwork' issue is resolved with it. Could you please send the source used to compile it? I'd like to do a diff on it and the official release :-/

[waspoza]

Got errors on my ubuntu:

/home/bitcoin/bin/bitcoind: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /home/bitcoin/bin/bitcoind)
/home/bitcoin/bin/bitcoind: /lib/libc.so.6: version `GLIBC_2.11' not found (required by /home/bitcoin/bin/bitcoind)


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 9.04
Release:        9.04
Codename:       jaunty

[M4v3R]

Got errors on my ubuntu:

/home/bitcoin/bin/bitcoind: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /home/bitcoin/bin/bitcoind)
/home/bitcoin/bin/bitcoind: /lib/libc.so.6: version `GLIBC_2.11' not found (required by /home/bitcoin/bin/bitcoind)


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 9.04
Release:        9.04
Codename:       jaunty

As far as I know Ubuntu builds work only on newer Ubuntu releases, you have too old one.

[timmmay]

Just updated my client on OpenSUSE 11.4.  Was running 0.3.21 fine but this one doesn't seem to be doing anything...

It's been running for about 20 mins.  Output of getinfo:

 # ./bitcoind getinfo
{
    "version" : 32200,
    "balance" : 0.00000000,
    "blocks" : 0,
    "connections" : 0,
    "proxy" : "",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 1.00000000,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1307348470,
    "paytxfee" : 0.00000000,
    "errors" : ""
}


I've forwarded 8333 to it to see if that helps but no.  It has a connection to irc.lfnet.org but nothing on port 8333.  I've checked my firewall logs too and nothing so far!

Any ideas?

EDIT: Seems to be working now, just took a lot longer than expected!

[jashan]

What about a MacOS version?

This.

Was that supposed to be a link? I'm also looking for a Mac version ... and btw, on bitcoins.org, it still says 0.3.21.

[waspoza]

Got errors on my ubuntu:

/home/bitcoin/bin/bitcoind: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /home/bitcoin/bin/bitcoind)
/home/bitcoin/bin/bitcoind: /lib/libc.so.6: version `GLIBC_2.11' not found (required by /home/bitcoin/bin/bitcoind)


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 9.04
Release:        9.04
Codename:       jaunty

As far as I know Ubuntu builds work only on newer Ubuntu releases, you have too old one.

Yeah, thought so.
Too bad i cannot upgrade this box. Back to the old version it seems...

[qurashee]

Here you are: a 0-fee sir http://ifile.it/jyzwhpi . I'll talk to luke about the eligius version and make a binary soon.

Just out of curiosity, I tested your binary. My 'getwork' issue is resolved with it. Could you please send the source used to compile it? I'd like to do a diff on it and the official release :-/

Sure, no need to upload the whole source, i just downloaded the zip file from the first post and in main.h changed the line that read  return dPriority > COIN * 144 / 250; into : return true;

This patch was proposed by the user Raulo here, and is not mine.

[Lucidize]

When I upgrade to this new version, will my original Bitcoin address be saved?

Thanks 

[Matt Corallo]

Sure, no need to upload the whole source, i just downloaded the zip file from the first post and in main.h changed the line that read  return dPriority > COIN * 144 / 250; into : return true;

This patch was proposed by the user Raulo here, and is not mine.

Please dont do that, that changes several other unrelated things that shouldn't be.  If you really want the option to more granularly control the fee, please build my better fee ui branch instead. Works much better and doesnt have adverse side effects on other uses of transaction acceptance.
Also, that wont change build results, can you give more information on your build environment?

[bitnut]

Beware that this version still seems to have the bug where initial wallet.dat creation does not fill the keypool with 100 pregenerated keypairs. Someone just lost a lot of BTC because of that (see http://forum.bitcoin.org/index.php?topic=11104.0).

There is a bug where the creation of the first-ever address (with label "Your Address") does not trigger filling of the keypool. The keypool is only filled once the next address is created, and then it takes tens of minutes to fill completely.

[Matt Corallo]

Beware that this version still seems to have the bug where initial wallet.dat creation does not fill the keypool with 100 pregenerated keypairs. Someone just lost a lot of BTC because of that (see http://forum.bitcoin.org/index.php?topic=11104.0).

Actually that guy lost his coins before keypool was created, in fact, keypool was created as a response to that person's post.
That said, yes you are right, before you backup the first time, make sure you get some coins and/or send some.

[timmmay]

It's taken this new install 4 hours so far to rescan the block count.  It's up to 121625 and still probably has 30 mins or so to go....very annoying!