Solving ECDLP with Kangaroos: Part 1 + 2 + RCKangaroo

[WanderingPhilospher]

Hello, I'm a little bit stupid. Maybe someone is able to help me.

I want to try the RCKangaroo.exe first with a know puzzle.
I tried
# Puzzle 22
# Adresse: 1CfZWK1QTQE3eS9qn61dQjV89KDjZzfNcv
# puplic key: 023ed96b524db5ff4fe007ce730366052b7c511dc566227d929070b9ce917abb43
# Start: 200000 Ende: 3fffff

First, which range should I use? This is not clear for me. So to what does it depend?

With the following it works, but needs a long time on my RTX 3060 Ti
RCKangaroo.exe -dp 16 -range 74 -start 200000 -pubkey 023ed96b524db5ff4fe007ce730366052b7c511dc566227d929070b9ce917abb43

And that secound, where to get the puplic key?
I mean for example for puzzle 67 it is not known.
Or how must the commandline must look for puzzle 67? Or is not possible to solve it with this programm?

Thanks a lot.

You say that is puzzle 22 but you are using a range size of 74. Try this:

RCKangaroo.exe -dp 16 -range 21 -start 100000 -pubkey 023ed96b524db5ff4fe007ce730366052b7c511dc566227d929070b9ce917abb43

See if that speeds it up for you.

[HansiPeter]

This do not work.
I get an error: error: invalid value for -range option

With puzzle 22 I mean the 22. from this side: https://privatekeys.pw/puzzles/bitcoin-puzzle-tx

I thoght that everyone is talking about it, because RetiredCoder solves some for the puzzles from there, 120 for exsample.

And the other point is still, where to get the public key. Because for 67 we only have the Bitcoin adress: 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 and the public hash 160: 739437bb3dd6d1983e66629c5f08c70e52769371
see also: https://privatekeys.pw/address/bitcoin/1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9

[WanderingPhilospher]

This do not work.
I get an error: error: invalid value for -range option

With puzzle 22 I mean the 22. from this side: https://privatekeys.pw/puzzles/bitcoin-puzzle-tx

I thoght that everyone is talking about it, because RetiredCoder solves some for the puzzles from there, 120 for exsample.

And the other point is still, where to get the public key. Because for 67 we only have the Bitcoin adress: 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 and the public hash 160: 739437bb3dd6d1983e66629c5f08c70e52769371
see also: https://privatekeys.pw/address/bitcoin/1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9

Per the source:

-range   bit range of private the key. Mandatory if "-pubkey" option is specified. For example, for puzzle #85 bit range is "84" (84 bits). Must be in range 32...170.

So it has to be at least 32.

As far as wanting to know the public key for 67...don't we all, don't we all.

[MrGPBit]

@RetiredCoder

Maybe you can fix these warnings in the next update

Code:

