Pages:
Author

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

full member
Activity: 431
Merit: 105
September 07, 2021, 06:45:52 AM
NotAThether, was thinking, not a programmer.

but can someone make pollard kangaroo, with thinking about the manually inputted lesser divisor, like 32 bits less, or whatever bit,
"range" so this would require user input, then start the kangaroo search, while this lower point found fast, beep, notification whatsoever,
directly calculate the higher divised pubkey without user input, putting those correct pk's inside file found, and on screen,
sound great doesn't it.
guessing would require some work, but seeing what you guys calculate for fun here, guess would be possible.

Yeah this is definitely possible. Hell, the division-splitting can even be integrated right into JLP Kangaroo (and then you can just use Birthday paradox to search for a handful of public keys at once), eliminating the need for another script.

dont forget you will have only one key in 5 bit below range Grin  other all keys will be on the curve but not below of 5 bit  Grin , in this case you need to load all 33 keys in the program and start searching but expect only one key to be hit. chances to hit one key in big range is fool idea, so my suggestion is

if loading multiple keys will not impact speed of your program do the divisor for 30 (33554432) bit down and load all keys , still one key will be below 30 bit but you will have less total keys in range as compared to original target range ~~~  perhaps this will increase the chance.

brainless talked about reducing the number of keys but he never shared how can we (working script) , perhaps i will figure out something better soon  Grin IA

can use all coders, ssxb, got system with tons of memory, and nice gpu settings here, will bsgs on that one in a minute all the way up to 80 bits, or use jlp kangs. or kangrand from iceland, to find all keys at one go.
jr. member
Activity: 81
Merit: 2
September 07, 2021, 06:38:08 AM
guys good news today i find 2 more ranges and where they are on the curve , today is celebration day for me , as i know total 3 ranges inside divisor , need to figure out other 29 ranges  Grin

  Kiss  math is beautiful  Kiss
jr. member
Activity: 81
Merit: 2
September 07, 2021, 06:27:16 AM
NotAThether, was thinking, not a programmer.

but can someone make pollard kangaroo, with thinking about the manually inputted lesser divisor, like 32 bits less, or whatever bit,
"range" so this would require user input, then start the kangaroo search, while this lower point found fast, beep, notification whatsoever,
directly calculate the higher divised pubkey without user input, putting those correct pk's inside file found, and on screen,
sound great doesn't it.
guessing would require some work, but seeing what you guys calculate for fun here, guess would be possible.

Yeah this is definitely possible. Hell, the division-splitting can even be integrated right into JLP Kangaroo (and then you can just use Birthday paradox to search for a handful of public keys at once), eliminating the need for another script.

dont forget you will have only one key in 5 bit below range Grin  other all keys will be on the curve but not below of 5 bit  Grin , in this case you need to load all 33 keys in the program and start searching but expect only one key to be hit. chances to hit one key in big range is fool idea, so my suggestion is

if loading multiple keys will not impact speed of your program do the divisor for 30 (33554432) bit down and load all keys , still one key will be below 30 bit but you will have less total keys in range as compared to original target range ~~~  perhaps this will increase the chance.

brainless talked about reducing the number of keys but he never shared how can we (working script) , perhaps i will figure out something better soon  Grin IA
full member
Activity: 431
Merit: 105
September 07, 2021, 06:24:11 AM
NotAThether, was thinking, not a programmer.

but can someone make pollard kangaroo, with thinking about the manually inputted lesser divisor, like 32 bits less, or whatever bit,
"range" so this would require user input, then start the kangaroo search, while this lower point found fast, beep, notification whatsoever,
directly calculate the higher divised pubkey without user input, putting those correct pk's inside file found, and on screen,
sound great doesn't it.
guessing would require some work, but seeing what you guys calculate for fun here, guess would be possible.

Yeah this is definitely possible. Hell, the division-splitting can even be integrated right into JLP Kangaroo (and then you can just use Birthday paradox to search for a handful of public keys at once), eliminating the need for another script.

