Lot of people are having the same problem since BCH comes to life, at end you had the privatekey from the addy, so no problem at all, you only have to import that privatekey to a BCH wallet and you will have access to the money. Now imagine if you get that deposit on a exchanger or a casino, damn, there is where the problems start, could take lot of days for the business to fix it.
That's why we mus be really careful with those transactions, other way we can risk and sometimes lose money.
Topic: BTC address given, but BCH funds sent (Read 255 times)
I save that in a text file, encrypt it with gpg, then shred the original text file.
Why don't you use BIP38 instead of gpg? I use both sometimes: a gpg encrypted private key in offline storage, and a BIP38 encrypted paper wallet with the same private key and a different password as a backup. 
What BTC wallet are you using? That is the originating wallet?
WIF private keys contain information about whether the compressed address should be used or the uncompressed one. Most likely the problem is that you've encoded the WIF private key for the wrong type of address. So I suggest converting to the other type and importing that.
FYI uncompressed private keys begin with 5 and compressed ones begin with L or K. You can convert between the two using bitaddress.org's wallet details tab (run offline).
WIF private keys contain information about whether the compressed address should be used or the uncompressed one. Most likely the problem is that you've encoded the WIF private key for the wrong type of address. So I suggest converting to the other type and importing that.
FYI uncompressed private keys begin with 5 and compressed ones begin with L or K. You can convert between the two using bitaddress.org's wallet details tab (run offline).
Thank you for the explanation.
I don't use any BTC wallet. Whenever I need a new address, I just generate a random number in Python by:
Quote
priv = os.urandom(32)
then apply the necessary steps to generate the corresponding Public Key and Address. I save that in a text file, encrypt it with gpg, then shred the original text file.
So normally I don't need to use the WIF at all. No mnemonic word lists either. Just good old private key.
I know it's a bit primitive but I like it that way :-)
I also wrote a python script to convert the Private Key to WIF:
Quote
import hashlib
import base58
import binascii
def privateKeyToWIF(key):
versionByte = "80"
extendedKey = versionByte + key
extendedKey_bytes = binascii.unhexlify(extendedKey)
doubleSHA256 = hashlib.sha256(hashlib.sha256(extendedKey_bytes).digest()).hexdigest()
checksum = doubleSHA256[:8]
finalKey = extendedKey + checksum
WIF = base58.b58encode(binascii.unhexlify(finalKey))
return WIF
import base58
import binascii
def privateKeyToWIF(key):
versionByte = "80"
extendedKey = versionByte + key
extendedKey_bytes = binascii.unhexlify(extendedKey)
doubleSHA256 = hashlib.sha256(hashlib.sha256(extendedKey_bytes).digest()).hexdigest()
checksum = doubleSHA256[:8]
finalKey = extendedKey + checksum
WIF = base58.b58encode(binascii.unhexlify(finalKey))
return WIF
I wasn't sure that's working properly, and following you message I verified it does, with bitaddress.org results.
Your steps should be right, so IMO there's an issue with BTC.com wallet.
Thanks. I tried it now with Electron Cash - successfully imported in seconds.
Naturally I have the private key for the BTC address.
Trying to solve that, I set up a BCH wallet (using BTC.com), converted the private key to WIF format, then tried to use the wallet's import / recovery feature with the WIF key.
The wallet does indeed recognize the WIF key as valid but returns "No positive balances were found".
Trying to solve that, I set up a BCH wallet (using BTC.com), converted the private key to WIF format, then tried to use the wallet's import / recovery feature with the WIF key.
The wallet does indeed recognize the WIF key as valid but returns "No positive balances were found".
What BTC wallet are you using? That is the originating wallet?
WIF private keys contain information about whether the compressed address should be used or the uncompressed one. Most likely the problem is that you've encoded the WIF private key for the wrong type of address. So I suggest converting to the other type and importing that.
FYI uncompressed private keys begin with 5 and compressed ones begin with L or K. You can convert between the two using bitaddress.org's wallet details tab (run offline).
- Do BTC and BCH private keys do indeed translate to the same Address?
Yes and No, because :
1. BTC and BCH use older/legacy address format (starting with 1 and 3)
2. BTC and BCH now have their own new address format (starting with bc1 and q...)
But since blockchair shows both coins (meaning you use older/legacy address format), the answer is Yes in your case.
- If so, is there a better way to swipe / import / recover the funds from a BCH private key?
No idea, i only can suggest use another wallet such as Electron Cash, Bitcoin ABC or Bitcoin Unlimited.
- Am I getting it completely wrong, or is the above just an issue with the specific wallet(BTC.com)?
Your steps should be right, so IMO there's an issue with BTC.com wallet.
P.S. if you don't mind post that address, that would make identifying process easier.
I didn't mention:
When I check the address in blockchair.com, and select the BCH one (the address shows both on BTC and BCH blockchains), it shows my address in "Legacy Address Format". Then there's also a "Cash address format".
When I check the address in blockchair.com, and select the BCH one (the address shows both on BTC and BCH blockchains), it shows my address in "Legacy Address Format". Then there's also a "Cash address format".
I gave someone a BTC address to receive a payment.
That person took my address, but mistakenly sent BCH (genius!)
Somehow the transaction went through. Now that BCH address shows the funds. I can see the transaction on the BCH blockchain.
Naturally I have the private key for the BTC address.
Trying to solve that, I set up a BCH wallet (using BTC.com), converted the private key to WIF format, then tried to use the wallet's import / recovery feature with the WIF key.
The wallet does indeed recognize the WIF key as valid but returns "No positive balances were found".
My questions:
- Do BTC and BCH private keys do indeed translate to the same Address?
- If so, is there a better way to swipe / import / recover the funds from a BCH private key?
- Am I getting it completely wrong, or is the above just an issue with the specific wallet(BTC.com)?
A bit more background: for BTC, I normally don't use any third party wallet. I generate the private key locally with a Python script, then do the necessary steps to move to Public Key and Address. I also used Python to move to WIF format.
It's not a huge sum but still irritating.
That person took my address, but mistakenly sent BCH (genius!)
Somehow the transaction went through. Now that BCH address shows the funds. I can see the transaction on the BCH blockchain.
Naturally I have the private key for the BTC address.
Trying to solve that, I set up a BCH wallet (using BTC.com), converted the private key to WIF format, then tried to use the wallet's import / recovery feature with the WIF key.
The wallet does indeed recognize the WIF key as valid but returns "No positive balances were found".
My questions:
- Do BTC and BCH private keys do indeed translate to the same Address?
- If so, is there a better way to swipe / import / recover the funds from a BCH private key?
- Am I getting it completely wrong, or is the above just an issue with the specific wallet(BTC.com)?
A bit more background: for BTC, I normally don't use any third party wallet. I generate the private key locally with a Python script, then do the necessary steps to move to Public Key and Address. I also used Python to move to WIF format.
It's not a huge sum but still irritating.
Jump to: