This was back in 2010 when everything was non standard. He likely used cli tools to generate the key. Is it possible that they may be custom encoded?

I don't know how to attach an image here.

I’m helping a friend recover Bitcoin from an old wallet dating back to 2010. The laptop is long gone, but luckily there’s a printed sheet with the following details:

1 Bitcoin address (confirmed to hold BTC)
1 public key (same in all entries)
3 different private key-looking strings
One is 32 characters, starts with HDr…
Two are 64 characters, start with oUC… and MHC…
3 different rmd160 hashes (possibly compressed vs uncompressed?)

All the public key and address fields are identical across the entries, which suggests these private keys might be different encodings or formats of the same key,  maybe raw hex, WIF, or Base58. This was common in early wallets or custom scripts that didn’t follow today’s standards.

Questions:
   1. Could these be the same private key in different formats (e.g., hex, WIF, Base58)?
   2. What’s the best way to decode and test which key is valid for the address?
   3. Can Electrum or another tool help me test them safely offline?

Any guidance or recommended tools would be hugely appreciate.  I’m happy to share more details privately if needed.

Thanks in advance!

I’m helping a friend recover Bitcoin from an old wallet dating back to 2010. The laptop is long gone, but luckily there’s a printed sheet with the following details:

1 Bitcoin address (confirmed to hold BTC)
1 public key (same in all entries)
3 different private key-looking strings
One is 32 characters, starts with HDr…
Two are 64 characters, start with oUC… and MHC…
3 different rmd160 hashes (possibly compressed vs uncompressed?)

All the public key and address fields are identical across the entries, which suggests these private keys might be different encodings or formats of the same key,  maybe raw hex, WIF, or Base58. This was common in early wallets or custom scripts that didn’t follow today’s standards.

Questions:
   1. Could these be the same private key in different formats (e.g., hex, WIF, Base58)?
   2. What’s the best way to decode and test which key is valid for the address?
   3. Can Electrum or another tool help me test them safely offline?

Any guidance or recommended tools would be hugely appreciate.  I’m happy to share more details privately if needed.

Thanks in advance!

Hello everyone, I first used armory in 2021 to store my bitcoin and never used it again. I decided to open it today, but it does not connect. I proceeded to export my keys but It doesn't show the keys for P2SH-P2WPKH address in offline mode. Why have this feature??? I read I can force armory to enable segwit in offline but I don't know how, please I need help, thanks.

Please I have a problem with Armory. It no longer connects online and when I open it offline, I can't export my key, iT SHOWS NONE, because it does not recognize P2SH-P2WPKH address in offline mode. How can I get armory to open segwit in offline mode, so I can export my key???

Hello, please I need some assistance. In 2016, we used python to generate a Bitcoin private key and then imported the key into the electrum Android app, sent btc there and forgot about it. Now, for the past one year, I have been trying to recover that address but the private key doesn’t generate the same address anymore. I have used python to generate 5 different legacy addresses but all are different from the very first one.

I am very sure it’s the right key because there are multiple backups. Is it possible that the address format is no longer supported and hence difficult to recreate with modern tools? Does anyone have any insight into this and what may be the possible problem???


To reiterate, the addresses are legacy addresses and the key I have is presumably a compressed key starting with L.

Is it possible that electrum android app uses a different architecture to generate a public address now or it had a bug that generated a wrong address for then?

Hello, please I need some assistance. In 2016, we used python to generate a Bitcoin private key and then imported the key into the electrum Android app, sent btc there and forgot about it. Now, for the past one year, I have been trying to recover that address but the private key doesn’t generate the same address anymore. I have used python to generate 5 different legacy addresses but all are different from the very first one.

I am very sure it’s the right key because there are multiple backups. Is it possible that the address format is no longer supported and hence difficult to recreate with modern tools? Does anyone have any insight into this and what may be the possible problem???


To reiterate, the addresses are legacy addresses and the key I have is presumably a compressed key starting with L.

Is it possible that electrum android app uses a different architecture to generate a public address now or it had a bug that generated a wrong address for then?

you need these three things for recovery User key- Seed and Public key. Shared key- Seed (encrypted) and Public key. Coinbase key- Public key.

Your best bet is iancoleman. you have to tweak the paths till you're able to find the missing address.'

Remember that you'll need to split the bsv from bch as they did not enable replay protection after the fork. You may also have other form coins to claim as well.

Sorry to hijack but can anyone help with spending a transaction from a time lock address???

I accidentally made the time lock 7140000 instead of 714000 and that means I have to wait 120 years to spend the coins. Please can anyone help?

Sorry to hijack but can anyone help with spending a transaction from a time lock address???

I accidentally made the time lock 7140000 instead of 714000 and that means I have to wait 120 years to spend the coins. Please can anyone help?

It's Already spent, I guess you figured it out.

is the offer still up, I may have a solution.

Yes, you can use it offline..

It seems like Electrum is treating each 'client id' as a change path. Your best bet may be to use the seed to manually recover the coins using iancoleman.

t

The screenshot makes it easier then, you can do this;

1. Go to electrum, in the derivation path, tick legacy and put m/clientid (m/489) underneath or

2. Use iancoleman.io/bip39 listed above(beware, using this may compromise your seed)


put the seed in the mnemonic box and change the derivation path to bip32, select custom path and put m/client id (m/489).

use m/44'/0'/client id', try that first and see if you'd get the address.

is the bounty still up?

Seems like it has already been redeemed.