utils.cpp:246:38: warning: ignoring return value of ‘size_t fread(void*, size_t, size_t, FILE*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  246 |                                 fread(&list->cnt, 1, 2, fp);
      |                                 ~~~~~^~~~~~~~~~~~~~~~~~~~~~

[leaguerd]

Could you please explain why the code doesn't work when the generator point changes? I'm very interested in experimenting with different generators. Can you assist me with this?

[COBRAS]

Could you please explain why the code doesn't work when the generator point changes? I'm very interested in experimenting with different generators. Can you assist me with this?

Are you saying that you are changing the value of Generator (G) and it is not working?

https://github.com/RetiredC/RCKangaroo/blob/main/Ec.cpp#L113-L114

Bitcoin uses secp256k1, so the G should be what is defined to be: https://en.bitcoin.it/wiki/Secp256k1

G point is the following:
(compressed form): 0279BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F81798
(uncompressed form): 0479BE667EF9DCBBAC55A06295CE870B07029BFCDB2DCE28D959F2815B16F81798483ADA7726A3C 4655DA4FBFC0E1108A8FD17B448A68554199C47D08FFB10D4B8

Not work for pubkey what not divides to G, for exp pubkey 5 and basepoint 2

[leaguerd]

For example, I would like to use N/2x as the Generator base. so, Gx=(N/2)x ,2P= Gx,  3P=.....,and so on.

[mjojo]

Code:

@ 2 x 4090 ( hit key in 5 minutes)
84 bits 

./rckangaroo -dp 16 -range 84 -start 1000000000000000000000 -pubkey 0329c4574a4fd8c810b7e42a4b398882b381bcd85e40c6883712912d167c83e73a


Solving public key
X: 29C4574A4FD8C810B7E42A4B398882B381BCD85E40C6883712912D167C83E73A
Y: 0E02C3AFD79913AB0961C95F12498F36A72FFA35C93AF27CEE30010FA6B51C53
Offset: 0000000000000000000000000000000000000000001000000000000000000000

Solving point: Range 84 bits, DP 16, start...
SOTA method, estimated ops: 2^42.202, RAM for DPs: 3.062 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 49.067.
GPU 0: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 1: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPUs started...
MAIN: Speed: 15961 MKeys/s, Err: 0, DPs: 2364K/77175K, Time: 0d:00h:00m/0d:00h:05m
MAIN: Speed: 15915 MKeys/s, Err: 0, DPs: 4798K/77175K, Time: 0d:00h:00m/0d:00h:05m
MAIN: Speed: 15885 MKeys/s, Err: 0, DPs: 7234K/77175K, Time: 0d:00h:00m/0d:00h:05m
MAIN: Speed: 15830 MKeys/s, Err: 0, DPs: 9656K/77175K, Time: 0d:00h:00m/0d:00h:05m
MAIN: Speed: 15820 MKeys/s, Err: 0, DPs: 12069K/77175K, Time: 0d:00h:00m/0d:00h:05m
MAIN: Speed: 15800 MKeys/s, Err: 0, DPs: 14491K/77175K, Time: 0d:00h:01m/0d:00h:05m
MAIN: Speed: 15643 MKeys/s, Err: 0, DPs: 64810K/77175K, Time: 0d:00h:04m/0d:00h:05m
MAIN: Speed: 15677 MKeys/s, Err: 0, DPs: 67210K/77175K, Time: 0d:00h:04m/0d:00h:05m
MAIN: Speed: 15643 MKeys/s, Err: 0, DPs: 69611K/77175K, Time: 0d:00h:04m/0d:00h:05m
MAIN: Speed: 15672 MKeys/s, Err: 0, DPs: 71997K/77175K, Time: 0d:00h:05m/0d:00h:05m
Stopping work ...
Point solved, K: 1.079 (with DP and GPU overheads)


PRIVATE KEY: 00000000000000000000000000000000000000000011720C4F018D51B8CEBBA8

Code:

@ 2 x 4090 ( hit key in 20 minutes)
90 bits

./rckangaroo -dp 16 -range 90 -start 1000000000000000000000 -pubkey 035c38bd9ae4b10e8a250857006f3cfd98ab15a6196d9f4dfd25bc7ecc77d788d5

035c38bd9ae4b10e8a250857006f3cfd98ab15a6196d9f4dfd25bc7ecc77d788d5

MAIN: Speed: 15668 MKeys/s, Err: 0, DPs: 201518K/617401K, Time: 0d:00h:14m/0d:00h:43m
MAIN: Speed: 15683 MKeys/s, Err: 0, DPs: 203915K/617401K, Time: 0d:00h:14m/0d:00h:42m
MAIN: Speed: 15697 MKeys/s, Err: 0, DPs: 206312K/617401K, Time: 0d:00h:14m/0d:00h:42m
MAIN: Speed: 15667 MKeys/s, Err: 0, DPs: 208708K/617401K, Time: 0d:00h:14m/0d:00h:43m
MAIN: Speed: 15664 MKeys/s, Err: 0, DPs: 211107K/617401K, Time: 0d:00h:14m/0d:00h:43m
MAIN: Speed: 15687 MKeys/s, Err: 0, DPs: 213507K/617401K, Time: 0d:00h:14m/0d:00h:42m
MAIN: Speed: 15702 MKeys/s, Err: 0, DPs: 292648K/617401K, Time: 0d:00h:20m/0d:00h:42m
MAIN: Speed: 15697 MKeys/s, Err: 0, DPs: 295048K/617401K, Time: 0d:00h:20m/0d:00h:42m
MAIN: Speed: 15697 MKeys/s, Err: 0, DPs: 297447K/617401K, Time: 0d:00h:20m/0d:00h:42m
MAIN: Speed: 15702 MKeys/s, Err: 0, DPs: 299847K/617401K, Time: 0d:00h:20m/0d:00h:42m
Stopping work ...
Point solved, K: 0.560 (with DP and GPU overheads)


PRIVATE KEY: 000000000000000000000000000000000000000002CE00BB2136A445C71E85BF

Code:

@ 4 x 4090 but fail (DP 16 and DP 32)
100 bits

03d2063d40402f030d4cc71331468827aa41a8a09bd6fd801ba77fb64f8e67e617
./rckangaroo -dp 32 -range 100 -start 1000000000000000000000 -pubkey 03d2063d40402f030d4cc71331468827aa41a8a09bd6fd801ba77fb64f8e67e617

MAIN: Speed: 30150 MKeys/s, Err: 0, DPs: 1221653K/19756849K, Time: 0d:00h:44m/0d:11h:55m
MAIN: Speed: 30160 MKeys/s, Err: 0, DPs: 1226261K/19756849K, Time: 0d:00h:44m/0d:11h:55m
MAIN: Speed: 30148 MKeys/s, Err: 0, DPs: 1230877K/19756849K, Time: 0d:00h:44m/0d:11h:55m
MAIN: Speed: 30140 MKeys/s, Err: 0, DPs: 1235494K/19756849K, Time: 0d:00h:44m/0d:11h:55m
MAIN: Speed: 30153 MKeys/s, Err: 0, DPs: 1240126K/19756849K, Time: 0d:00h:44m/0d:11h:55m
MAIN: Speed: 30131 MKeys/s, Err: 0, DPs: 1244850K/19756849K, Time: 0d:00h:45m/0d:11h:56m
MAIN: Speed: 30144 MKeys/s, Err: 0, DPs: 1249601K/19756849K, Time: 0d:00h:45m/0d:11h:55m
MAIN: Speed: 30156 MKeys/s, Err: 0, DPs: 1254460K/19756849K, Time: 0d:00h:45m/0d:11h:55m
MAIN: Speed: 30144 MKeys/s, Err: 0, DPs: 1259068K/19756849K, Time: 0d:00h:45m/0d:11h:55m
MAIN: Speed: 30162 MKeys/s, Err: 0, DPs: 1263747K/19756849K, Time: 0d:00h:45m/0d:11h:55m
MAIN: Speed: 30144 MKeys/s, Err: 0, DPs: 1268496K/19756849K, Time: 0d:00h:45m/0d:11h:55m
MAIN: Speed: 30167 MKeys/s, Err: 0, DPs: 1273295K/19756849K, Time: 0d:00h:46m/0d:11h:55m
MAIN: Speed: 30136 MKeys/s, Err: 0, DPs: 1278176K/19756849K, Time: 0d:00h:46m/0d:11h:56m
MAIN: Speed: 30141 MKeys/s, Err: 0, DPs: 1282829K/19756849K, Time: 0d:00h:46m/0d:11h:55m
MAIN: Speed: 30141 MKeys/s, Err: 0, DPs: 1287745K/19756849K, Time: 0d:00h:46m/0d:11h:55m
MAIN: Speed: 30123 MKeys/s, Err: 0, DPs: 1292540K/19756849K, Time: 0d:00h:46m/0d:11h:56m
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
MAIN: Speed: 30144 MKeys/s, Err: 0, DPs: 1297134K/19756849K, Time: 0d:00h:46m/0d:11h:55m
DPs buffer overflow, some points lost, increase DP value!

Code:

@ 8 x 4090 but fail (DP 18)
100 bits

DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
MAIN: Speed: 62716 MKeys/s, Err: 0, DPs: 4464433K/4939212K, Time: 0d:05h:13m/0d:05h:44m

[minobia]

I created a Discord Server just in case someone needs more in depth help.

There is a channel to share files and scripts!

https://discord.gg/eEQbQnnRaY

[karrask]

@RetiredCoder, do You plan any other minipuzzles (or maxi) in the future? Let us know "when", if You plan something, please

I don't plan them in advance, but anyway here is another one:
https://bitcointalk.org/index.php?topic=5526453.0

Good afternoon! when the program starts, the number of kangaroos is displayed, 1548806? does each scan its segment sequentially at a rate of 2.3 million per second? Did you get it right, or was there a mistake somewhere?

[Shelby0901]

Hello, I previously asked you a question about adding the -end search range function, you answered me why you are not satisfied with -range .. I will answer why if I am looking for a 130 puzzle, then -range 84 will search where the zeros are in this example -dp 16 -range 84 -start 33e7665705350000000000000000000000 but nothing more right?) and what I mean is that with the -end function I can break the same 135 puzzle into a dozen or a hundred pieces and search throughout -range 134 but with short distances as an example -range 134 -start 6d9999999999999999999999999999996 -end 7ffffffffffffffffffffffffffff I can calculate the work here, let’s say that I would go through one path in one day and the next day start another path, but only with the start I can’t do this because I don’t know where this path ended if I turn off the program in other words, -end is needed so that you can start with it later) but with -range this is not possible

