 Show Posts
|
|
Pages: [1]
|
Well, I did my best, I stopped trying a long time ago. It's basically just a file for me at this point. If people say they can crack it in half an hour, okay, no problem, but I'm not going to click any links or send anything up front.
You can totally do this on your own, Just read these instructions[ https://btcrecover.readthedocs.io/en/latest/TUTORIAL/#installation] for btcrecover carefully. First, create your own list of passwords in a text file. You only need to test 365 keys for one year, and only 365 x 50 for fifty years. Then, change those passwords to different formats, like DDMMYYYY, DDMMYY, DD/MM/YYYY, DD-MM-YYYY or other format, and repeat the process. I can help you create those password lists in a text file or guide you step-by-step. Don't worry, there won't be any links to click on, and you won't need to send me anything upfront. Contact me up on Telegram at @Panadawn |
|
|
|
Unfortunately, I don’t have the python script you referenced. If you can, please send me the link. Thanks.
I can create it for you, but I need to known where the wrong position is. For example, 5JXB[]hvvfQaT7GxoN7BGicZST25uGhLJ5aK9y3SS3LL[]766tfaS, the wrong position is '5' and '44' I don't check this site often, Can you contact me in telegram? [Telegram: @Panadawn] |
|
|
|
I assume the last seven characters on a private key is based on checksum then the search would have been 3*58.
I tried it on FinderOuter but the search is 3*58*58*58*58*58*58*58*58.
Ie 3=first character after 5.
Than 58 for one invalid character.
Then last seven characters for checksum ( 58 x 7 ).
Had FinderOuter provisions for elimination of checksum and calculated only the main characters then the search for valid key would have been very simple.
1. Checksum part for WIF private key starting with '5' is only last 5 character (Not 7) 2. If you assured that there are 2 Char wrong, So all possible valid key that can generated is only 3x58. ( = 174 key) 3. After convert those key to P2PKH address (BTC address starting with '1'),You can check all of that 174 address if it have balance or not. (It takes less than 1 minute in bitcoin blockchain inquiry API) All the above processes can be done with one python script |
|
|
|
It starts with 5 but the second character is ‘F’ followed by other characters with two invalid Base 58 characters and checksum error which makes me understand that last four characters are not correct.
The one charecter that does’nt fit the Base58 chart is ‘I’.
Perhaps the format of the key is not Base58. The knowledge of wallet creation may not have been widespread in 2010, so methods for generating private keys may differ, You should try to decode your key with another format ex Base64, Base62 |
|
|
|
This python script below can create new valid checksum, It probably won't help much. But you should at least give it a try. import base58
key = '5JLUSIY1ap3diK5PP2PIuAtdhyHKqyPTDzccqlHfiMcCGd5s8LM' #change this key to your private key
x = key.replace('I', 'i')
y = x.replace('l', 'L')
bytekey = base58.b58decode(y[0:46] + 'z'*5)[:33]
print(str(base58.b58encode_check(bytekey), 'utf-8'))
I can create the code that specific on your case, but I need more information [ex. how many 'I' and 'l' in your key and Where is it located?]. May be a months or a years, If you tried every possible way but still can't find the valid key, contact me at telegram or email on my profile. |
|
|
|
I lost my priv keys few years back and recently found while going through old lap top
Did you find it in an original email or it was in the text file you created? If you find it in an original email, it's high likely that it's a scam because it's wrong from the beginning. but if it in the text file you created, The mistake might be that you recorded it incorrectly, for example You may alternate lowercase letters with uppercase letters. (Base58 is case sensitive), The more mistakes you make,the more time it takes to find. It may take an hours to find valid key in 3 letters wrong. But for 4 letters wrong, It may take months or even years to find the valid key [Run on one simple CPU 24hr/day] In this case, I think the first thing to do is you should try to find the private key form your original email. |
|
|
|
How did you find your private key? Did you find it in an old email? or Was it handwritten? if it's handwriting You might write it down wrong at some point. The private key that starts with '5' and has total 51 Char is Uncompressed WIF private key pattern. This type of key always has a checksum in the last position to check that all characters of the key are correct. When you try to import the key and got 'Invalid private key', It may be caused by having some characters wrong. If you write it down no more than 3 character wrong. you can recover it with this python script below. import base58
import itertools
Damage_key = '5Kax3UAwGmHHuj6fQD1LDmKR6J3SwYyFWyHgxKAZ2cKRzVCRETY' #change this key to your private key
Pos_3_change = list(itertools.combinations(range(1,51),3))
Base58_3_change = list(itertools.product('123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz', repeat=3))
def key_recovery():
for a in Pos_3_change:
for b in Base58_3_change:
private_key = list(Damage_key)
private_key[a[0]] = b[0]
private_key[a[1]] = b[1]
private_key[a[2]] = b[2]
try:
base58.b58decode_check(''.join(private_key))
print(''.join(private_key))
except:
pass
print('complete...')
key_recovery()
You can adjust the code above to suit your case. Hope this help. |
|
|
|
|
