Pages:
Author

Topic: Pollard's kangaroo ECDLP solver - page 45. (Read 58537 times)

jr. member
Activity: 50
Merit: 7
July 23, 2021, 10:58:43 AM
What DP size are you using and how many DPs have you already found?

I have discovered that adjusting the DP size too high or too low actually ruins the runtime of Kangaroo so usually it's better to leave it at the default setting, or no more than 5 bits away from the default.

I am running DP 25 I'm at [DP Count 2^25.35/2^25.55] Searching in the 2^99-2^100 Keyspace using 1,048,576 Divided Keys
Are you running/checking all keys at once or run 1 key for so long then run the next key?

All keys simultaneously.
full member
Activity: 1162
Merit: 237
Shooters Shoot...
July 23, 2021, 10:36:05 AM
What DP size are you using and how many DPs have you already found?

I have discovered that adjusting the DP size too high or too low actually ruins the runtime of Kangaroo so usually it's better to leave it at the default setting, or no more than 5 bits away from the default.

I am running DP 25 I'm at [DP Count 2^25.35/2^25.55] Searching in the 2^99-2^100 Keyspace using 1,048,576 Divided Keys
Are you running/checking all keys at once or run 1 key for so long then run the next key?
jr. member
Activity: 50
Merit: 7
July 23, 2021, 09:20:48 AM
What DP size are you using and how many DPs have you already found?

I have discovered that adjusting the DP size too high or too low actually ruins the runtime of Kangaroo so usually it's better to leave it at the default setting, or no more than 5 bits away from the default.

I am running DP 25 I'm at [DP Count 2^25.35/2^25.55] Searching in the 2^99-2^100 Keyspace using 1,048,576 Divided Keys
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
July 23, 2021, 06:10:45 AM
What DP size are you using and how many DPs have you already found?

I have discovered that adjusting the DP size too high or too low actually ruins the runtime of Kangaroo so usually it's better to leave it at the default setting, or no more than 5 bits away from the default.
member
Activity: 110
Merit: 61
July 23, 2021, 03:16:21 AM
I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool


Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo


What DP size are you using and how many DPs have you already found?
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
July 22, 2021, 09:17:58 PM
Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo
With that rate you should be able to get #119 in ~10 days. What is your power consumption for these 809 Billion Keys/s on Kangaroo?

Cheesy Getting close boys!
Good luck!

A little under 58 Kw Cry


Hello, check your PM messages.

Regard.
jr. member
Activity: 50
Merit: 7
July 22, 2021, 08:52:31 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool

What a device is that?

Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo

But believe it or not I get better performance from my 3990X Threadrippers (4 in total), i built a program that combines Bitcrack with BSGS and uses a POW server to distribute the ranges to my machines (with a few other minor revisions), Calculating huge Big Steps over 3TB of memory in total, ~40,000,000,000,000,000,000 Keys/s currently working on the 120 address, CPU machines have been running for 5.2 days solid now, GPUs have been running close to a month Cheesy Getting close boys!
Interested in what you are doing combining a key/brute force program with BSGS.

With 5 GPUs I was getting 62,000,000,000,000,000 hashes per second, with a modified brute force/kangaroo approach.

With BSGS alone, a single 4 thread CPU should get/check around 2^44 keys in less than 3 seconds.

Applying your bruteforce/kangaroo approach with my farm might yield some impressive results, those are very intriguing numbers!

I am only utilizing the physical cores on my 3990X's,  severely underclocked as well... Using the full power of the CPU's resulted in a negative performance impact due to heat, even with watercooling I cannot dissipate the heat fast enough.
full member
Activity: 1162
Merit: 237
Shooters Shoot...
July 22, 2021, 08:23:22 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool

What a device is that?

Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo

But believe it or not I get better performance from my 3990X Threadrippers (4 in total), i built a program that combines Bitcrack with BSGS and uses a POW server to distribute the ranges to my machines (with a few other minor revisions), Calculating huge Big Steps over 3TB of memory in total, ~40,000,000,000,000,000,000 Keys/s currently working on the 120 address, CPU machines have been running for 5.2 days solid now, GPUs have been running close to a month Cheesy Getting close boys!
Interested in what you are doing combining a key/brute force program with BSGS.

With 5 GPUs I was getting 62,000,000,000,000,000 hashes per second, with a modified brute force/kangaroo approach.

With BSGS alone, a single 4 thread CPU should get/check around 2^44 keys in less than 3 seconds.
jr. member
Activity: 50
Merit: 7
July 22, 2021, 06:05:21 PM
Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo
With that rate you should be able to get #119 in ~10 days. What is your power consumption for these 809 Billion Keys/s on Kangaroo?

Cheesy Getting close boys!
Good luck!

A little under 58 Kw Cry
copper member
Activity: 76
Merit: 11
July 22, 2021, 05:56:44 PM
Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo
With that rate you should be able to get #119 in ~10 days. What is your power consumption for these 809 Billion Keys/s on Kangaroo?

Cheesy Getting close boys!
Good luck!
jr. member
Activity: 50
Merit: 7
July 22, 2021, 05:24:32 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool

What a device is that?

Ive used to be big into mining crypto so Ive got a huge farm of GPU's, Im currently getting around 809 Billion Keys/s on Kangaroo