Your idea sounds senseless for me, but anyway it's open-source so you can modify sources and implement all ideas you have.

Can you confirm that you are using the code from Jean Luc here: https://github.com/JeanLucPons/Kangaroo ?

You can download both sources and compare, my code is not related to JLP's code.

I'm really interested, and for us beginners, it would be super helpful to have a detailed tutorial explaining how you set it up from start to finish

I won't write articles like "step-by-step guide how to crack #135", sorry  

What about little bit of clues 😬@RetiredCoder

[mjojo]

Code:

root@C.17267517:~/RCKangaroo$ ./rckangaroo -dp 16 -range 95 -start 800000000000000000000000 -pubkey 026457b0abb3a7dda004e1c3200e88a194a26079773cca28056306558ff57316b6
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 1, L2 size: 73728 KB
GPU 1: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 70, L2 size: 73728 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: 6457B0ABB3A7DDA004E1C3200E88A194A26079773CCA28056306558FF57316B6
Y: 5E3AF26441EE207F5306B17AA0A078378B1B977E08E69FEE1D67EF4D3454F618
Offset: 0000000000000000000000000000000000000000800000000000000000000000

Solving point: Range 95 bits, DP 16, start...
SOTA method, estimated ops: 2^47.702, RAM for DPs: 130.295 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 2220.504.
GPU 0: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 1: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPUs started...
MAIN: Speed: 16266 MKeys/s, Err: 0, DPs: 2411K/3492550K, Time: 0d:00h:00m/0d:03h:54m
MAIN: Speed: 16261 MKeys/s, Err: 0, DPs: 4895K/3492550K, Time: 0d:00h:00m/0d:03h:54m
MAIN: Speed: 16198 MKeys/s, Err: 0, DPs: 7377K/3492550K, Time: 0d:00h:00m/0d:03h:55m
MAIN: Speed: 16177 MKeys/s, Err: 0, DPs: 9859K/3492550K, Time: 0d:00h:00m/0d:03h:55m
MAIN: Speed: 13378 MKeys/s, Err: 0, DPs: 1738022K/3492550K, Time: 0d:02h:08m/0d:04h:45m
MAIN: Speed: 13364 MKeys/s, Err: 0, DPs: 1740073K/3492550K, Time: 0d:02h:08m/0d:04h:45m
MAIN: Speed: 13374 MKeys/s, Err: 0, DPs: 1742114K/3492550K, Time: 0d:02h:08m/0d:04h:45m
MAIN: Speed: 13356 MKeys/s, Err: 0, DPs: 1744167K/3492550K, Time: 0d:02h:08m/0d:04h:45m
Stopping work ...
Point solved, K: 0.575 (with DP and GPU overheads)