How can i help test, add, can help will test 2day starting now
a.a
member
Activity: 126
Merit: 36
September 07, 2021, 06:06:22 AM
Actually... I dont trust the numbers. It happened to me multiple times too. I had broken code, which resulted basically in an empty for loop. Then I got fictive numbers like those, showing me 1 TH/s, despite there was actually no cracking in process except incrementing the processed key counter.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
September 07, 2021, 03:05:51 AM
NotAThether, was thinking, not a programmer.

but can someone make pollard kangaroo, with thinking about the manually inputted lesser divisor, like 32 bits less, or whatever bit,
"range" so this would require user input, then start the kangaroo search, while this lower point found fast, beep, notification whatsoever,
directly calculate the higher divised pubkey without user input, putting those correct pk's inside file found, and on screen,
sound great doesn't it.
guessing would require some work, but seeing what you guys calculate for fun here, guess would be possible.

Yeah this is definitely possible. Hell, the division-splitting can even be integrated right into JLP Kangaroo (and then you can just use Birthday paradox to search for a handful of public keys at once), eliminating the need for another script.
full member
Activity: 431
Merit: 105
September 06, 2021, 08:52:32 PM
NotAThether, was thinking, not a programmer.

but can someone make pollard kangaroo, with thinking about the manually inputted lesser divisor, like 32 bits less, or whatever bit,
"range" so this would require user input, then start the kangaroo search, while this lower point found fast, beep, notification whatsoever,
directly calculate the higher divised pubkey without user input, putting those correct pk's inside file found, and on screen,
sound great doesn't it.
guessing would require some work, but seeing what you guys calculate for fun here, guess would be possible.
copper member
Activity: 76
Merit: 11
September 06, 2021, 01:58:39 PM
Why ? JeanLuck kangaroo keyrate is 1 Giga, I use kangaroo what 55 terra, and I was try BSGS what 500 Peta(but I no so like BSGS, kangaroo I like more), so WanderingPhilospher make his own soft what has exakeys... If you use dead software this not meant what other uses so software 2.

Well you might be right about BSGS (but I have never used that software before so take this with a grain of salt), but I don't think you can hit 55 terakeys per second on kangaroo without a GPU farm and leverage the kangaroo server feature.

Maybe they have ...

Do you know, if there are already asics like these

not to mine coins but for point addition?
jr. member
Activity: 37
Merit: 1
September 06, 2021, 05:58:20 AM
Yes, ok but could you share us the program? which program is this..
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
September 06, 2021, 05:49:28 AM
Why ? JeanLuck kangaroo keyrate is 1 Giga, I use kangaroo what 55 terra, and I was try BSGS what 500 Peta(but I no so like BSGS, kangaroo I like more), so WanderingPhilospher make his own soft what has exakeys... If you use dead software this not meant what other uses so software 2.

Well you might be right about BSGS (but I have never used that software before so take this with a grain of salt), but I don't think you can hit 55 terakeys per second on kangaroo without a GPU farm and leverage the kangaroo server feature.

see this again:

[55.22 TeraKeys/s][Kang 3072][Count 2^27.92/2^29.06][Elapsed 48s][Dead 0][RAM 25.8MB/44.7MB] This is absolute normal keyrate, but not comfortable for work. Yes, I hope wanderPhilisopher will help and we share with him 1.2 BTC 50/50%.

legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
September 06, 2021, 05:47:01 AM
Why ? JeanLuck kangaroo keyrate is 1 Giga, I use kangaroo what 55 terra, and I was try BSGS what 500 Peta(but I no so like BSGS, kangaroo I like more), so WanderingPhilospher make his own soft what has exakeys... If you use dead software this not meant what other uses so software 2.

Well you might be right about BSGS (but I have never used that software before so take this with a grain of salt), but I don't think you can hit 55 terakeys per second on kangaroo without a GPU farm and leverage the kangaroo server feature.
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
September 06, 2021, 05:29:17 AM
I will find it...for the team...for the win!! With my new program that does not require DPs or RAM. It just searches for xpoint and let's every thread just EAT!

Working on xPoint: c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938
Using  [Number of CPU Threads: 0] [DP size: n/a]
Using GPU [GPU Id 0 RTX 3070]
............................................
Scanning Range  0x1 : 0x1124bff742a76f92fa3a76f8f6552f
[2714579271.01 TeraKeys/s] [Elapsed 4:26][RAM n/a]