But believe it or not I get better performance from my 3990X Threadrippers (4 in total), i built a program that combines Bitcrack with BSGS and uses a POW server to distribute the ranges to my machines (with a few other minor revisions), Calculating huge Big Steps over 3TB of memory in total, ~40,000,000,000,000,000,000 Keys/s currently working on the 120 address, CPU machines have been running for 5.2 days solid now, GPUs have been running close to a month Cheesy Getting close boys!
copper member
Activity: 76
Merit: 11
July 22, 2021, 04:21:07 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool

What a device is that?
jr. member
Activity: 50
Merit: 7
July 22, 2021, 04:12:29 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

I am currently in the Quadrillions of Keys/s and still no luck with finding the 120 Puzzle... yet  Cool
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
July 22, 2021, 03:56:58 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?

Poible(what can avaliable for me) 4 time faste, but, this not crack 256byte or 128 byte direclty...
copper member
Activity: 76
Merit: 11
July 22, 2021, 03:29:05 PM
...
I'm work now with 861 811 060 385 455 217 keys/s but this is not helpful for 120 !!!
How is that high keys/s rate possible?
member
Activity: 73
Merit: 19
July 22, 2021, 05:36:33 AM
Thanks for your attention COBRAS
The answer to my question is not your answer. I know how to translate hexdecimal numbers. but it became difficult for me to read it in c language and understand loop methods after a while.
For this reason, I wanted to understand with the example in my previous message.
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
July 21, 2021, 07:10:56 PM
Hello there

Can you explain with an example the algorithm used in Pollard's kangaroo ECDLP solver project?
I'm having trouble understanding because the numbers are hexdecimal.

for example


sage: randint(2**45,2**46)
47219499872892

sage: 47219499872892*G
(18692559038988851916170053003258633318507926584259629315624368898934485230811 : 9144672546996927057709444239997623041606234894764707963152906128604997321118 : 1)

sage: hex(18692559038988851916170053003258633318507926584259629315624368898934485230811),hex(9144672546996927057709444239997623041606234894764707963152906128604997321118)
('29539d0d985554a180fa729fdfcf57727e275619c4f7624923d489ba9ba324db', '1437b38492cc93a5e7188705806da639a9bdabb9591f3e265dc278c1afef819e')




2**45 bit
2**46 bit
pubkey = 0229539d0d985554a180fa729fdfcf57727e275619c4f7624923d489ba9ba324db



this can output decimal in hex. and vice versa all hex-es needs start with "0x""

https://defuse.ca/big-number-calculator.htm
member
Activity: 73
Merit: 19
July 21, 2021, 06:39:35 PM
Hello there

Can you explain with an example the algorithm used in Pollard's kangaroo ECDLP solver project?
I'm having trouble understanding because the numbers are hexdecimal.

for example


sage: randint(2**45,2**46)
47219499872892

sage: 47219499872892*G
(18692559038988851916170053003258633318507926584259629315624368898934485230811 : 9144672546996927057709444239997623041606234894764707963152906128604997321118 : 1)

sage: hex(18692559038988851916170053003258633318507926584259629315624368898934485230811),hex(9144672546996927057709444239997623041606234894764707963152906128604997321118)
('29539d0d985554a180fa729fdfcf57727e275619c4f7624923d489ba9ba324db', '1437b38492cc93a5e7188705806da639a9bdabb9591f3e265dc278c1afef819e')




2**45 bit
2**46 bit
pubkey = 0229539d0d985554a180fa729fdfcf57727e275619c4f7624923d489ba9ba324db





full member
Activity: 1162
Merit: 237
Shooters Shoot...
July 09, 2021, 07:32:47 PM
Does anyone have the public key of 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN   puzzle #64 or is there a way to figure out the public key of a public address?? I'm so confused I've been running cuBitCrack on tesla v100 for almost a day and I figured that Pollard's kangaroo for SECPK1 would work a lot better than cuBitCrack please help
Try Bitcrack2 it has a great random stride from 1 to 32, uses public address not key. With a fast gpu like yours it may do the trick. I ran 4 gtx 970's for 4 months non stop and only got a large electric bill on 64. Looking at the previous keys found my bet is on d, e or f and probably uncompressed since the keyspace is not that big and no one has found it in a few years and most try compressed. Good luck
You can't use a program that uses public key for 64. All we have is the public address for 64.

It will be a compressed key, as all are. No one has found it because only around 13% of total keyspace has been searched.  Maybe add 1 or 2% to that for a total of 15%, but that is probably all that has been searched.
jr. member
Activity: 76
Merit: 4
July 09, 2021, 07:27:53 PM
Does anyone have the public key of 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN   puzzle #64 or is there a way to figure out the public key of a public address?? I'm so confused I've been running cuBitCrack on tesla v100 for almost a day and I figured that Pollard's kangaroo for SECPK1 would work a lot better than cuBitCrack please help
Try Bitcrack2 it has a great random stride from 1 to 32, uses public address not key. With a fast gpu like yours it may do the trick. I ran 4 gtx 970's for 4 months non stop and only got a large electric bill on 64. Looking at the previous keys found my bet is on d, e or f and probably uncompressed since the keyspace is not that big and no one has found it in a few years and most try compressed. Good luck
Pages:
Jump to: