|
Blockchain.info has been known to have this bug for a long time.
It doesn't check the checksums and lengths of the WIF keys entered and that's quite a big problem.
The bug is hard to reproduce outside of BCI, so my suggestion would be creating a new wallet (remember the usual security precautions, and since that key has already seen BCI, it can be considered compromised), importing the troubled WIF key and exporting it back (I've tried that with an intentionally-corrupted key and it appears to work).
|
|
|
|
|
Virtually no online wallets existed back then, so are you sure you stored your coins online?
You can try searching the hard drives for files named "wallet.dat", since it's most likely that you have used Bitcoin Core back then.
|
|
|
|
|
DarkStar_ is right, you have some balance on the forked chains (you can sell them off too!)
|
|
|
|
|
AFAIK, a wallet from 2010 can't contain any xpub / xprv keys, because they weren't introduced back then.
|
|
|
|
Maybe it's a ledger problem?
I don't think it is a Ledger problem as the LTC worked fine and shows up.
Why not import your seed into another wallet client and see if your bit coin shows up?
This is an option I may have to consider by purchasing a new one!
Or you could run Ian Coleman's tool and tweak the derivation path to search for the address.
When you say 'tweak' the derivation path - I would I do this? Try choosing "Derivation Path" -> "BIP141" -> "P2WPKH nested in P2SH". |
|
|
|
Do you have your 24-word seed that your Ledger made you write down?
Hi SopaXT - Yes I do have my 24-word seed written down from my Ledger. What do you suggest? A Ledger reset/reconfiguration? Any help and assistance would be great appreciated. Try resetting and re-initializing your Ledger from that seed (however, as you seem to have a lot of BTC, I'd recommend getting a new one for that instead of resetting the old one, just in case). Also, do you remember what account did you generate that address from (it's possible that you're just using a different one)? e.g. "Accounts > My Account", etc? Does it say the same right now? |
|
|
|
|
Do you have your 24-word seed that your Ledger made you write down?
|
|
|
|
|
Do you have your 24 words (that were given to you when you first turned your Ledger on) written down?
If that is the case, then you have nothing to worry about when resetting your wallet, as all of your addresses are generated from that (you might need to create a new LTC account afterwards, though).
It's highly unlikely that you'll need to reset it, though.
Are you sure that you're using the correct BTC account (there can be multiple accounts with multiple addresses generated from them, all from a single seed)?
Does the address ever show up in your wallet right now?
Also, it's possible that you're using the old Litecoin address format (do your Litecoin addresses start with an M or a 3?).
If you have sent Bitcoin to a Litecoin SegWit address, it's still possible to recover that (although rather quirky).
|
|
|
|
|
The "public key" and "private key" are proper cryptographical names.
However, addresses are often confused with public keys. An address is actually a hash of the public key, normally Base58-encoded.
|
|
|
|
|
First of all, do you have them in order (first, second, third...)?
If yes, then the problem lies in simply brute-forcing the 3 words, which is about 8 billion tries.
This number may look scary, but in fact it's doable even on an average PC in a few days at most.
How exactly did you lose the last words?
If you still have some parts of them left, this will make the brute-forcing process easier by several orders of magnitude.
|
|
|
|
|
Your SegWit-supporting wallet can make a SegWit transaction afterwards, and the fee for that is going to be lower.
|
|
|
|
Hi, I have used for my Address to start with D - DKo6y9Cfuwu8imVUz2MWbAeYXHtmgYkFFF the wallet that I use to verify the address confirm that the address is a valid address. What should I replace with in order for my Private key (WIF key) to start with the capital letter Q - the wallet return an invalid private key message Tnx, H. If you're developing an altcoin, asking this is unacceptable - you should know better! The correct private key version is probably , according to the source code (address version + 128). |
|
|
|
|
Tools such as btcrecover (to brute-force your wallet password) support raw encrypted keys such as yours.
Do you remember what the password could be?
|
|
|
|
|
It's a wallet.dat dump, such as that created by pywallet.
It can be used to recover the wallet file, but I'd also recommend looking for the original wallet.dat.
|
|
|
|
|
On other threads here, it's suggested to run Bitcoin Core with the -upgradewallet option.
Seems like that it needs help to understand the old wallet formats now.
Also, running an old version won't help - it isn't going to synchronize with the network.
|
|
|
|
Hi all,
I saw an older post and someone had the same problem like mine. Basically I set up a paper wallet and wrote down the private key, now I've missed out a character I used bitaddress.org. Private Key WIF Compressed 52 characters base58, my key starts with a K. Now I thought that I only missed out a character, but I ran a script and got 3162 combinations that gave an extra character inputted them into blockchain and none worked.
So now I am missing a character and somewhere along the line I have made a very small error (that could be accidentally making one of letters caps instead of noncap, looking at my key there could be maximum possibility of 6 characters that could be noncap or cap that is worst case scenario) I'm pretty sure that 90% of this key is correct as I skimmed through it after writing it down also my bitcoin address is correct. If there is a way of working out the key based on my partial private key and my bitcoin address that would be great. I want to try another 3162 combinations is there a way of automatically checking these keys instead of copying and pasting into blockchain? If the key is found a reward will be given. Thanks for the help.
Do you have a QR code printed on your paper wallet or did you write it down manually? This tool can help finding the typo in the key automatically: https://github.com/hexafraction/wif-repair. |
|
|
|
|
You can try installing Bitcoin Core and copying the wallet.dat file into your AppData\Roaming\Bitcoin directory (if you're on Windows).
You'll probably need to sync the client (which requires downloading 100 GB of data), and then you'll be able to access your coins.
|
|
|
|
|
Are you sure that it's not an altcoin wallet?
|
|
|
|
|
Show Posts
