Pollard's kangaroo ECDLP solver

[a.a]

brainless.... are you kidding me? Come with some reasonable arguments and not with conjectures.


2520 will get you stuck, but 30240 will work. Old Babylonian Astronomers knew this.

Source(s): Dude trust me

[1714489853]

1714489853

[1714489853]

1714489853

[1714489853]

1714489853

[1714489853]

1714489853

[1714489853]

1714489853

[ssxb]

30240 came from astro
360 days in year
7 day in week
12 month in year
360 x 7 x 12 = 30240
Full ver
2520
360 x 7 = 2520
For complete numerology 30240 will work
2520 will make u stuck in some part of calc

come to papa 

[_Counselor]

30240 came from astro
360 days in year
7 day in week
12 month in year
360 x 7 x 12 = 30240
Full ver
2520
360 x 7 = 2520
For complete numerology 30240 will work
2520 will make u stuck in some part of calc

I don't want to upset you, but there are 365 days in a year

[NotATether]

~

I don't want to upset you, but there are 365 days in a year

What a dumpster fire the last few pages of this thread have been. 

[ssxb]

so talk about idea guys

here is idea , brainless make a fire here and instead of drinking soda i throw all my soda to extinguish this shit but all in vein ~ now when i am out from all soda cans . my mind start working again and got a idea
why the hell i should not ask brainless to share a script which he is using to reduce the shit out of keys.

brainless : could you please be so kind and share your genius script so i can see what u did in this summer.

as i cant see a working logic here and i have to sale that script to a.a to buy a soda cans

[ssxb]

30240 came from astro
360 days in year
7 day in week
12 month in year
360 x 7 x 12 = 30240
Full ver
2520
360 x 7 = 2520
For complete numerology 30240 will work
2520 will make u stuck in some part of calc

2   447   7572   564114
3   596   9536   752152
4   631   10096   1128228
6   894   14304   1504304
8   1192   15144   2256456
12   1262   20192   3008608
16   1788   28608   4512912
24   1893   30288   6017216
32   2384   40384   9025824
48   2524   60576   18051648
64   3576   94019  
96   3786   121152  
149   4768   188038  
192   5048   282057  
298   7152   376076  

30288 what other guys call 30240 as i call this shit a 30288

WTF ?  

dude you are going against your magic numbers , somebody please hand over me tomato ketchup i will assume it soda and drink it today

 where the hell i left my .75 btc? sorry i forgot 

[wedom]

Guys, if brainless really succeeded in reducing the number of keys, then you would listen carefully, turn on your brain, think, try and analyze. And I see that Brainless is giving advice, and others already being shit on here for 2 pages, as if all of you have a script to reduce by 10 bits with one key.
Brainless gives interesting math from a side that many haven't even thought about. So less showing off and more focus to understand the algorithm itself. I don't think Brainless will give it in a ready-made form. Thank you for at least giving hints. Enjoy.

[wedom]

...
30288 what other guys call 30240 as i call this shit a 30288

WTF ?  

dude you are going against your magic numbers

...

Why do you think he's going against the magic numbers?
Didn't you think so: 30240 = 30288 - 48 ?
That said, both 30288 and 48 refer to these numbers

[a.a]

And what is the actual algorithm? It is so annoying.

brainless: Check my magic numbers
me: What are those.
brainless: See this post, were is just post them without any explaination
me: lets see, what is it? check it out and search what those are... they are the divisors of N-1 Ok. Check in Wolfram Alfa, seems legit
me: What now?
brainless: You do something with them and get less keys
ssxb: You add, subtract multiply divide in some arbitrary order and get less keys.


Wow
What is the fucking algorithm? Is there some pseudocode?

But hey, he wants 0,75 BTC for a Rig. Sure...

[math09183]

WTF you did to this thread?
Your lack of mathematical knowledge is terrible. Thread which started with smart software based on well-known and proofed mathematical theory you changed into thrash can, garbage full of your imaginations.
Is it possible to ignore some users on the forum? Just not to see BS from people like COBRA or brainles. You just waste network bandwidth.
I understand that someone may be greedy - but greedy, stupid and ignorant - I do not accept it...

[brainless]

30240 came from astro
360 days in year
7 day in week
12 month in year
360 x 7 x 12 = 30240
Full ver
2520
360 x 7 = 2520
For complete numerology 30240 will work
2520 will make u stuck in some part of calc