PRIVATE KEY: 0000000000000000000000000000000000000000AC327FD28ABC09372827384B

[WanderingPhilospher]

@ 8 x 4090 but fail (DP 18)
100 bits

DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
DPs buffer overflow, some points lost, increase DP value!
MAIN: Speed: 62716 MKeys/s, Err: 0, DPs: 4464433K/4939212K, Time: 0d:05h:13m/0d:05h:44m

I wasn't sure if you reran this or not or figured out what the issue was.
I ran a 100 bit test (99 bits) and it did find the key:

Code:

~$ ./rckangaroo -dp 24 -range 8000000000000000000000000:fffffffffffffFFFFFFFFFFFF -pubkey 024ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
Start Range: 000000000000000000000008000000000000000000000000
End   Range: 00000000000000000000000fffffffffffffffffffffffff
Bits: 99
CUDA devices: 8, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 1, L2 size: 73728 KB
GPU 1: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 65, L2 size: 73728 KB
GPU 2: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 98, L2 size: 73728 KB
GPU 3: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 129, L2 size: 73728 KB
GPU 4: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 161, L2 size: 73728 KB
GPU 5: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 193, L2 size: 73728 KB
GPU 6: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 194, L2 size: 73728 KB
GPU 7: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 225, L2 size: 73728 KB
Total GPUs for work: 8

