Bitcoin Forum
May 13, 2024, 02:36:21 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How to properly validate a BIP38 paper wallet?  (Read 206 times)
orangepeel (OP)
Newbie
*
Offline Offline

Activity: 4
Merit: 7


View Profile
February 01, 2018, 11:15:22 AM
Merited by OmegaStarScream (2), DannyHamilton (2), achow101 (2), LoyceV (1)
 #1

The process of creating and validating a BIP38 wallet is still confusing to me.

So I go to bitaddress.org and generate a BIP38 encrypted wallet. This is all done offline via ubuntu usb drive.

Now I have the BIP38 public and private keys. So I print these.

In order to validate this wallet is functioning correctly, I use bitaddress.org's "wallet info" tab and enter the encrypted (6P...) private key on my paper wallet and passphrase.

Success. It opens a bunch of different addresses; the important ones I'm guessing are "Bitcoin Address" and "Bitcoin Address Compressed"

Also, "Private Key WIF 51 characters base58, starts with a '5'" and "Private Key WIF Compressed 52 characters base58, starts with a 'K' or 'L'".

I was under the impression that the "Bitcoin Address" was supposed to match the public key on my physical paper wallet, which goes along with the "Private Key WIF 51 characters base58, starts with a '5'".

However, I notice my physical paper wallets public address does not match the displayed "Bitcoin Address" from the "wallet info" tab. Instead the "Bitcoin Address Compressed" matches.

So if I were importing and sweeping this wallet onto a hot wallet, would I use the "Encrypted Private Key (6p...)" as seen on my physical paper wallet or the "Private Key WIF 51 characters base58, starts with a '5'" or "Private Key WIF Compressed 52 characters base58, starts with a 'K' or 'L displayed in the "wallet info" tab?

Furthermore, is opening the wallet under "wallet details" on bitaddress.org (offline) using the encrypted private key on my paper wallet and passphrase, and seeing the matching "Bitcoin Address Compressed" to the physical paperwallet's public key in my hand, enough to verify the wallet is functioning correct and to begin sending funds to?
1715610981
Hero Member
*
Offline Offline

Posts: 1715610981

View Profile Personal Message (Offline)

Ignore
1715610981
Reply with quote  #2

1715610981
Report to moderator
1715610981
Hero Member
*
Offline Offline

Posts: 1715610981

View Profile Personal Message (Offline)

Ignore
1715610981
Reply with quote  #2

1715610981
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715610981
Hero Member
*
Offline Offline

Posts: 1715610981

View Profile Personal Message (Offline)

Ignore
1715610981
Reply with quote  #2

1715610981
Report to moderator
1715610981
Hero Member
*
Offline Offline

Posts: 1715610981

View Profile Personal Message (Offline)

Ignore
1715610981
Reply with quote  #2

1715610981
Report to moderator
LoyceV
Legendary
*
Online Online

Activity: 3304
Merit: 16655


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
February 01, 2018, 12:33:01 PM
Merited by DannyHamilton (2), HCP (1)
 #2

Now I have the BIP38 public and private keys. So I print these.
Let's call them Bitcoin address and BIP38 encrypted private key. The address isn't encrypted.

Quote
In order to validate this wallet is functioning correctly, I use bitaddress.org's "wallet info" tab and enter the encrypted (6P...) private key on my paper wallet and passphrase.
All good so far!

Quote
Success. It opens a bunch of different addresses; the important ones I'm guessing are "Bitcoin Address" and "Bitcoin Address Compressed"
I suggest to only use the Compressed address, which is what bitaddress.org uses by default.

Quote
Also, "Private Key WIF 51 characters base58, starts with a '5'" and "Private Key WIF Compressed 52 characters base58, starts with a 'K' or 'L'".
You'll only need the Private Key WIF Compressed to use your funds from the compressed address.

Quote
I was under the impression that the "Bitcoin Address" was supposed to match the public key on my physical paper wallet, which goes along with the "Private Key WIF 51 characters base58, starts with a '5'".

However, I notice my physical paper wallets public address does not match the displayed "Bitcoin Address" from the "wallet info" tab. Instead the "Bitcoin Address Compressed" matches.
By default, it uses the compressed address. This reduces fees when you make a transaction.

Quote
So if I were importing and sweeping this wallet onto a hot wallet, would I use the "Encrypted Private Key (6p...)" as seen on my physical paper wallet
If your wallet supports it (my phone wallet Mycelium does), you can import/sweep the BIP38 encrypted key directly and enter the password in your wallet.

Quote
or the "Private Key WIF 51 characters base58, starts with a '5'" or "Private Key WIF Compressed 52 characters base58, starts with a 'K' or 'L displayed in the "wallet info" tab?
This works too. Decrypting the BIP38 private key before importing/sweeping works in almost any wallet.

Quote
Furthermore, is opening the wallet under "wallet details" on bitaddress.org (offline) using the encrypted private key on my paper wallet and passphrase, and seeing the matching "Bitcoin Address Compressed" to the physical paperwallet's public key in my hand, enough to verify the wallet is functioning correct and to begin sending funds to?
This is what I do too.
You could be even safer by using other software to decrypt the private key, so you don't rely on bitaddress only. I've used bitcoinpaperwallet.com for this, although I think it uses the same engine.

Before funding your paper wallet with high amounts, I suggest to make a small transaction first, and sweep it into a wallet to experience how it works. Fees aren't that high at the moment.
After this transaction your paper wallet can no longer be called "cold storage": create a new one.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!