Author

Topic: BIP38 encrypted paper wallets (Read 445 times)

newbie
Activity: 2
Merit: 0
August 02, 2017, 12:44:38 PM
#4
has anyone figured this out yet?
newbie
Activity: 2
Merit: 0
July 13, 2017, 02:00:31 PM
#3
I had the exact same issue last week when I accidentally sent some LTC to one of my no longer used paper wallets. I just decrypted the bip38 and imported private key to electrum wallet back in may of this year with no problem. Well, I went to do the exact same procedure and the wallet would not decrypt. Lucky me though I used the stand alone version of LTC electrum wallet and when I fired it up my private key was still there and I was able to send my coins to my ledger hardware wallet no problem. I am not sure what the issue is but I know my password but bitaddress will not let me decrypt.
full member
Activity: 129
Merit: 101
July 13, 2017, 01:46:02 PM
#2
I made some paper wallets recently using bitcoinpaperwallet.com's offline generator.  I tested decryption right after i made them and they opened just fine.  After a few days, I try to open the same one again with the same passwrod, and it says invalid passphrase.  This has happened before but I thought it was me forgetting the password.  I don't think this is the case now.  I'm wondering if anyone else has noticed this and what the solution is. This happens with both bitaddress.org and bitcoinpaperwallets.com (and makes sense as they both use the same code).

I too have some from years ago and i am fairly sure I had the correct password but no go.

Let me know if you figure it out.
newbie
Activity: 19
Merit: 0
July 13, 2017, 01:36:20 PM
#1
I made some paper wallets recently using bitcoinpaperwallet.com's offline generator.  I tested decryption right after i made them and they opened just fine.  After a few days, I try to open the same one again with the same passwrod, and it says invalid passphrase.  This has happened before but I thought it was me forgetting the password.  I don't think this is the case now.  I'm wondering if anyone else has noticed this and what the solution is. This happens with both bitaddress.org and bitcoinpaperwallets.com (and makes sense as they both use the same code).
Jump to: