Topic: Pollard's kangaroo ECDLP solver - page 37. (Read 60381 times)
I apologize in advance for asking, but is it possible to check which of two points is greater? k number of one point is known.
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
lol , i read what you say and understand as well , just i asked if you like to share send me codes so will try to fix bug and do optimization ,
same here bro, will test and share, and prolly you will put it up on git to, like vanbitcrackn,
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
lol , i read what you say and understand as well , just i asked if you like to share send me codes so will try to fix bug and do optimization ,
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
Try run your cangaroo again, and you find 85 bit. Kangaroo and BSGS some time need run again for find a key as show my practice.
All is well, we will find 120 at the pool...
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
Try run your cangaroo again, and you find 85 bit. Kangaroo and BSGS some time need run again for find a key as show my practice.
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
Try my pubkeys....
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
looks good , can i have hand on program? , maybe can help in some optimization
A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.
CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.
i know private key of this pub but cant take money out 
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
its 0 as a.a said
with PK 020000000000000000000000000000000000000000000000000000000000000000 ~ 350USD there waiting for you 
SexObIllo
, find privkey for this and I give you 0.6 Btc ??1:124bff742a76f92fa3a76f8f6552f
0313ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f
0213ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f
1124bff742a76f92fa3a76f8f6552f
124bff742a76f92fa3a76f8f6552f taking out 100000000000000000000000000000 does not mean your calculations are precise
Dude , you posted before different key and now different ~ do you actually have any idea what you are doing lol . provide a logic behind it and i will use my all 3 rigs to solve it
i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
its 0 as a.a said
with PK 020000000000000000000000000000000000000000000000000000000000000000 ~ 350USD there waiting for you SexObIllo
, find privkey for this and I give you 0.6 Btc ??1:124bff742a76f92fa3a76f8f6552f
0313ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f
0213ee32399b1441d0c8cf7caf6d10641b30d280fe1b59fcaa09eb0326cad5cb6f
i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
its 0 as a.a said
with PK 020000000000000000000000000000000000000000000000000000000000000000 ~ 350USD there waiting for you i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
its 0 as a.a said
i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
its 0 as a.a said
The privatekey for 020000000000000000000000000000000000000000000000000000000000000000 is 0
It is invalid as secp256k1 is starting with 1 and not 0.
It is invalid as secp256k1 is starting with 1 and not 0.
i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
Can't write to PM020000000000000000000000000000000000000000000000000000000000000000
If it's not a secret, what is the private key of this public key? Me not for money, but for understanding curves. You can at PM
...
If you guys are using the same program that Cobras showed in his post, especially the Kangaroo one, it doesn't matter what speed the program shows, it is not that fast. It only searches x bits per round. I mean it's python code with some back .dll code. Do a search in the 52 bit range, middle of the range, say pub key 02B2FE98A1DCF9906C103ADEABB4EFEE7DBD7B74BA985838B0F34041EF225C5C58
Now run the same test using Jean Luc's Kangaroo or BSGS with 4 CPU threads only; I guarantee you, JLPs Kangaroo version will be thousands of times faster even though the speed on the screen says it's slower. Again, it's all in what the coder deems as a hash, or checked key. But side by side comparison tests shows the true speed. People may feel that a program is faster because of what the program shows the speed is but facts do not care about feelings...
If you guys are using the same program that Cobras showed in his post, especially the Kangaroo one, it doesn't matter what speed the program shows, it is not that fast. It only searches x bits per round. I mean it's python code with some back .dll code. Do a search in the 52 bit range, middle of the range, say pub key 02B2FE98A1DCF9906C103ADEABB4EFEE7DBD7B74BA985838B0F34041EF225C5C58
Now run the same test using Jean Luc's Kangaroo or BSGS with 4 CPU threads only; I guarantee you, JLPs Kangaroo version will be thousands of times faster even though the speed on the screen says it's slower. Again, it's all in what the coder deems as a hash, or checked key. But side by side comparison tests shows the true speed. People may feel that a program is faster because of what the program shows the speed is but facts do not care about feelings...
I agree completely. I have tested different versions as well. The kangaroo is much faster, no matter what the numbers show.
p.s. This is a real keyreyt for this day -
1,5 QADRILION/SEC
1,5 QADRILION/SEC
lol , bro chill out my one rig i9 10850k + 128GB 3600 over clocked ram , is giving me 9.897 QADRILION/SEC
, i know now you guys will ask prove well i am out from home so i will post here later today ~ :-*Math 
Now run the same test using Jean Luc's Kangaroo or BSGS with 4 CPU threads only; I guarantee you, JLPs Kangaroo version will be thousands of times faster even though the speed on the screen says it's slower. Again, it's all in what the coder deems as a hash, or checked key. But side by side comparison tests shows the true speed. People may feel that a program is faster because of what the program shows the speed is but facts do not care about feelings...
i know private key of this pub but cant take money out
020000000000000000000000000000000000000000000000000000000000000000
020000000000000000000000000000000000000000000000000000000000000000
i actually could not find the program that show quadrillion readout, all his current git version show trillion
so probably an older version, showing 20000000000000000 is 20.00000 quadrillion in 12 sec. on cpu,
Search Range: 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffffff
PVK not found. 20000.00000 Trillion scanned in 12.01 sec. New range
and why i mean this range 1:
1124bff742a76f92fa3a76f8f6552f (decimal only 89014422443240977657631574972585263 !!! ) bits ?
100000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFF
on 03c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938
key 117 bit?
so probably an older version, showing 20000000000000000 is 20.00000 quadrillion in 12 sec. on cpu,
Search Range: 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffffff
PVK not found. 20000.00000 Trillion scanned in 12.01 sec. New range
and why i mean this range 1:
1124bff742a76f92fa3a76f8f6552f (decimal only 89014422443240977657631574972585263 !!! ) bits ?
100000000000000000000000000
1FFFFFFFFFFFFFFFFFFFFFFFFFF
on 03c95ba9e6a637e739d13a6d036507ecc37a70c26e68ac7e5f157268311c6c3938
key 117 bit?
I dont calculaye how many exact bits this 1:1124bff742a76f92fa3a76f8f6552f range, and privkey not on upper of this range, start and you crack faster then you come to 1124bff742a76f92fa3a76f8f6552f.
Wonder not found privkey I think, hi is only trolling a little.
Jump to: