 Show Posts
|
|
Pages: [1]
|
Can you share the public key and then the characters of your WIF which you have?
DO NOT share such information with anyone here or in your personal message. - Jay - Are you talking to me or advising others against me? Lol, even if OP shared both public key and the remaining of the WIF characters, nobody could solve the key in a few thousand years, a 256 bit private key is not something we could simply brute force. I don't know if there is a public key, but this seems more like a sold wallet case where the buyer thinks he can get help from here to find his fortune. No public key/ address, means there is something wrong with this case. i have shared examples of the public key and the remaining WIF Characters , not the real one , i am aware that this sensitive information can't be shared with anyone . well , it's not a sold fake hex edited wallet or something like this , it's my own wallet from 2011 / 2012 nothing wrong with the case , i have been reading through Secp256k1 in the past few years and i know that it's impossible to bruteforce a 256bit private key , but in my case i have some bits missing from the end of the wif , it's not easy as i know because the checksum is missing too , so i was thinking that i can try ( even if it's not possible ) to do it through the same entropy that was core using in 2011 / 2012 . at least i know the start range of my old private key . i have tried to write some simple python codes that using the random module , but the problem is the random here is repeated and i need something to be done that makes the code saves the work from the last point and start from it , i guess diving in the ocean through public keys will not lead me to anything . i think that the randomness logic that bitcoin core was using can be found in the Key.cpp in the core source code , but i don't have such knowledge to implement it through python . so i need a little helping hand to arrange things together , maybe i know something but it's scrambled in my head so i don't know the right ordering of it . |
|
|
|
What do you mean you have the device entropy details?
When generating a private key, your computer collects entropy from various sources. Mouse movements, network activity, thermal noise etc. You can't just redo the process and expect to get the same entropy, because the entropy is dependent on beyond RAM and probably other hardware info. In fact, I think that preventing the recovery of an entropy is what the Cryptographically Secure Random Number Generator is trying to accomplish in the first place, for if it wasn't, other programs could work out your private keys.
i want to just try it , even if i fails , i have been already in this for few years . |
|
|
|
No, even if you have the same specs as your old specs when you generated this WIF key it's still impossible to recover the missing 21 characters it would take decades to brute force these missing characters.
I think you were thinking that you can generate the same WIF key by having the same entropy that is impossible never heard someone succeed in doing this even me I tried that thing past year's ago without success, I just want to recover my old private key due to backup corruption but no it doesn't work.
Be careful on the post below that asks for public addresses and the WIF key with missing characters.
i want to just try it , even if it fails i am not willing to share any of my private info with anyone , i am aware of this . |
|
|
|
i have opened a topic here in the past year asking if i could recover my missing wif characters https://bitcointalk.org/index.php?topic=5407589.0Since i was trying to recover my 21 Wif missing character over the past few years with No Luck i was so disappointed , yes i know that 21 characters is too much , too much bits missing to be bruteforced . i have a question but due my lack of knowledge i need some help . could i use my exact device entropy details that was used to generate the private key through bitcoin core in 2011 or 2012 i have my exact old computer specs and the exact ram memory that was used and other important info . if this possible i want a python code or something using this entropy details i could try to hope to find a collision to my address or the change addresses in my wallet at that time . any help will be appreciated too much  |
|
|
|
i have both uncompressed and compressed
Your BTC address, was it created as compressed or uncompressed? i have both compressed and uncompressed created addresses . |
|
|
|
If it is uncompressed key, it complicates thing, as we cannot calcululate "the path" for additions. If we would have compressed key, we may base on compression flag encoded in WIF, to find what should be the starting points for Kanagaroo ranges. With uncompressed, it is much more complicated, as we do not know how to find stride (and from which key) to calculate keys which would not impact last bytes of decoded WIF.
i have both uncompressed and compressed how can do it in the compressed public key that is starting with 02 ( even ) or 03 ( odd ) ?? any info. and help needed please |
|
|
|
The problem with your WIF is that stride collides with checksum and you may have improperly calculated private keys, tomorrow I will launch my calculator to see how to solve it, usually it may be solved by launching several works with a different starting points. Just confirm how many characters you know l, from the gap to the end.
well , it seems like i had no luck in my recovery process because my characters is more than 21 and the searching range is so big , is there is any other thing i can do , like lattice attack on my outgoing txns , or something . i have the public key which computes right to my address , and have everything except for the private key . Any Help will be appreciated , i am out of luck as you see and hope that i can find something . also i did not ever shared my wallet with anyone , so no one have it except me ( the owner ) . |
|
|
|
No, that’s not correct. I mean, it is, technically, but it is not the best way to solve WIF problem. You know that you look for a private keys with a given stride, which is “58^number of known characters to the end”, in your case 58^15.
Thank you very much , i will try to prepare the necessary configurations and will try to solve it . can the ckeys in the wallet.dat files cracked through the master key , i saw something like this before but i can't remember what it was . |
|
|
|
5HpHagT65TZzG1P*********************EB3kEsreAnchuDf
it is not the best example, because you used WIF from private key=1. Normally you calculate range as follows: replace unknown characters by "1", decode, it will be your starting range. Then add 58^unknown characters (in your case 21?), if you add to starting range you will have the end range for search. how can i add the 58^21 to my start range ? - is there is some useful methods to try to recover my wallet instead of bitcrack ?
Yes, that's what we try to do with Kangaroo - if the bitcoin address contains 0.054 BTC , will it be a 54 bit 2^54 ? ( sorry if it's a dump question , but i have limited knowledge ) .
No, it has nothing in common. - can i split the range that i will be searching for into 2 parts , for example let's say that i will search for a specific range for 7 days , how can i split this search into 2 devices ?
doable. how can this be done i a short explanation ? i have replaced the unknown characters by 1 and got the start range , then i replaced again with z and got the end range , is that right ? how can i add 58^21 into my starting range ? |
|
|
|
Now i have another thing despite from the wif damaged
i got the dumped wallet and it contains a secret
can i recover my wallet throght the secret ?
I'm going to assume the wallet is a Bitcoin Core wallet. It is only possible if the wallet is not encrypted, or if the wallet is encrypted but you remember the password. If the wallet is encrypted it's probably more (theoretically) faster to just brute-force the WIF. i have seen before that the ckeys of the wallet can be cracked by some software , but i don't remember exactly what it is . |
|
|
|
i have tried BSGS and Pollard Kangaroo with no success , it takes like forever
Could you write what are positions of missing characters? At the end, at the beginning, in the middle? Is it one group or there are several groups? If it is one group and as you seem to have public key (is it indeed correct?), it should be doable with Kangaroo in a very reasonable time. Ok , i will give you an exact example of the positions of missing character this is just a WIF as an example 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf The Missing Characters ( Replaced By * ) Are as Follows : 5HpHagT65TZzG1P*********************EB3kEsreAnchuDf I Have converted my public key to an address and the output is the Address of my wallet , ( My wallet has no outgoing Transactions ) , so i got the public key from the info of the wallet that i found earlier in the txt file . I have some questions and i hope that you can give me a good explanation or some help if you can - can i determine what is the range of the bitcoin address to search for it in a specific range , i know that the range could be determined in Privatekeys but i am just wondering if something like this exists . - is there is some useful methods to try to recover my wallet instead of bitcrack ? - if the bitcoin address contains 0.054 BTC , will it be a 54 bit 2^54 ? ( sorry if it's a dump question , but i have limited knowledge ) . - can i split the range that i will be searching for into 2 parts , for example let's say that i will search for a specific range for 7 days , how can i split this search into 2 devices ? |
|
|
|
Now i have another thing despite from the wif damaged
i got the dumped wallet and it contains a secret
can i recover my wallet throght the secret ?
I'm going to assume the wallet is a Bitcoin Core wallet. It is only possible if the wallet is not encrypted, or if the wallet is encrypted but you remember the password. If the wallet is encrypted it's probably more (theoretically) faster to just brute-force the WIF. yes you 're right , but the wif brute forcing will take too much time due to it's more than 19 missing characters at known positions . i have tried BSGS and Pollard Kangaroo with no success , it takes like forever i have tried also Wif-Solver Cuda and Calculated the stride & Range which is too big and after running it for few hours it still at 0.000 % . so i ran out of ideas  |
|
|
|
You need to be more specific without disclosing sensitive information of your wallet like private keys and such.
What kind of wallet is this?
What kind of dump of the wallet do you have?
If it is a Bitcoin Core HD wallet and you see as "secret" the private key that is used as seed for the HD wallet, then I think it should be possible to recreate your wallet's keys with that.
If you have a Bitcoin Core wallet dump with lots of private keys in the dump then you can import those private keys e.g. in an Electrum wallet (in my opinion the import is easier with Electrum than with Bitcoin Core itself) and see if you find any of your coins.
It's quite some time ago that I did some experiments to recover a Bitcoin Core HD wallet by using the dumped HD key from the donor wallet dump, but I don't remember the results unfortunately, sorry. Only I remember is that I had some trouble, but that might have been due to lack of knowledge with proper command usage for Bitcoin Core console or bitcoin-cli.
to be more specific with you it's not a wallet dump , my few wallets was lost in and the HDD is damaged , however those are some of the backups in text format i made before in my 2nd HDD . the format in the txt files follows this : "addr": " My Bitcoin Address " "compressed": false, "encrypted_privkey": " Privatekey " "hexsec": " dfgdfgfdffhfg" ex. "label": "", "pubkey": Pubkey ex: "0000000046556641541" "reserve": 0, "sec" "secret": " Contains a secret hash All those Values are given so i have the enc_privkey , hexsec , pubkey , sec ( which is a full privatekey but it refers to another empty wallet address ) , and finally the secret . Any Help will be appreciated |
|
|
|
hello there i have my own bitcoin address and public key and a WIF recognized as invalid this txt file was old and recovered from my old HDD i assume that the wif has more than 19 missing characters at known positions is there is any chances that i can recover it ?? any guiding help will be appreciated First at all: 19 is a lot. How did it happen? What do you have? Text file? How are you sure the rest of characters are correctly recovered? Do you miss beginning or end? If there would be less characters, but maybe randomly distributed, I would say my WifSolver could help: https://github.com/PawelGorny/WifSolverBecause you have many characters missing, if you lost the beginning you may use much faster version, build for GPU: https://github.com/PawelGorny/WifSolverCudaThat program would not work if you have your characters missing at the end. Then you should try to convert problem into simple brute-force tool like BitCrack. There is also 4th option. If you know public key (address has outgoing transaction) we may use Kangaroo, normal or modified for solving WIFs ( https://github.com/PawelGorny/Kangaroo) Let me know if you need hep with any of tools, we will try to find the best approach. But honestly speaking, as you sad you are sure 19 characters are missing, the only chance to restore it in reasonable time is to have public key and attack with Kangaroo. Thank you really for helping out Now i have another thing despite from the wif damaged i got the dumped wallet and it contains a secret can i recover my wallet throght the secret ? |
|
|
|
19 characters gone/lost already? Sorry, you will not be able to recover the WIF private key.
Alright , thank you i thought that too what is the maximum WIF missing characters that can be recovered ? |
|
|
|
hello there i have my own bitcoin address and public key and a WIF recognized as invalid this txt file was old and recovered from my old HDD i assume that the wif has more than 19 missing characters at known positions is there is any chances that i can recover it ?? any guiding help will be appreciated |
|
|
|
|