2   447   7572   564114
3   596   9536   752152
4   631   10096   1128228
6   894   14304   1504304
8   1192   15144   2256456
12   1262   20192   3008608
16   1788   28608   4512912
24   1893   30288   6017216
32   2384   40384   9025824
48   2524   60576   18051648
64   3576   94019  
96   3786   121152  
149   4768   188038  
192   5048   282057  
298   7152   376076  

30288 what other guys call 30240 as i call this shit a 30288

WTF ?  

dude you are going against your magic numbers , somebody please hand over me tomato ketchup i will assume it soda and drink it today

 where the hell i left my .75 btc? sorry i forgot  

for kids in math, first learn word and meaning
1. ecc secp256k1 number = 1bit to 256bit
2. numberology = 0 to infinite
i post both side magic numbers, , unfortunatly you all unable to understand, further no details from my side, extreme knowledge for your hightech brains brainless posted, definatly i am thousands year back living in A.D, as i dont know 360 or 365 in a year, here are muslim , christ, and jews, chinese all have there own year calender, and can better understand why 360
Enjoy your time

[WanderingPhilospher]

@WP
I take a 255 bit pubkey, divide it by 33. Now I only have to search the 2^255/33 ~ 2^252  range to find the key. What a reduction.

@ssxb

Well but what is the new knowledge?

Also the 33 division makes sense as the distance between each point will be the mod inverse of 33 or so. Its like cutting the whole N into ranges, as mentioned before. Only problem is, that you are only getting one in the lower bruteforcable range and then can jump from that one and can determine the other 32 private keys.

And yes, you just have to multiply the privatekey times your divisor and then mod N to get the right result.

Again, reduction of range, not what I am saying. I also said you can use any divisor, not just 33. For tests, I also did 192, and 192*192.

Everyone keeps saying you add a bigger range/create a bigger range, but that is not the case. If you divide by using whatever divisor, it does not create a larger keyspace to search. All ranges to search are the original size of whatever size the original private key range is in, except the original range, it has obviously been reduced. So if you start with a key that lies in a 120 bit range and divide by 192 or 256 or 1,000,000, then you can find any pubkey in the same size range. You do not make search range larger.

Also "2^255/33 ~ 2^252" I do not know where this math comes from. If I take a key in a 2^255 range and divide by 33. 255/33, then the new reduced range would be at least 250, but again, not the point here.

"multiply the privatekey times your divisor and then mod N to get the right result" -- seems like more steps than needed, I do not mod N anything to jump back to the private key but I imagine there are multiple ways to walk back to original private key...9 ways to skin a cat.

[a.a]

Is according to your empirical test this range reduction valid for small ranges like 2^120 also?

[WanderingPhilospher]

Is according to your empirical test this range reduction valid for small ranges like 2^120 also?

Not sure if your post/question was to me but yes...that is in fact common knowledge. It's all about powers of 2. If you take a key in 2^120 range and divide by 33, you reduced the range down, by 5 ranges.

If your post was to brainless, only he can answer that lol...

I think many on here are confusing several different concepts. So if one struggles understanding one and confuse it with another, they call out BS or spread misinformation.

I do not know or claim to know brainless' "secret" but my tests were centered on one of his post and what he said in that post is 100% accurate. "when dividing a pub key, the other pubkeys do not appear randomly in the curve..."

Things I am claiming I can do:
reduce any key range, but that adds additional xpoints to search (obviously)
find any pubkey that is generated, after dividing by any divisor, without increasing the size of the original range

[WanderingPhilospher]

Only problem is, that you are only getting one in the lower bruteforcable range and then can jump from that one and can determine the other 32 private keys.

Prime example...your statement is not true as to what I am saying/doing.

I am not jumping from any key to another key...there is no magic jumping.

I can take the pubkeys generated, and search a different range, not the "lower bruteforcable range", and find the priv key to the original pub key. All pub keys created after dividing can be found in a same sized range. And my tests so far, I am actually finding 2 pubs per range that leads me back to original pub key's priv key.

[a.a]

Do you have some example data? Can you provide them to me please?

Privatekey, derived pubkeys and some of their privatekeys counterparts?

I am really interested to analyze your findings.

[WanderingPhilospher]

Do you have some example data? Can you provide them to me please?

