Topic: Pollard's kangaroo ECDLP solver - page 53. (Read 60095 times)

The quick and easy answer would be to look at how long it took to solve #110...roughly 2 days.  You could take the 2 days and times that by 260 to get a quick and easy answer however, we know that the tames generated while searching for each pubkey would be used/valid for each subsequent pubkey. I think if one had 260 GPUs, each searching for 1 of the 260 pubkeys, and doing a daily merge/collision check, it would be much faster than the 2 x 260 days, but no way to be 100% certain.

Are all 260 in the 110 range?

If you can compile your own version, you can add the export option that https://github.com/PatatasFritas/FriedKangaroo created.  If you search for PatatasFritas in this thread, they also have a python script that will do the same; export the wild and tame files.

What to use to look at the DP's I have in the workfiles?

if 260 pubkeys in 110bit, then how much time it will take ?

Yes the full range of 120

Not really.  I don't know what range you are running but normally they start accumulating when running through a small range.  There is limited space in smaller range so the kangaroos in the same herd start to trip over each other.  But if you do get dead kangaroos in a larger range, no worries, the program automatically resets them to different random points.

why at certain times the kangaroo program start to accumulate dead kangaroos? does this give any indication as to solving the the puzzle

I am very grateful to you for your answer.
GoldTiger69
NotATether

P.S.
It is a pity that this puzzle has already exhausted itself, there are literally 1-3 addresses left that can be obtained, the rest will remain unattainable.

The private keys were deliberately generated within those ranges by the author. The ranges themselves weren't calculated.

So it's like the author made #64's private key between ranges 2^64 and 2^65-1, #65 between 2^65 and 2^66-1, and so on.

How then were the ranges calculated in https://privatekeys.pw/puzzles/bitcoin-puzzle-tx
?

You can't, that's why Bitcoin is secure (by now).

Hi everybody.
I read a very interesting topic.
I have a question.
How do you know in which exact range is this or that address?


For example, take any address

1AnQDYo81Ta4VcSbeQNWp9CwPcsZqRvPGD
How to find out in what range its private key?

I apologize if the question is stupid.

I am new to this and I appreciate the help. i tested this one on 63 and 65, starting at 0 straight not random in the keyspace and it took 0 seconds to find 63 and about 1 minute on 65 with just the 1 public key so i know it works. I just wasted the last month on 120 because i divided the keyspace up in 8 parts (lack of understanding) with none of the parts able to merge with the other. I should have asked people with knowledge first LOL. If i do find 120 or 125 I will definitely take care of you. Thanks

I really can't speak to a different BSGS program.  Jean Lucs loads all pubkeys, performs the baby steps one time, and then runs each pubkey through the giant steps, sequentially.

If it takes 10 seconds to perform/store the baby steps and then 1 second to run and check one public key in a 2^48 range, then if you were to run 1,000 pubkeys in the same  range, it would take about 1 minute to search all 1,000 pubkeys loaded.

I wouldn't use another BSGS because I haven't found one faster than Jean Luc's.

Ok with 200 keys loaded I get
 Thread ac696c49b9408a82028a45ab2a0629ds: 2754540302104 keys/s

• Thread fbba3026c71c044279bbfa174174d5ds: 2750714982463 keys/s
• Thread 9468dafbf9970e2876c5cc4199a3edds: 2752389277771 keys/s
• Thread cfe35ea9483be51a01a063acbcbf3eds: 2748653881650 keys/s
• Thread eefb0efefad83846f455cf5b9bd98eds: 2750316472506 keys/s
• Thread db0b986adc150b65b3624c4c3351bads: 2751949106769 keys/s
• Thread 996ef3f4b518d1e2842ba5f0cf0551^C: 2753552586849 keys/s

Normally this computer gets 600 trillion per second

my other computer usually does with 1 key loaded 2.7 quadrillion per second but with 1000 keys loaded it is doing 76 billion / second.

I don't think keys per second drops using BSGS, not the one I put out that Jean Luc built.
It's actually faster because with multiple pubkeys you do not have to rewalk the baby steps every time.  If you are using another version of BSGS, then I'm not sure about it. But the one I use, it's the same speed, but overall faster because it doesn't have to perform and store the baby walks every time.

With Kangaroo, it probably is faster searching 1 pubkey.  Let's say you shifted down 2^10; now you'd have to search 1024 pubkeys in the 2^110 range.
Avg operations of 1 pubkey at 2^120 = 2^60 (roughly) but 1024 at 2^110 = 1024 * 2^55 = 2^65 operations

For example If I am running with 1 loaded public key BSGS and for argument sake with 1 key loaded I am operating at 100 million keys per second but if I substract and load  1000 of the same key just offset by a different distance from the target key my keys per second drops 100 million/1000 (more actually) but now I have 1000 more possible chances of a collision because i have added 1000 targets.

Example
03b6c66d90910721ac8e6f8ef0ebb222fff638227122b21c5853e787ca3d119f08 # - 651321717934608777722865459537368854
030e7b9ccf0feabe79d8745a89b575b52ff21333368b4a9c95c72dbef88a6105e2 # + 651321717934608777722865459537368854
029a564b60e6bed3449052228a609334b43d59bc5f79ca5c622334658ce89b6026 # - 657967857913533357087384494838770577
03a127833050783f814ee013e796fbc937067a86741564bdb9086a6e6e6398e11d # + 657967857913533357087384494838770577
03d0203676b61edda6208b2f9b204de5e8ee2849723458dc7531b1eaba503de390 # - 664613997892457936451903530140172300
0247dd5a10ae3aab4187c7af2a5babcc8ee401ed09e67fbc6ea75e35cc8471d8c9 # + 664613997892457936451903530140172300
02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630 # target


If one of these keys hits then i just add or subtract the decimal value on the right from the hex private key found  convert to decimal add or subtract than convert back to hex  and now I have the  key for 120 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa885a2630

Please explain...

That's what I was trying to ask a while ago about how many ways to solve a key.

Is it better to go with the 1 public key and get the higher keys per second or go with keysubtracter of 100 or 1000 public keys and get proportionally lower keys per second?