Try please someone find a privkey for this pubkey ? range - not more 75-80 Byte.

[COBRAS]

How to find a privkey of 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

Now understand  what is I looking for ?

No, I do not understand.

Are you multiplying by 0x db09b0615ad40a0 * 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ??

yes, I multiply.

Can you try find a privkey for this 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

p.s. I was provide a part of privkey and range 2^60 earlier in previous my post

By multiplying, how does one know what range the new pubkey will lie in?  If it is like dividing, then you would add (instead of subtracting when using division) so this pub/private key is well over the 2^100 range.

Well over 2^100, probably over 2^120 range, not sure what you are trying to do...
Find a privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918, and I will show you privkey for target. ?

p.s. I can provide after sach 'magic''numbers for targets with balance from bounty transactions....

If you are multiplying an existing 2^60 range key by another 2^60 range key (0x db09b0615ad40a0) then the key will be in 2^120 range.

Bro, find interested me privkey, and we are continue ok ? I will info after I will know how to find needed me privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918

[WanderingPhilospher]

How to find a privkey of 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

Now understand  what is I looking for ?

No, I do not understand.

Are you multiplying by 0x db09b0615ad40a0 * 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ??

yes, I multiply.

Can you try find a privkey for this 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

p.s. I was provide a part of privkey and range 2^60 earlier in previous my post

By multiplying, how does one know what range the new pubkey will lie in?  If it is like dividing, then you would add (instead of subtracting when using division) so this pub/private key is well over the 2^100 range.

Well over 2^100, probably over 2^120 range, not sure what you are trying to do...
Find a privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918, and I will show you privkey for target. ?

p.s. I can provide after sach 'magic''numbers for targets with balance from bounty transactions....

If you are multiplying an existing 2^60 range key by another 2^60 range key (0x db09b0615ad40a0) then the key will be in 2^120 range.

Bro, find interested me privkey, and we are continue ok ? I will info after I will know how to find needed me privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918

Bro, no one will waste time on a key that lies in a 2^120 range when their is a current challenge to find a 2^120 range key with 1.2 BTC as prize. You follow?

[COBRAS]

How to find a privkey of 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

Now understand  what is I looking for ?

No, I do not understand.

Are you multiplying by 0x db09b0615ad40a0 * 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ??

yes, I multiply.

Can you try find a privkey for this 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918 ?

p.s. I was provide a part of privkey and range 2^60 earlier in previous my post

By multiplying, how does one know what range the new pubkey will lie in?  If it is like dividing, then you would add (instead of subtracting when using division) so this pub/private key is well over the 2^100 range.

Well over 2^100, probably over 2^120 range, not sure what you are trying to do...
Find a privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918, and I will show you privkey for target. ?

p.s. I can provide after sach 'magic''numbers for targets with balance from bounty transactions....

If you are multiplying an existing 2^60 range key by another 2^60 range key (0x db09b0615ad40a0) then the key will be in 2^120 range.

Bro, find interested me privkey, and we are continue ok ? I will info after I will know how to find needed me privkey for 038141a3381c97660163ce69acf22d5a0cc8c09fcbb624fa556ff17629b4b31918

Bro, no one will waste time on a key that lies in a 2^120 range when their is a current challenge to find a 2^120 range key with 1.2 BTC as prize. You follow?

Ok. I will provide info for 120 key in 30 minutes.... hope someone will be interested after.

[dextronomous]

now comes the magical part where we get some explanation, on btc balance of the key? or stop continue looking for 120..
thanks COBRAS.

[jacky19790729]

if it is 75-80 bit max you can reduce it to 32 - 40 bit :
so in algo used by pollard rho in this 2 examples you get answer during 3 minutes.
if you want pm me mail

~~120 bit  public key divide by 2  =>  119 bit
~~119 bit  public key divide by 2  =>  118 bit
~~118 bit  public key divide by 2  =>  117 bit
~~117 bit  public key divide by 2  =>  116 bit

[WanderingPhilospher]

thank you dear mr. wanderingphilospher for explaining,
i thought with the dividing part it went halving by 2..
and multiplying by db09b0615ad40a0 does this new
key not go over 256 bit there,

Dividing can yield a number of results, not just halving by 2. For example, if you wanted to reduce search range by 2^5 then you would divide by 32. Reversing this would be multiplying or adding. I have never multiplied a key up as this would increase the difficulty, but I believe (someone correct me if I am wrong) you would do the opposite, if you wanted to move a key search range up by 2^5 then you would add (multiply) by 32.

It seems Cobra took the #60 key and multiplied it by another key in the 2^60 range. But I am not 100 percent sure of that either lol.

[COBRAS]

now comes the magical part where we get some explanation, on btc balance of the key? or stop continue looking for 120..
thanks COBRAS.

Sorry, Buddies, some kind of incomprehensible situation came out with 120, I have different approaches to my intermediate public keys secretscan.org in which there is a calculator of the public key from the compressed to the unpacked format, for the public keys(2 pcs) found in many ways, it shows the one and the same address  1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E !!!!:. Force majeure. I am very tired, so I will write a little later.

[a.a]

now comes the magical part where we get some explanation, on btc balance of the key? or stop continue looking for 120..
thanks COBRAS.

Sorry, Buddies, some kind of incomprehensible situation came out with 120, I have different approaches to my intermediate public keys secretscan.org in which there is a calculator of the public key from the compressed to the unpacked format, for the public keys(2 pcs) found in many ways, it shows the one and the same address  1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E !!!!:. Force majeure. I am very tired, so I will write a little later.

If you search for 1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E you will realize that this address is a burner address, as the publickey is not on secp256k1.

[n0nce]

now comes the magical part where we get some explanation, on btc balance of the key? or stop continue looking for 120..
thanks COBRAS.

Sorry, Buddies, some kind of incomprehensible situation came out with 120, I have different approaches to my intermediate public keys secretscan.org in which there is a calculator of the public key from the compressed to the unpacked format, for the public keys(2 pcs) found in many ways, it shows the one and the same address  1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E !!!!:. Force majeure. I am very tired, so I will write a little later.

If you search for 1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E you will realize that this address is a burner address, as the publickey is not on secp256k1.

If I remember correctly, this user has only ever posted about random invalid / burner addresses / wallets that contain a large amount of BTC and he desperately tries to crack them / get help cracking them. Stuff like the public key derived from private key '0' etc. As you say: keys that aren't on the curve at all and similar.

Beware, sometimes they try to waste our time by calling it a 'challenge' and similar, while in actuality it's not a challenge at all and not a 'puzzle' either since these keys are uncrackable other than using brute force.

[a.a]

Yeah it is unprofessional to not even check Google to exclude the most obvious errors. Also the chuzpe to pressure people to calculate their pointless ideas, is unbelievable impertinent

[j2002ba2]

If you search for 1HT7xU2Ngenf7D4yocz2SAcnNLW7rK8d4E you will realize that this address is a burner address, as the publickey is not on secp256k1.

There are however about 2⁹⁶ valid public keys with that address, unknown of course.

There is ~37% chance (1/e), that no 160 bit private key has this address, leaving us with 63.2% chance (1-1/e) that one or more 160 bit private keys has the address. If we consider both compressed and uncompressed public keys, the lack of chance is 13.5%, while one or more is 86.5%.