Pollard's kangaroo ECDLP solver

[Etar]

Hello @Jean_Luc and dear forum members,

Thanks for this, I gave it a try with a 80bit range and it worked.

One question please. If the key/keys is out of range for the given PubKeys in the .txt file, is it suppose to stop and give an error? I tested this by searching out of range keys for 3 pubKeys and it kept searching for many hours without stopping or giving an error like "not found" or something. Isn't it supposed to stop once it finishes searching the range without finding the key? Again I'm referring o smaller ranges 70-80 bits and I use powerful Teslas. If the keys are in range it finds them but if they keys are out of range it just keeps going...Thanks.

Cheers,
Jorge

Kangaroo did not know that you public key is out of range and will keep searching forever.
To stop searching use commands -m maxStep: number of operations before give up the search (maxStep*expected operation)
For ex if expected operation = 2^30 and -m 2 then Kangaroo will stop searching after 2^31 operations.

But be careful when choosing -m because the expected number of operations is with a 50% probability. Or it may be that your key will be found at 80% or even 90% and using -m can make it impossible.

Generally use a kangaroo only if you are sure that the key lies in this range!

[1715125442]

1715125442

[1715125442]

1715125442

[1715125442]

1715125442

[1715125442]

1715125442

[Bitcoinfan2020]

Hello @Jean_Luc and dear forum members,

Thanks for this, I gave it a try with a 80bit range and it worked.

One question please. If the key/keys is out of range for the given PubKeys in the .txt file, is it suppose to stop and give an error? I tested this by searching out of range keys for 3 pubKeys and it kept searching for many hours without stopping or giving an error like "not found" or something. Isn't it supposed to stop once it finishes searching the range without finding the key? Again I'm referring o smaller ranges 70-80 bits and I use powerful Teslas. If the keys are in range it finds them but if they keys are out of range it just keeps going...Thanks.

Cheers,
Jorge

Kangaroo did not know that you public key is out of range and will keep searching forever.
To stop searching use commands -m maxStep: number of operations before give up the search (maxStep*expected operation)
For ex if expected operation = 2^30 and -m 2 then Kangaroo will stop searching after 2^31 operations.

But be careful when choosing -m because the expected number of operations is with a 50% probability. Or it may be that your key will be found at 80% or even 90% and using -m can make it impossible.

Generally use a kangaroo only if you are sure that the key lies in this range!

OK, got it. Thanks for explaining.

[Etar]

Maybe any one can share map file from crackServer?

[dextronomous]

Maybe any one can share map file from crackServer?

hi there etar,

where does it get those 32 addressess. i mean it finds those 32 but writes one
at the end inside this file with a date and winkey.txt inside the default folder the test.bat.
so when run 1 time, at the end of those 32 can it show the keys saved inside the xxx.txt cause right
now nowhere the pkey for 31 of them to be found. is it.?
thanks man.

[Etar]

Maybe any one can share map file from crackServer?

hi there etar,

where does it get those 32 addressess. i mean it finds those 32 but writes one
at the end inside this file with a date and winkey.txt inside the default folder the test.bat.
so when run 1 time, at the end of those 32 can it show the keys saved inside the xxx.txt cause right
now nowhere the pkey for 31 of them to be found. is it.?
thanks man.

in test.bat address main addres 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv and -dp 6 and range 8000000000:ffffffffff
This mean that whole range devide into 32subranges. And each of this subranges in random way go to client.
So Task for client is find 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv but to prof of work, that client realy solve rubrange, server add 1 address randomly generated on the fly in this subrange.
So client get 2 address in each job. main address and pow address. And he need at worst case solve 1 address and in the best 2 address.
Once main key solved server creat winkey.txt file where put privat key and address. PK from pow keys never stored no where.
File xxx.txt created only on clientside and always deleted by client app.

[WanderingPhilospher]

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

[COBRAS]

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

Hello

Endomorphism perate 1rpivkeyPt/2 bytes * 2 !!! So endomorhpism not operate not split ranges.

Bro, this is

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

a ranges for kids bro

what you say about ranges for ex

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

Yous see ? real keys are not 65 bytes bro

And "real deal"

Search in from

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
to
FAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

[WanderingPhilospher]

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

