Post
Topic
Board Development & Technical Discussion
Re: Solving ECDLP with Kangaroos: Part 1 + 2 + RCKangaroo
by
zahid888
on 20/12/2024, 21:20:56 UTC
v2.0 (Windows/Linux):
https://github.com/RetiredC/RCKangaroo

- added support for 30xx, 20xx and 1xxx cards.
- some minor changes.

Speed:
4090 - 7.9GKeys/s.
3090 - 4.1GKeys/s.
2080Ti - 2.9GKeys/s.

Please report speed for other cards, for old cards speedup is up to 40%.
Code:
RCKangaroo_v20>RCKangaroo.exe -dp 16 -range 74 -start 4000000000000000000 -pubkey 03726b574f193e374686d8e12bc6e4142adeb06770e0a2856f5e4ad89f66044755
********************************************************************************
*                    RCKangaroo v2.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
Windows version
CUDA devices: 1, CUDA driver/runtime: 12.7/12.6
GPU 0: NVIDIA GeForce RTX 3060 Ti, 8.00 GB, 38 CUs, cap 8.6, PCI 1, L2 size: 3072 KB
Total GPUs for work: 1

MAIN MODE

Solving public key
X: 726B574F193E374686D8E12BC6E4142ADEB06770E0A2856F5E4AD89F66044755
Y: 9B15322E6707090A4DB3F09C7E6632A26DB57F03EB07B40979FC01C827E1B0A3
Offset: 0000000000000000000000000000000000000000000004000000000000000000

Solving point: Range 74 bits, DP 16, start...
SOTA method, estimated ops: 2^37.202, RAM for DPs: 0.277 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 1.937. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3669 MB, 1245184 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2067 MKeys/s, Err: 0, DPs: 304K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 2100 MKeys/s, Err: 0, DPs: 626K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 2096 MKeys/s, Err: 0, DPs: 930K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 2090 MKeys/s, Err: 0, DPs: 1253K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 2083 MKeys/s, Err: 0, DPs: 1575K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 2083 MKeys/s, Err: 0, DPs: 1897K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 2079 MKeys/s, Err: 0, DPs: 2220K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 2079 MKeys/s, Err: 0, DPs: 2523K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
Stopping work ...
Point solved, K: 1.277 (with DP and GPU overheads)


PRIVATE KEY: 0000000000000000000000000000000000000000000004C5CE114686A1336E07
Managed to crack a 74-bit private key in less than a minute using one 3060 Ti!

Now, the real question: Is it worth running this occasionally to attempt a 135-bit private key?
Would it still work purely on sequence, or is there a way to incorporate randomness to test our luck with this blazing performance?

Looking forward to hearing your reply!