Pages:
Author

Topic: My own Bitcoin WIF Missing Characters Help (Read 723 times)

legendary
Activity: 952
Merit: 1367
September 27, 2022, 04:41:35 AM
#38
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 Smiley

But do you have partial compressed WIF? As I said before, first you must find the correct starting point and using that start your search (adapting also a stride).
member
Activity: 71
Merit: 43
September 27, 2022, 02:14:34 AM
#37
you are missing 21 characters from your wif which is a lot....
as someone posted above if your address contains small amount of btc than it's simply not worth it (the costs for finding the key are higher than the wallet itself)
if the wallet balance is good maybe a pool can be created for collective search of private key (you will get your share and also the people who searched for your key)
Ofcourse the second method is a little risky (you need to find a trusty person for the pool) but it's still better than nothing.

If you try to recover the key alone chances are 100% that you will not find it even in 10 years from now.
Just my 2 cents, good luck recovering your funds
newbie
Activity: 16
Merit: 0
September 26, 2022, 10:08:20 PM
#36
i have both uncompressed and compressed

Your BTC address, was it created as compressed or uncompressed?

i have both compressed and uncompressed created addresses  .
member
Activity: 194
Merit: 67
'Bitcoin signature chain' & '1 pixel inscriptions'
September 26, 2022, 07:48:46 PM
#35
i have both uncompressed and compressed

Your BTC address, was it created as compressed or uncompressed?
newbie
Activity: 16
Merit: 0
September 26, 2022, 07:22:20 PM
#34
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 Smiley
member
Activity: 194
Merit: 67
'Bitcoin signature chain' & '1 pixel inscriptions'
September 26, 2022, 01:33:48 PM
#33
In your case it depends on the public key  Smiley

Why public key?

public key -> address -> amount of BTC

- if the bitcoin address contains 0.054 BTC , ~

if it contains 0.054 BTC --> not doable  Smiley
if it contains 5.4 BTC --> doable

|MC|bits|ETA|$|
|14|82|00:11:17|2|
|15|88|01:25:53|18|
|16|94|10:54:07|133|
|17|100|3d 11:01:37|1,016|
|18|105|26d 08:18:52|7,740|
|19|111|200 days|58,942|
legendary
Activity: 952
Merit: 1367
September 26, 2022, 06:10:16 AM
#32
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.
newbie
Activity: 16
Merit: 0
September 25, 2022, 04:42:19 PM
#31
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 ) .
full member
Activity: 204
Merit: 437
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 Smiley

The Missing Characters ( Replaced By * ) Are as Follows :
5HpHagT65TZzG1P*********************EB3kEsreAnchuDf

Assuming you manage to tweak Pollard Kangaroo (don't know if it's possible, looks kinda tricky), here are the expected run times and cost (on-demand, spot instance could be 1/3rd of the price) when using AWS GPU instance p3.8xlarge (4x V100):
MC - missing characters, bits - equivalent missing bits
|MC|bits|ETA|$|
|14|82|00:11:17|2|
|15|88|01:25:53|18|
|16|94|10:54:07|133|
|17|100|3d 11:01:37|1,016|
|18|105|26d 08:18:52|7,740|
|19|111|200 days|58,942|
|20|117|4 years 68 days|448,893|
|21|123|32 years|3,418,664|
|22|129|242 years|26,035,770|
|23|135|1849 years|198,282,544|
|24|141|14083 years|1,510,074,752|

This was using my software (not published), Jean_Luc should be faster (50%?), newer hardware should be faster as well.
legendary
Activity: 952
Merit: 1367
Keep in mind that this method is only accurate when the missing characters are all at the end since the farther away they get from the end, the bigger the range is going to be compared to the actual range of missing characters.

I know, but I have prepared a version of Kangaroo which works with given stride - just to be able to solve WIFs, preferably with missing beginning.
https://bitcointalksearch.org/topic/--5315607
legendary
Activity: 3444
Merit: 10558
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.
Keep in mind that this method is only accurate when the missing characters are all at the end since the farther away they get from the end, the bigger the range is going to be compared to the actual range of missing characters. Take the following private key for example (to simplify things I didn't remove checksum):
Code:
L2QCuJrrk5c5VrD1xEPzHVYQf3hv4UoSUejn8fZ6mKXdXCUt19vs
If the last character is replaced by 1 and then incremented by 1 (...19v1 to ...19v2) the integer values are the following:
Code:
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4059d0d081db68f0c2c740901c8f9def2
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4059d0d081db68f0c2c740901c8f9def3
The difference between these two numbers is 100% accurate and equal to 1 (we incremented by 1)

Now lets say the missing character is the second from the right, and we repeat the same thing (...191s to 192s):
Code:
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4059d0d081db68f0c2c740901c8f9d322
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4059d0d081db68f0c2c740901c8f9d35c
The difference is now less accurate and equal to 58.

Now lets take a random character in the middle and repeat the same thing again (..UoS1ejn8... to ...UoS2ejn8...):
Code:
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4058c695c4030531c07c151f5a0c1df24
809a96095dbbf6e7fddf52b0c06f96c1e107723599a4058d07203ee971c61c13ca844ce9df24
Now the difference is huge and equal to 3199866632452173458088315935260672 while it was only 1 character and we only incremented the character by 1.
legendary
Activity: 952
Merit: 1367
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.
newbie
Activity: 16
Merit: 0
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 .
legendary
Activity: 952
Merit: 1367
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.
newbie
Activity: 16
Merit: 0
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 ?
legendary
Activity: 952
Merit: 1367
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.

- 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.
newbie
Activity: 16
Merit: 0
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 .
newbie
Activity: 16
Merit: 0
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 ?
legendary
Activity: 952
Merit: 1367
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.
newbie
Activity: 16
Merit: 0
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 Sad
Pages:
Jump to: