Help! btc never showed up in my wallet

[glennd1]

I made my first transfer of 20 btc to my new wallet qt address. However I encrypted my wallet and cannot get my passphrase right, but the btc arent even in the wallet! How do I make a new wallet and get the btc in it with the original address? the address is in the blockchain as completed. Thanks

[gbl08ma]

First of all, do not delete your wallet.dat. There's no way to "create another wallet with the original address" without knowing the private key for that address, which is encrypted inside wallet.dat at the moment.

You better keep on trying to guess the password to the old wallet. I think there are some recovery tools around which help in case you remember part of the password.

[Stephen Gornick]

I encrypted my wallet and cannot get my passphrase right,

Here's another person that ended up in that scenario, though was able to eventually get it figured out:

He had indeed mistyped the password, but I cracked it.. 52 char pwds are not always good, easy to mistype =)

 - http://bitcointalk.org/index.php?topic=85495.0

[dooferorg]

I made my first transfer of 20 btc to my new wallet qt address. However I encrypted my wallet and cannot get my passphrase right

LOL!!!

*cough* .. oh man, you made my day

LOL!!!!

Try and online wallet next time and store your password somewhere private. At least online sites have password recover tools if you're .. you know, forgetful.

[CJGoodings]

Jesus, that blows, shouldnt be using passphrase systems when you cant remember the phrase's you used.

[vphen]

you better try to guess your password

[gbl08ma]

At least online sites have password recover tools if you're .. you know, forgetful.

I'd stay away from an online wallet that provides password recovery options. blockchain.info doesn't allow this (it only allows for optional password hints), and any wallet that allows for password recovery/replacement (when not logged in) doesn't encrypt the wallet client-side (because there's no way to provide recovery options while still encrypting client-side), which is bad.