LOL  Cheesy , nice try with the speed doctoring WP.

For real though, I think the number of points is much smaller than the number of privkeys, because you can exclude invalid points on the curve when searching for xpoint.



Please guys share us the program that does 2714579271.01Tera/s
What kind of program is this? how does it search with such a very huge fast speed?
many thanks

I think it was just a prank, there is no way to make a program that can search

2714.57927101

exakeys per second.

Why ? JeanLuck kangaroo keyrate is 1 Giga, I use kangaroo what 55 terra, and I was try BSGS what 500 Peta(but I no so like BSGS, kangaroo I like more), so WanderingPhilospher make his own soft what has exakeys... If you use dead software this not meant what other uses so software 2.
jr. member
Activity: 37
Merit: 1
September 06, 2021, 05:09:51 AM
Yes i think too it's a prank.
there's no way that a program can search THIS much addreseses/s
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
September 06, 2021, 05:05:14 AM
I will find it...for the team...for the win!! With my new program that does not require DPs or RAM. It just searches for xpoint and let's every thread just EAT!

Working on xPoint: c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938
Using  [Number of CPU Threads: 0] [DP size: n/a]
Using GPU [GPU Id 0 RTX 3070]
............................................
Scanning Range  0x1 : 0x1124bff742a76f92fa3a76f8f6552f
[2714579271.01 TeraKeys/s] [Elapsed 4:26][RAM n/a]

LOL  Cheesy , nice try with the speed doctoring WP.

For real though, I think the number of points is much smaller than the number of privkeys, because you can exclude invalid points on the curve when searching for xpoint.



Please guys share us the program that does 2714579271.01Tera/s
What kind of program is this? how does it search with such a very huge fast speed?
many thanks

I think it was just a prank, there is no way to make a program that can search

2714.57927101

exakeys per second.
jr. member
Activity: 37
Merit: 1
September 06, 2021, 05:03:20 AM
Please guys share us the program that does 2714579271.01Tera/s
What kind of program is this? how does it search with such a very huge fast speed?
many thanks
full member
Activity: 1162
Merit: 237
Shooters Shoot...
September 06, 2021, 01:44:38 AM
Quote
i need more explanation as i have to take down my workers and will start searching this one but i need some mathematical or logical prove for what i am searching , i can solve this i guess easily with my firepower. but really need some logic here
If you could solve it easily with your firepower, why not solve 120? This key is in a 117 bit range, so not far from 119 bit range.

you are right my dear but read my words, i didnot say that in one day or one week , 120 is hell of range , and any bit down will make some easiness so i have to believe and dream i can solve this  , but main focus is here some logic behind this key that is important
I did read your words my dearest of dears dear...you said easily, I said why not solve 120? I did not say in one day or one week. I merely said solve 120 if you can solve 117 easily.  Whatever easily is to you...I did not say what your "easily" is oh dearie deary dear of dearest dears.
jr. member
Activity: 81
Merit: 2
September 06, 2021, 01:02:41 AM
Quote
i need more explanation as i have to take down my workers and will start searching this one but i need some mathematical or logical prove for what i am searching , i can solve this i guess easily with my firepower. but really need some logic here
If you could solve it easily with your firepower, why not solve 120? This key is in a 117 bit range, so not far from 119 bit range.

you are right my dear but read my words, i didnot say that in one day or one week , 120 is hell of range , and any bit down will make some easiness so i have to believe and dream i can solve this  , but main focus is here some logic behind this key that is important
full member
Activity: 1162
Merit: 237
Shooters Shoot...
September 06, 2021, 12:29:32 AM
Quote
i need more explanation as i have to take down my workers and will start searching this one but i need some mathematical or logical prove for what i am searching , i can solve this i guess easily with my firepower. but really need some logic here
If you could solve it easily with your firepower, why not solve 120? This key is in a 117 bit range, so not far from 119 bit range.
jr. member
Activity: 81
Merit: 2
September 05, 2021, 11:35:11 PM
This is a 120 bit puzzle publick key !!!

