Sure enough, the network doesn't see it.  What was the From address?

Yes, a corrupt operator can slightly manipulate the timestamps for a marginal benefit.

Doing a it would in a big way would require a significant 51% attack where considerable amounts of history were rewritten in order to achieve a moderate benefit. It is theoretically a problem, but the risk/cost/reward is poor.  As such I don't think anyone has ever bothered.

Would you mind posting the address or txid so we can have a look?

https://en.bitcoin.it/wiki/Block_timestamp

Timestamps are checked against network time and your local time.  Nodes refuse to relay if the block's time is too far off.

No problem!  I'm always glad to help. 

Try:

mv ~/.bitcoin ~/.bitcoin-old
mkdir ~/.bitcoin
cp ~/.bitcoin-old/wallet.dat ~/.bitcoin
echo rpcpassword=somerandomjunk > ~/.bitcoin/bitcoin.conf
./bitcoind -daemon



edit: Fixed the echo line

Did you actually get and install bitcoin?  Try this:

wget http://softlayer.dl.sourceforge.net/project/bitcoin/Bitcoin/bitcoin-0.6.3/bitcoin-0.6.3-linux.tar.gz
tar -xf bitcoin-0.6.3-linux.tar.gz
cd bitcoin-0.6.3-linux/bin/32/
mv ~/.bitcoin/brute.rb .
echo rpcpassword=somerandomjunk > ~/.bitcoin/bitcoin.conf
./bitcoind -daemon

... wait a minute while it starts up ...

ruby brute.rb

And it should start cracking.

Is bitcoind in the .bitcoin dir?  To be clear, it needs to be in the directory with the Satoshi client program goes, not the one where the wallet.dat goes.

Did you put it in the same dir as bitcoind? 

It needs to be able to run it and it only looks in the current dir.

Don't forget:  set an RPC password

Also, do it while disconnected from the net so it's not trying to download the blockchain while it runs.  That'll just slow things down.

If you want to use my script:

Install Ruby - http://www.ruby-lang.org/en/downloads/
Save the script to brute.rb in the same directory as bitcoind
Edit the script to change the passphrase from "oops" to your best guess
Start up bitcoind
run: ruby brute.rb

The script was originally for Linux but it should work on OSX or Windows with some small changes.

https://bitcointalk.org/index.php?topic=52155.0;all
https://bitcointalk.org/index.php?topic=60703.0;all
https://bitcointalk.org/index.php?topic=86589.0;all

tl;dr: You need to find a problem that is: 1) very hard to solve (about 20,000 GPU-hours per solution); 2) trivial to verify it was done correctly (less than 1 GPU-second per check); 3) politically neutral (we have to agree on the problem being solved, and some people will object to using their GPUs to solve some problems).

No one knows a useful problem in this category, so we're using SHA256.  Feel free to suggest something better, but criteria #2 is the hard one.

Thanks.    Glad to hear it worked out.

Start by looking in the db.log and debug.log.  Post them here if you want us to have a look.

It's just so that it wraps into the available width.  Delete the space.  

Edit: 165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g

Yeah, I've seen that on blockexplorer sometimes.  I suspect it happens occasionally when it's busy.

<-  My address is right over there. 

And no problem, always glad to help.

http://blockchain.info/ or http://blockexplorer.com/

Just enter your address in the search box.

10 is plenty.  The update is usually limited by the speed of your CPU and disk, not the number of connections.

0.6.2 should update faster than 0.3.23.  Just give it a bit.

%APPDATA%\Bitcoin

On Windows 7, that means C:\Users\(username)\AppData\Roaming\Bitcoin

But you shouldn't have to do anything manually.  Upgrading won't delete the wallet.dat, so it'll already be there when you start it up again.

Actually, the sourceforge blockchain is only to block 170k.  If you're already within 10k blocks of finished then there's no point in downloading it again.

All you have to do is exit, update to 0.6.2, then fire it up again.  It will pick up where it left off.