Hello

Endomorphism perate 1rpivkeyPt/2 bytes * 2 !!! So endomorhpism not operate not split ranges.

Bro, this is

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

a ranges for kids bro

what you say about ranges for ex

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

Yous see ? real keys are not 65 bytes bro

Kid or not, I am just telling you the python script offsetting the pubkey with starting range is not going to help you with a range such as:

Code:

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

But it will for the smaller, "kid" ranges.
Also, if 0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx is kid range, then there is an easy .64 bitcoin waiting for you

[COBRAS]

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

Hello

Endomorphism perate 1rpivkeyPt/2 bytes * 2 !!! So endomorhpism not operate not split ranges.

Bro, this is

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

a ranges for kids bro

what you say about ranges for ex

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

Yous see ? real keys are not 65 bytes bro

Kid or not, I am just telling you the python script offsetting the pubkey with starting range is not going to help you with a range such as:

Code:

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

But it will for the smaller, "kid" ranges.
Also, if 0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx is kid range, then there is an easy .64 bitcoin waiting for you

Im some busy now, I will message you some later

Br

[COBRAS]

-snip-
Bro, Your code is making what is described there https://bitcointalk.org/index.php?topic=5238719.msg54296078#msg54296078 or something else ?

Python code do exactly what you need (substract startrange from public key). After you will find key, just add to key your startrange and you will get correct PK.

Big Thank You Bro !!!

@COBRAS, this code is not going to help you the way you think it might. You still have to know the starting range in order for it to help you, and with larger ranges, it will not help you at all, even if you know the starting range. Large range in what I think you are looking at, 2^256...it will not help you so do not waste time using the code and searching. It's not going to split the range in half, so you will not go from 2^256 to 2^128.
Now, what it can do, and what I can do with it, is split search time dramatically with smaller ranges.
Anyone can challenge, set up a test. I've seen several posts stating it doesn't help reduce search time but it does.
Test:
Someone create a random private key in let's say this range:

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

(keep it small so it's not a long test)
Once you've generated the private key in that range, find the public key and post it here.
Running CPU only, I bet I can find the private key in half the time than it would normally take someone else just running Kangaroo alone. I will post results of my time versus anyone else's time, running Kangaroo only.
COBRAS, I just don't want you wasting any time thinking it will cut range in half. JP says there is a quick mod to increase the Kangaroo search range from 128 to 256. I'd ask him what to do code wise, versus doing anything else.
Someone post pub key in the

Code:

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

range. Let's go.

Hello

Endomorphism perate 1rpivkeyPt/2 bytes * 2 !!! So endomorhpism not operate not split ranges.

Bro, this is

0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

a ranges for kids bro

what you say about ranges for ex

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

Yous see ? real keys are not 65 bytes bro

Kid or not, I am just telling you the python script offsetting the pubkey with starting range is not going to help you with a range such as:

Code:

1000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
4000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
8000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx
F000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx

But it will for the smaller, "kid" ranges.
Also, if 0000000000000000000000000000000000000000000000001xxxxxxxxxxxxxxx is kid range, then there is an easy .64 bitcoin waiting for you

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

[TheArchaeologist]

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

You are aware there are no funds in 1PymQyaT8eLb8e3vgkpjgcesNwpEgQ56CB right?

[COBRAS]

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

You are aware there are no funds in 1PymQyaT8eLb8e3vgkpjgcesNwpEgQ56CB right?

Yes. I will give 30$ in btc whom fined privey

[youssefs0102]

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

You are aware there are no funds in 1PymQyaT8eLb8e3vgkpjgcesNwpEgQ56CB right?

Yes. I will give 30$ in btc whom fined privey

how did you know the range is not large and how did you find this public key ? i can help if you give me more information about this

[COBRAS]

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

You are aware there are no funds in 1PymQyaT8eLb8e3vgkpjgcesNwpEgQ56CB right?

Yes. I will give 30$ in btc whom fined privey

how did you know the range is not large and how did you find this public key ? i can help if you give me more information about this

Edited:
Show me private key first. If you do it, we are talk after. Ok ?

[youssefs0102]

Ok Bro, help me fined privkey to this pubkey:

04eb838fb6782028a5adfc4082e52f30341ad2c0b3571ed8082062304a11eddeeb6d72b07bdf5c9 40efeeaa7f91e5a2552f632bb20e2744720973b26b4d16c61af

I dont know exact range, but think what range is not to lage. PLEASE TRY SEARCH PRIVKEY, CAN YOU GET THIS PRIVKEY ?

?

You are aware there are no funds in 1PymQyaT8eLb8e3vgkpjgcesNwpEgQ56CB right?

Yes. I will give 30$ in btc whom fined privey

how did you know the range is not large and how did you find this public key ? i can help if you give me more information about this

Publick privkey fires Bro. If you help me we are can talk.

sorry i didn't inderstand what you say

[dextronomous]

Maybe any one can share map file from crackServer?

hi there etar,

where does it get those 32 addressess. i mean it finds those 32 but writes one
at the end inside this file with a date and winkey.txt inside the default folder the test.bat.
so when run 1 time, at the end of those 32 can it show the keys saved inside the xxx.txt cause right
now nowhere the pkey for 31 of them to be found. is it.?
thanks man.

in test.bat address main addres 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv and -dp 6 and range 8000000000:ffffffffff
This mean that whole range devide into 32subranges. And each of this subranges in random way go to client.
So Task for client is find 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv but to prof of work, that client realy solve rubrange, server add 1 address randomly generated on the fly in this subrange.
So client get 2 address in each job. main address and pow address. And he need at worst case solve 1 address and in the best 2 address.
Once main key solved server creat winkey.txt file where put privat key and address. PK from pow keys never stored no where.
File xxx.txt created only on clientside and always deleted by client app.

ok took some time, but i get it now, random no problemo, its on the same road, ok thanks for the answer, what if i dont want to solve those random address takes time to solve them?.
just the 64th puzzle how you start like wich -dp  and is dp21 to high?
Etar and one more question, it sits at 21.00 start time, for over a day, without showing anything, is there a verbose option or more details while this waiting happens, thanks

[Etar]

-snip-
ok took some time, but i get it now, random no problemo, its on the same road, ok thanks for the answer, what if i dont want to solve those random address takes time to solve them?.
just the 64th puzzle how you start like wich -dp  and is dp21 to high?
Etar and one more question, it sits at 21.00 start time, for over a day, without showing anything, is there a verbose option or more details while this waiting happens, thanks

bitcrack generate public keys and convert each pub key to address then just compare this address with main and pow.
So you didn`t spent time to find pow address. It is the same like you start walk from the beginning of the street before you find house number 10(main address) you first find house number 6(pow address)
There no verbose option, each connection of client to server you can see in server console(ask job, submit, etc). Or you mean that you not see anything in client console?
In client console you should see that the work recieved(params of this work) and information that bitcrack started.(Your GPU will be buzzy during solving job)
About -dp, dp you need set dependency of your gpu power. -dp 20 mean devide range into 2^20 subranges. For pazzle #64  2^64/2^20=2^43 each subrange. 2080ti can calculate 2^30.3key/s so subrange 2^43 2080ti can done in 2.5h. More dp = more subranges = more quick will be solved subrange. Don`t forget that server have timeout 24h for job done. If your subrange will be to big and gpu can not done this job in 24 then job will be deleted and you just waste of your time.
For me for #64 best choice set DP between 19-21 for hi-end GPU and 22..24 for low-end GPU.
And before using client app make clear test and launch bitcrack directly.. find best params -t,-b,-p for your GPU and after that use this params in client app.

[dextronomous]

wow great thanks a lot for that information. guess needed it a lot.
now i can continue, now it works. great pieces. your's and brichard's work.
good luck

[COBRAS]

wow great thanks a lot for that information. guess needed it a lot.
now i can continue, now it works. great pieces. your's and brichard's work.
good luck

As for me DP not so simple. Then I crack 64 bytes with DP 20, key was not be found, and with dp 16 key was found. This on 2080ti.

[dextronomous]

wow great thanks a lot for that information. guess needed it a lot.
now i can continue, now it works. great pieces. your's and brichard's work.
good luck

As for me DP not so simple. Then I crack 64 bytes with DP 20, key was not be found, and with dp 16 key was found. This on 2080ti.

what key you find?