If someone find a privkey for this pubkey in a range:

1:1124bff742a76f92fa3a76f8f6552f (decimal only 89014422443240977657631574972585263 !!! ) Range is mach less then origginal 120 Puzle range !!!

pubkey:

03c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938
02c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938

search in pubkey what start with 02 some faster than 03.

you can try any of this pubkeys.

Proof of my succes tests with another ranges and same pubkeys one what start with 03, and anower start with 02:

  • Working on Pubkey: 049fa3ea651e72c5f0a660c7ae509ad180860477283f539c918a2e43514c29da92237c8751b32e5 90883aa8bd617c60aa6b388aa78381cc7adb10046a33b038598
  • Using  [Number of CPU Threads: 3] [DP size: 10] [MaxStep: 1]
  • ............................................
  • Scanning Range  0x1 : 0x100000000000000
  • [55.22 TeraKeys/s][Kang 3072][Count 2^27.92/2^29.06][Elapsed 48s][Dead 0][RAM 25.8MB/44.7MB]
    ============== KEYFOUND ==============
    Kangaroo FOUND PrivateKey : 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbf59aefd71d64b15

  • Working on Pubkey: 049fa3ea651e72c5f0a660c7ae509ad180860477283f539c918a2e43514c29da92dc8378ae4cd1a 6f77c557429e839f5594c775587c7e338524effb95bc4fc7697
  • Using  [Number of CPU Threads: 3] [DP size: 10] [MaxStep: 1]
  • ............................................
  • Scanning Range  0x1 : 0x100000000000000
  • [42.05 TeraKeys/s][Kang 3072][Count 2^28.68/2^29.06][Elapsed 01:26][Dead 0][RAM 37.7MB/44.7MB]
    ============== KEYFOUND ==============
    Kangaroo FOUND PrivateKey : 0x0000000000000000000000000000000000000000000000000078af8f5e5ff62c
    ======================================

    We are spit 1.2 btc 50/50 after with someone who publication in this thread privkey first, all others member sorry... !!!

    Lets DO IT !!! ?Wink



i need more explanation as i have to take down my workers and will start searching this one but i need some mathematical or logical prove for what i am searching , i can solve this i guess easily with my firepower. but really need some logic here   
jr. member
Activity: 81
Merit: 2
September 05, 2021, 11:03:04 PM
little bit more example
dec 33
hex 21
pubkey 021697ffa6fd9de627c077e3d2fe541084ce13300b0bec1146f95ae57f0d0bd6a5
use your program to get 32 keys of above pubkey

you will see 0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798 in your list
one step ahead pubkey is 1.03125 ( 03bb2228d3ea32cb3c1eb160cc824a4ba8115f9a7f415d18ddcaac8193defc2c47 + 0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798  )

and in private key F7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFEC4D965FF79CE5B39E1D3CB9869B48F38
029eda0cebe3c594b59add6dccbff3347f06ad09e83e0b9279dd821cc94284c5d0

hope you will test each zone for your understand

Sorry to rain on this, but this method is useless.

I managed to decode how to split multiple keys using this method (I even made a script that reproduces your example, but it's private at the request of someone else, not that the results would be useful/practical to anyone here), and it turns out you're just using mod(32)-sized ranges.

Now as we all know, when you modinv a small number on secp256k1 you get a very large number (and modinv a "decimal number" is really just modinv(denominator) * numerator so this still holds for that)

This effectively means that the range becomes humungous, way bigger than 2^120 where we started.



The ranges look something like this (P = public key):

1*modinv(32) 2*modinv(32)     1P
2*modinv(32) 3*modinv(32)     2P
...
32*modinv(32) 33*modinv(32) (32*modinv(32) = 1)      32P

The ranges are much bigger than when you divide-and-split them down by a number.

Now of course you can replace 32 with an extremely huge number to make the ranges manageable/smaller but what's the point? Now you have an unmanageable amount of public keys.

i guess we need to figure out how to make range small , as if we use some techniques and range will get bigger and bigger no one is going to beat that as with each bit increment you need to pay your 100 of life's hahahah  Grin
Pages:
Jump to: