Do you get different answers for 'getbalance'  versus 'getbalance "*"' ?

There is a longstanding issue with they way unconfirmed transactions are counted that might be the source of your problem:
  https://github.com/bitcoin/bitcoin/issues/172

Pieter fixed the "100% usage on OSX bug" and I created and uploaded a fixed version 0.6.2.2 especially for the Mac.

RE: upgrading:  the best upgrade practice is to:

1) Backup your wallet someplace safe (if you're running an 0.6 release then use the Backup Wallet menu item).
2) Shutdown. Make sure Bitcoin isn't still in your system tray-- don't just close the window, shut it down.
3) Wait a minute or two (it can take older versions a minute or two to completely shut down)
4) Install and run the new version.

Over 50 BTC in donations with no fundraising effort-- thanks everyone who has donated so far!
 

Because when I was a young child a Portuguese family lived across the street from me and their oldest child bullied me mercilessly, making fun of my haircut and my funny Australian accent.

(KIDDING!  JUST KIDDING!)

Somebody to do translation quality assurance is a great idea. Want to volunteer?

Yeah, but you're probably a geek and think cute cat videos have too little actual information, too.

The video gets a +1 from me; effective marketing appeals to emotion, not intellect.

Bitcoin version 0.6.2 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.2/

This is a bug-fix and code-cleanup release, with no major new features.

Please report bugs using the github issue tracker at:
  https://github.com/bitcoin/bitcoin/issues

NOTABLE CHANGES
===============

Much faster shutdowns. However, the blkindex.dat file is no longer
portable to different data directories by default. If you need a
portable blkindex.dat file then run with the new -detachdb=1 option
or the "Detach databases at shutdown" GUI preference.

Fixed https://github.com/bitcoin/bitcoin/issues/1065, a bug that
could cause long-running nodes to crash.

Mac and Windows binaries are compiled against OpenSSL 1.0.1b (Linux
binaries are dynamically linked to the version of OpenSSL on the system).


CHANGE SUMMARY
==============

Use 'git shortlog --no-merges v0.6.0..' for a summary of this release.

Source codebase changes:
- Many source code cleanups and warnings fixes.  Close to building with -Wall
- Locking overhaul, and several minor locking fixes
- Several source code portability fixes, e.g. FreeBSD

JSON-RPC interface changes:
- addmultisigaddress enabled for mainnet (previously only enabled for testnet)

Network protocol changes:
- protocol version 60001
- added nonce value to "ping" message (BIP 31)
- added new "pong" message (BIP 31)

Backend storage changes:
- Less redundant database flushing, especially during initial block download
- Shutdown improvements (see above)

Qt user interface:
- minor URI handling improvements
- progressbar improvements
- error handling improvements (show message box rather than console exception,
  etc.)
- by popular request, make 4th bar of connection icon green



Thanks to everybody who contributed to this release:

Chris Moore
Dwayne C. Litzenberger
Gavin Andresen
Jeff Garzik
Luke Dashjr
Matt Corallo
Philip Kaufmann
Pieter Wuille
R E Broadley
Timothy Redaelli
Wladimir J. van der Laan
cardpuncher
freewil
graingert
sje397

On restart, you should be able to ask bitcoind for the top-of-chain block (using getblockcount/getblockhash/getblock).

If it's not in your database, then add it.  Then look at the previous block hash, and if it's not in your database ask bitcoind for it (and so on).

To be extra safe, after you're all done ask bitcoind for the top-of-chain block again to see if there was a block re-org while you were catching up.

See https://en.bitcoin.it/wiki/Public_relations

We'll announce a 0.6.2 later today, which is just 0.6.1 plus a last-minute bugfix for a crashing bug (I was THIS CLOSE to formally announcing 0.6.1 when Pieter found and fixed the bug...).

@luke-jr : I don't want to start an argument, but I still think we don't have enough testing resources to support 4 releases. I think we need to establish good QA for the main Bitcoin-Qt/bitcoind release before we worry about next-test or so-called-"stable" releases.

That's a good discussion for the Testing Project team to have, though, once it gets up and running a little more.

I'd also like the Testing Project to not get pigeonholed into "QA testing for Bitcoin-Qt/bitcoind", but to tackle cross-implementation compatibility (which I think is the next big, critical issue).

I'd still like to see several somebodies who know a lot more about networking than I do work on transmitting Bitcoin traffic over different networks (along with bridge nodes to shuffle traffic between the network we have now and the new networks).

I'd sleep easier if I knew that an as-yet-undiscovered bug in the network protocol we have now couldn't bring the entire system down. I'm confident we'd quickly fix whatever the problem is and I'm sure it would be back up and running within 24 hours, but it would be better if big merchants and miners and services could run two or more completely different bitcoin-network-stacks so they're less likely to be taken down by DoS attacks, bugs, or ISPs deploying deep packet inspection to try to block Bitcoin traffic.

+1

I still expect it to be a long and very bumpy road, but as long as the system keeps chugging away reliably processing transactions I think it will, overall, in the long run, gain more and more trust.

Miners won't switch to a 51% chain if it means they can't cash out the coins they're creating!

The attack we're talking about is "51% attacker refuses to include anybody else's transactions in their blocks."  And newly generated coins are useless to miners if they can't get transactions that spend them into the block chain....

I said:

I like decentralized approaches, because failures are less catastrophic and because I think smaller, focused organizations are more effective than big, try-to-be-everything-to-everybody organizations.

So I'm happy that the Cryptocurrency Legal Advocacy Group is working on legal issues, starting with figuring out what the issues are.

And I'm happy that LoveBitcoins have been starting PR/Marketing efforts for Bitcoin.

Today I created the Bitcoin Testing Project to tackle some infrastructure needs that I think are being ignored (rigorous quality assurance / testing):
   https://bitcointalk.org/index.php?topic=80019.0

I setup the wallet this afternoon, the donation address was:  (defunct address, don't send coins...)

I've been procrastinating creating a "Bitcoin Testing Project" to fund testing work, and I was actually thinking a few days ago that vulnerability bounties would fit in nicely as one of the things a Bitcoin Testing organization would tackle.

I decided to stop procrastinating today; see my announcement here for a Bitcoin Testing Project:
   https://bitcointalk.org/index.php?topic=80019.0

Testing changes to Bitcoin-Qt continues to be a chronic problem, and as alternative implementations of Bitcoin start to mature testing to make sure that they interoperate correctly and don't harm the network will become a big problem.

Therefore, I'm creating a decentralized, transparent organization using the BetterMeans system. I'll need help from people willing to be fundraisers, testers, project managers, toolmakers, troll-catchers, etc.

I'll create and hold a secure wallet that will be used for donations (at least until the project gets mature enough to turn over that responsibility to somebody else), but we'll use the BetterMeans "Credits" system so that everybody working on the project collaboratively decides who gets what, and what the priorities aught to be.

So: it is easy to talk about stuff like this, who's willing to help make it happen?  Send me an email at gavinandresen@gmail.com if this sounds like a project you'd like to help with, describing what you think the highest priorities for the project aught to be, how you could contribute, how much time you could contribute per week, and any relevant prior experience.

See doc/build-osx.txt in the source tree for how to build bitcoind on osx.

See doc/readme-qt.rst  for how to build Bitcoin-Qt.

That's a BIP 16 transaction:  see https://en.bitcoin.it/wiki/BIP_0016

I think this is The Idea That Will Not Die.

Bottom line: ain't gonna happen, everybody who created or purchased bitcoin over the last three years did so with the expectation the they would last forever, not that they would have some arbitrary 5-year expiration date.