Privatekey, derived pubkeys and some of their privatekeys counterparts?

I am really interested to analyze your findings.

I can, it's really not rocket surgery though. It's a matter of people jumping to conclusions about making key ranges larger when dividing. It's also about not searching the entire 2^256 space to find any pub key generated via dividing but knowing exactly where and which key space the generated pubkeys lie in. They don't lie in random ranges, and if you find one, you have solved the private key to original pubkey without looking at lower bits, shifting or whatever some others were discussing.

Basically instead of calling all of brainless' words BS, I took the time to decode what he was saying and verify if what he was saying was true/false...

standby...

[ssxb]

Only problem is, that you are only getting one in the lower bruteforcable range and then can jump from that one and can determine the other 32 private keys.

Prime example...your statement is not true as to what I am saying/doing.

I am not jumping from any key to another key...there is no magic jumping.

I can take the pubkeys generated, and search a different range, not the "lower bruteforcable range", and find the priv key to the original pub key. All pub keys created after dividing can be found in a same sized range. And my tests so far, I am actually finding 2 pubs per range that leads me back to original pub key's priv key.

in case you are wondering , i can subtract 120 and can give you billions of keys from same range which will lead you back to orignal key. dont know why you guys are repeating all old stuffs.

enough fun from my side so i am serious right now on this. believe me or not you guys are working only on 2 methods but there are so many hidden ways to jump forward/back to orignal key.

but one issue is there just one issue. those all methods all failing because all public keys are repeating the relationship on 1 key distance.  what i am talking only those guys will know who had a experience with such jumps or reverse engineering. my project is still under extensive experiments and i have strong believe i will reach to target soon and will share a tip with you guys as well.

#Soda

[WanderingPhilospher]

Only problem is, that you are only getting one in the lower bruteforcable range and then can jump from that one and can determine the other 32 private keys.

Prime example...your statement is not true as to what I am saying/doing.

I am not jumping from any key to another key...there is no magic jumping.

I can take the pubkeys generated, and search a different range, not the "lower bruteforcable range", and find the priv key to the original pub key. All pub keys created after dividing can be found in a same sized range. And my tests so far, I am actually finding 2 pubs per range that leads me back to original pub key's priv key.

in case you are wondering , i can subtract 120 and can give you billions of keys from same range which will lead you back to orignal key. dont know why you guys are repeating all old stuffs.

enough fun from my side so i am serious right now on this. believe me or not you guys are working only on 2 methods but there are so many hidden ways to jump forward/back to orignal key.

but one issue is there just one issue. those all methods all failing because all public keys are repeating the relationship on 1 key distance.  what i am talking only those guys will know who had a experience with such jumps or reverse engineering. my project is still under extensive experiments and i have strong believe i will reach to target soon and will share a tip with you guys as well.

#Soda

zzzzzzzzzzz...same old ssxb

[ssxb]

Only problem is, that you are only getting one in the lower bruteforcable range and then can jump from that one and can determine the other 32 private keys.

Prime example...your statement is not true as to what I am saying/doing.

I am not jumping from any key to another key...there is no magic jumping.

I can take the pubkeys generated, and search a different range, not the "lower bruteforcable range", and find the priv key to the original pub key. All pub keys created after dividing can be found in a same sized range. And my tests so far, I am actually finding 2 pubs per range that leads me back to original pub key's priv key.

in case you are wondering , i can subtract 120 and can give you billions of keys from same range which will lead you back to orignal key. dont know why you guys are repeating all old stuffs.

enough fun from my side so i am serious right now on this. believe me or not you guys are working only on 2 methods but there are so many hidden ways to jump forward/back to orignal key.

but one issue is there just one issue. those all methods all failing because all public keys are repeating the relationship on 1 key distance.  what i am talking only those guys will know who had a experience with such jumps or reverse engineering. my project is still under extensive experiments and i have strong believe i will reach to target soon and will share a tip with you guys as well.

#Soda

zzzzzzzzzzz...same old ssxb

dont forget you need to burn the universe as fuel to break this BTC keep in mind guys target is bigger than you are expecting. so do a part of yours and hope to get it. but who knows this all conversation knowledge will give some clue to our grand son's specifically brainless grand son as i am not leaving much suspense in my conversations as treasure to my grand son otherwise who know he will come and beat a shit out from my grave