MAIN MODE

Solving public key
X: 4ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9
Y: 77621A8FCABAD9A502611EBB502359CE874065C1D0F5AF246028B38545B8990A
Offset: 0000000000000000000000000000000000000008000000000000000000000000

Solving point: Range 99 bits, DP 24, start...
SOTA method, estimated ops: 2^49.702, RAM for DPs: 2.220 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 8.674.
GPU 0: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 1: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 2: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 3: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 4: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 5: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 6: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 7: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPUs started...
MAIN: Speed: 59748 MKeys/s, Err: 0, DPs: 37036K/54571K, Time: 0d:02h:54m:38s/0d:04h:15m:23s

Stopping work ...
Total Time: 2 hours, 54 minutes, 41 seconds
Point solved, K: 0.781 (with DP and GPU overheads)


PRIVATE KEY: 000000000000000000000000000000000000000F4A21B9F5CE114686A1336E07

So we know it works. But why didn't it work for you? DP size?

[mjojo]

Code:

~$ ./rckangaroo -dp 24 -range 8000000000000000000000000:fffffffffffffFFFFFFFFFFFF -pubkey 024ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
Start Range: 000000000000000000000008000000000000000000000000
End   Range: 00000000000000000000000fffffffffffffffffffffffff
Bits: 99
CUDA devices: 8, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 1, L2 size: 73728 KB
GPU 1: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 65, L2 size: 73728 KB
GPU 2: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 98, L2 size: 73728 KB
GPU 3: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 129, L2 size: 73728 KB
GPU 4: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 161, L2 size: 73728 KB
GPU 5: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 193, L2 size: 73728 KB
GPU 6: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 194, L2 size: 73728 KB
GPU 7: NVIDIA GeForce RTX 4090, 23.64 GB, 128 CUs, cap 8.9, PCI 225, L2 size: 73728 KB
Total GPUs for work: 8

MAIN MODE

Solving public key
X: 4ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9
Y: 77621A8FCABAD9A502611EBB502359CE874065C1D0F5AF246028B38545B8990A
Offset: 0000000000000000000000000000000000000008000000000000000000000000

Solving point: Range 99 bits, DP 24, start...
SOTA method, estimated ops: 2^49.702, RAM for DPs: 2.220 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 8.674.
GPU 0: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 1: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 2: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 3: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 4: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 5: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 6: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPU 7: allocated 2394 MB, 786432 kangaroos. OldGpuMode: No
GPUs started...
MAIN: Speed: 59748 MKeys/s, Err: 0, DPs: 37036K/54571K, Time: 0d:02h:54m:38s/0d:04h:15m:23s

Stopping work ...
Total Time: 2 hours, 54 minutes, 41 seconds
Point solved, K: 0.781 (with DP and GPU overheads)


PRIVATE KEY: 000000000000000000000000000000000000000F4A21B9F5CE114686A1336E07

Hai Wander, did you modify or change the code in your test?

[WanderingPhilospher]

Hai Wander, did you modify or change the code in your test?

I changed how the program receives its info, and some cosmetic stuff.

Basically, you enter a start and end range, start:end, the program calculates the difference and from that, the bit size of the range. Since we entered the start range, this is passed as the old offset flag.
So all of that is automatic now.

./rckangaroo -dp 24 -range 8000000000000000000000000:fffffffffffffFFFFFFFFFFFF -pubkey 024ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9

is all you have to enter now.

And I got rid of the repeating lines and just kept them on a single line. And I added a start/finish timer.

So while I did tweak a few things, I did not touch the actual Kangaroo parts of the program; no math or jumps or any of that. This way I could test if the program had issues or was user error, maybe the cause.

[mjojo]

Hai Wander, did you modify or change the code in your test?

I changed how the program receives its info, and some cosmetic stuff.

Basically, you enter a start and end range, start:end, the program calculates the difference and from that, the bit size of the range. Since we entered the start range, this is passed as the old offset flag.
So all of that is automatic now.

./rckangaroo -dp 24 -range 8000000000000000000000000:fffffffffffffFFFFFFFFFFFF -pubkey 024ECC524F1F53F525A7224364A4290BA97D72298D885FCF93B6E139E802B421B9

is all you have to enter now.

And I got rid of the repeating lines and just kept them on a single line. And I added a start/finish timer.

So while I did tweak a few things, I did not touch the actual Kangaroo parts of the program; no math or jumps or any of that. This way I could test if the program had issues or was user error, maybe the cause.

Ok thank for the explaining, so far what maximum bits did you test and success?

[kTimesG]

Code:

./RCKangaroo
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 1, CUDA driver/runtime: 12.8/12.5
GPU 0: NVIDIA GeForce RTX 5090, 31.36 GB, 170 CUs, cap 12.0, PCI 33, L2 size: 98304 KB
Total GPUs for work: 1

BENCHMARK MODE

Solving point: Range 78 bits, DP 16, start...
SOTA method, estimated ops: 2^39.202, RAM for DPs: 0.547 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 9.236.
GPU 0: allocated 3176 MB, 1044480 kangaroos. OldGpuMode: No
GPUs started...
BENCH: Speed: 9393 MKeys/s, Err: 0, DPs: 2848K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9382 MKeys/s, Err: 0, DPs: 4281K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9351 MKeys/s, Err: 0, DPs: 5713K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9340 MKeys/s, Err: 0, DPs: 7147K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9294 MKeys/s, Err: 0, DPs: 8565K/9646K, Time: 0d:00h:01m/0d:00h:01m
BENCH: Speed: 9294 MKeys/s, Err: 0, DPs: 9983K/9646K, Time: 0d:00h:01m/0d:00h:01m
Stopping work ...
Point solved, K: 1.345 (with DP and GPU overheads)

Points solved: 1, average K: 1.345 (with DP and GPU overheads)

Solving point: Range 78 bits, DP 16, start...
SOTA method, estimated ops: 2^39.202, RAM for DPs: 0.547 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 9.236.
GPU 0: allocated 3176 MB, 1044480 kangaroos. OldGpuMode: No
GPUs started...
BENCH: Speed: 9294 MKeys/s, Err: 0, DPs: 1386K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9289 MKeys/s, Err: 0, DPs: 2805K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9294 MKeys/s, Err: 0, DPs: 4222K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9258 MKeys/s, Err: 0, DPs: 5638K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9258 MKeys/s, Err: 0, DPs: 7056K/9646K, Time: 0d:00h:00m/0d:00h:01m
BENCH: Speed: 9309 MKeys/s, Err: 0, DPs: 8474K/9646K, Time: 0d:00h:01m/0d:00h:01m
BENCH: Speed: 9289 MKeys/s, Err: 0, DPs: 9909K/9646K, Time: 0d:00h:01m/0d:00h:01m
Stopping work ...
Point solved, K: 1.320 (with DP and GPU overheads)

Points solved: 2, average K: 1.333 (with DP and GPU overheads)

...

Points solved: 7, average K: 1.734 (with DP and GPU overheads)

Hypotetical scenario: a RTX 5090 can do at least 13.0 G jumps/s at DP 32. Are there plans to improve RCKangaroo or is 9.3 Gk/s still a "very good" speed, compared to an optimized version?

I am disappointed in the 5090 so far, I only got at most a 20% speed up compared to 4090.

[RetiredCoder]

Hypotetical scenario: a RTX 5090 can do at least 13.0 G jumps/s at DP 32. Are there plans to improve RCKangaroo or is 9.3 Gk/s still a "very good" speed, compared to an optimized version?

In general, I'm not interested in further support/improvements of RCKangaroo, but since it's open-source, someone else can do it.
My original goal was to share my method of solving ECDLP with best K.
I did it, but people (and you too btw) said that K is calculated incorrectly, also my method will not work in practice because loops cannot be handled properly and my method worked for puzzles only because I burned tons of money and any method is good in this case. So I also created RCKangaroo for 4090 to demonstrate that loops can be handled efficiently and K=1.15 is real.
Then people tried to run it on old cards so I had to support old cards too (and also to prove that loops can be handled efficiently on any GPU).
Right now RCKangaroo uses the fastest method for solving ECDLP ever, and also it's the fastest open-source GPU solver, so I think it's still good enough for open-source.
Yes sometimes you say that you have magic non-looping method with K=1 (DP>0) or that you have faster jumps like 13Gkeys/s, but it's just words, nobody can test or use it. Sometimes here I see funny messages like "I have broken EC" or "I solved all puzzles" 
At this moment, I have demonstrated and proved everything I want and now I'm busy with another interesting project.

[kTimesG]

Hypotetical scenario: a RTX 5090 can do at least 13.0 G jumps/s at DP 32. Are there plans to improve RCKangaroo or is 9.3 Gk/s still a "very good" speed, compared to an optimized version?

In general, I'm not interested in further support/improvements of RCKangaroo, but since it's open-source, someone else can do it.

Thank you for taking time to respond!

While I do admire that you had the skills and resources to break three ECDLP problems in a row, judging by your expertise you know very well that everything is a tradeoff when it comes to programming. I still stand by all my previous comments regarding this: cycle handling slows down the jumps. Another way to view this is: even with a very fast optimized cycle-handling kernel such as yours (much faster than some whatever JLP reference fork), it can be made to run faster if we trade the resources for cycle handling to enabling more jumps. The question at the end of the day is: from what point on is it worth it to either have low "K" with slow jumps, or a higher "K" with faster jumps. And yes, I did manage to reach 13.4 G/s on a RTX 5090 without even compiling natively to ccap 12.0, so the question is even more interesting now.

I was more interested about one of your older replies, regarding the fact that an optimized version is not even twice as fast as RCKang, which hinted that maybe somehow you managed to reach 14 Go/s on a RTX 4090, which would have been fascinating, considering that the public version can't reach 8 G/s.

[RetiredCoder]

Thank you for taking time to respond!

While I do admire that you had the skills and resources to break three ECDLP problems in a row, judging by your expertise you know very well that everything is a tradeoff when it comes to programming. I still stand by all my previous comments regarding this: cycle handling slows down the jumps. Another way to view this is: even with a very fast optimized cycle-handling kernel such as yours (much faster than some whatever JLP reference fork), it can be made to run faster if we trade the resources for cycle handling to enabling more jumps. The question at the end of the day is: from what point on is it worth it to either have low "K" with slow jumps, or a higher "K" with faster jumps. And yes, I did manage to reach 13.4 G/s on a RTX 5090 without even compiling natively to ccap 12.0, so the question is even more interesting now.

I was more interested about one of your older replies, regarding the fact that an optimized version is not even twice as fast as RCKang, which hinted that maybe somehow you managed to reach 14 Go/s on a RTX 4090, which would have been fascinating, considering that the public version can't reach 8 G/s.

Currently I have about 12.8GKeys/s on 4090. 5090 is a shame, I skip it and wait for next generation.
Perhaps I will make all my sources public when #135 is solved, though I'm not sure, people are not interested in what I do, also I see zero good discussions on this forum about EC, so better I will spend my time for more interesting things