Search content
Sort by
Showing 20 of 131 results by Lolo54
Re: How many CPUs/GPUs needed to crack Bitcoin Puzzle 71 and 135 in 1 day?
To keep things simple without going into technical details and exhausting calculations for
71
--> the range comprises 1180591620717411303423 addresses to be scanned. It all depends on where the target address is located in this range, but if we assume that it's at the end, it would take almost 2 million 4090 GPUs to reach it in 24 hours. If the target is in the middle of the range, let's say that 1 million GPU 4090s would suffice
with GPU 5090s, let's say that this number would require around 20% fewer GPUs, i.e. 1M5 or 750K
This is using Bitcrack or Vanitysearch, perfectly optimized for the system used.
For the 135 it's different insofar as the pubkey is available, the tools and speed are also different, but the difficulty is just as great. RetiredCoder's RCKangaroo, which was perfectly optimized for its configuration (i.e. over 12GK/s for the 130é), took 2 months to achieve this using 400 GPU 3090s, with the target at 62% of the range. In 1 day, we would have needed almost 60 times as many 3090 GPUs, say at least 24,000 RTX 3090 GPUs.
For the 135th, the search space is more than 30 times larger, so we'd need at least 750k GPUs 3090 to get there in 24 hours, if the target is 60% of the range, using software perfectly optimized to run on such a configuration.
Whether it's the 71st or the 135th, the difficulty of getting there is roughly the same, even if the software or the way of doing it is different, since for one the pubkey is known. We wish you good luck.
71
--> the range comprises 1180591620717411303423 addresses to be scanned. It all depends on where the target address is located in this range, but if we assume that it's at the end, it would take almost 2 million 4090 GPUs to reach it in 24 hours. If the target is in the middle of the range, let's say that 1 million GPU 4090s would suffice
with GPU 5090s, let's say that this number would require around 20% fewer GPUs, i.e. 1M5 or 750K
This is using Bitcrack or Vanitysearch, perfectly optimized for the system used.
For the 135 it's different insofar as the pubkey is available, the tools and speed are also different, but the difficulty is just as great. RetiredCoder's RCKangaroo, which was perfectly optimized for its configuration (i.e. over 12GK/s for the 130é), took 2 months to achieve this using 400 GPU 3090s, with the target at 62% of the range. In 1 day, we would have needed almost 60 times as many 3090 GPUs, say at least 24,000 RTX 3090 GPUs.
For the 135th, the search space is more than 30 times larger, so we'd need at least 750k GPUs 3090 to get there in 24 hours, if the target is 60% of the range, using software perfectly optimized to run on such a configuration.
Whether it's the 71st or the 135th, the difficulty of getting there is roughly the same, even if the software or the way of doing it is different, since for one the pubkey is known. We wish you good luck.
When app starts it displays estimated RAM for DPs based on -range and -dp options, multiply it by -max option to get required RAM (roughly).
Or download latest sources and compile them, I added max RAM size calculation.
Or download latest sources and compile them, I added max RAM size calculation.
Code:
...RCKangaroo.exe" -dp 16 -range 75 -start 4000000000000000000 -tames rckang75a.dat -max 3
********************************************************************************
* 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
Windows version
CUDA devices: 1, CUDA driver/runtime: 12.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
TAMES GENERATION MODE
Solving point: Range 75 bits, DP 16, start...
SOTA method, estimated ops: 2^37.702, RAM for DPs: 0.315 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^39.287
Estimated DPs per kangaroo: 2.891. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
GEN: Speed: 1149 MKeys/s, Err: 0, DPs: 216K/3410K, Time: 0d:00h:00m/0d:00h:03m
GEN: Speed: 1582 MKeys/s, Err: 0, DPs: 467K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1566 MKeys/s, Err: 0, DPs: 701K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1552 MKeys/s, Err: 0, DPs: 935K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1542 MKeys/s, Err: 0, DPs: 1168K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1538 MKeys/s, Err: 0, DPs: 1402K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1533 MKeys/s, Err: 0, DPs: 1636K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1532 MKeys/s, Err: 0, DPs: 1871K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1523 MKeys/s, Err: 0, DPs: 2104K/3410K, Time: 0d:00h:01m/0d:00h:02m
….
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9282K/3410K, Time: 0d:00h:06m/0d:00h:02m
GEN: Speed: 1521 MKeys/s, Err: 0, DPs: 9515K/3410K, Time: 0d:00h:06m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9749K/3410K, Time: 0d:00h:07m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9983K/3410K, Time: 0d:00h:07m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 10217K/3410K, Time: 0d:00h:07m/0d:00h:02m
Operations limit reached
Stopping work ...
saving tames...
tames saved
********************************************************************************
* 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
Windows version
CUDA devices: 1, CUDA driver/runtime: 12.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
TAMES GENERATION MODE
Solving point: Range 75 bits, DP 16, start...
SOTA method, estimated ops: 2^37.702, RAM for DPs: 0.315 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^39.287
Estimated DPs per kangaroo: 2.891. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
GEN: Speed: 1149 MKeys/s, Err: 0, DPs: 216K/3410K, Time: 0d:00h:00m/0d:00h:03m
GEN: Speed: 1582 MKeys/s, Err: 0, DPs: 467K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1566 MKeys/s, Err: 0, DPs: 701K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1552 MKeys/s, Err: 0, DPs: 935K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1542 MKeys/s, Err: 0, DPs: 1168K/3410K, Time: 0d:00h:00m/0d:00h:02m
GEN: Speed: 1538 MKeys/s, Err: 0, DPs: 1402K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1533 MKeys/s, Err: 0, DPs: 1636K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1532 MKeys/s, Err: 0, DPs: 1871K/3410K, Time: 0d:00h:01m/0d:00h:02m
GEN: Speed: 1523 MKeys/s, Err: 0, DPs: 2104K/3410K, Time: 0d:00h:01m/0d:00h:02m
….
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9282K/3410K, Time: 0d:00h:06m/0d:00h:02m
GEN: Speed: 1521 MKeys/s, Err: 0, DPs: 9515K/3410K, Time: 0d:00h:06m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9749K/3410K, Time: 0d:00h:07m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 9983K/3410K, Time: 0d:00h:07m/0d:00h:02m
GEN: Speed: 1519 MKeys/s, Err: 0, DPs: 10217K/3410K, Time: 0d:00h:07m/0d:00h:02m
Operations limit reached
Stopping work ...
saving tames...
tames saved
I must not have understood correctly but in this case the ram displayed is indeed 0.315GB and -max 3 it should take 900 MB or even 1 GB but it took 352 MB exactly 352055KB, why?
Very interesting this update, for fun I did the test with a precalculation of the points on #75 bit with -max 3 this already requires 350 Mo of free space.
how many Go available requires for example the precalculation of a 100bit space with -max 10 ?
how many Go available requires for example the precalculation of a 100bit space with -max 10 ?
I did a 85bit -max10 the Generation took 4 hours and 35GB of space
ok thank you for your answer I'm going to test a 90 in -max 5 to see but I'm not sure I'll have enough space we'll see
Very interesting this update, for fun I did the test with a precalculation of the points on #75 bit with -max 3 this already requires 350 MB of free space.
how many GB available requires for example the precalculation of a 100bit space with -max 10 ?
how many GB available requires for example the precalculation of a 100bit space with -max 10 ?
you were right the bug was me in the command line
It works very well. Thanks for the clarification
It works very well. Thanks for the clarification
Code:
C:\Users\AlphaT"C:\Users\Documents\bitcoin\RCKangaroo.exe" -dp 16 -range 75 -start 4000000000000000000 -pubkey 03FAC615733B5B83682DBBCD4539A8DA3E90085D43FAC8B3B54E43B92DDAAB14B8
********************************************************************************
* 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.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: FAC615733B5B83682DBBCD4539A8DA3E90085D43FAC8B3B54E43B92DDAAB14B8
Y: E2A089597B384B71B37C7932AC457613FF649D1E98481A05732DFBA9E4DE444D
Offset: 0000000000000000000000000000000000000000000004000000000000000000
Solving point: Range 75 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: 2.044. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 1103 MKeys/s, Err: 0, DPs: 216K/2411K, Time: 0d:00h:00m, Est: 0d:00h:02m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 432K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1521 MKeys/s, Err: 0, DPs: 666K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 900K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 1134K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1517 MKeys/s, Err: 0, DPs: 1367K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 1600K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 1834K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2067K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 2301K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2517K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 2751K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 2985K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 3219K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3453K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3687K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
Stopping work ...
Point solved, K: 1.863 (with DP and GPU overheads)
PRIVATE KEY: 0000000000000000000000000000000000000000000007D4AB114686A1336E07
********************************************************************************
* 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.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: FAC615733B5B83682DBBCD4539A8DA3E90085D43FAC8B3B54E43B92DDAAB14B8
Y: E2A089597B384B71B37C7932AC457613FF649D1E98481A05732DFBA9E4DE444D
Offset: 0000000000000000000000000000000000000000000004000000000000000000
Solving point: Range 75 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: 2.044. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 1103 MKeys/s, Err: 0, DPs: 216K/2411K, Time: 0d:00h:00m, Est: 0d:00h:02m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 432K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1521 MKeys/s, Err: 0, DPs: 666K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 900K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1519 MKeys/s, Err: 0, DPs: 1134K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1517 MKeys/s, Err: 0, DPs: 1367K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 1600K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 1834K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2067K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 2301K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2517K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 2751K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 2985K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 3219K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3453K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3687K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
Stopping work ...
Point solved, K: 1.863 (with DP and GPU overheads)
PRIVATE KEY: 0000000000000000000000000000000000000000000007D4AB114686A1336E07
There seems to be a bug for 20xx cards, nothing is found
For small beaches as well as larger ones it turns without finding anything.
I take as examples the beach mentioned by Zahid888
For small beaches as well as larger ones it turns without finding anything.
I take as examples the beach mentioned by Zahid888
Code:
C:\Users\AlphaT"C:\Users\M. Orsini\Documents\bitcoin\RCKangaroo.exe" -dp 16 -range 74 -start 40000000000000000000 -p
ubkey 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.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: 726B574F193E374686D8E12BC6E4142ADEB06770E0A2856F5E4AD89F66044755
Y: 9B15322E6707090A4DB3F09C7E6632A26DB57F03EB07B40979FC01C827E1B0A3
Offset: 0000000000000000000000000000000000000000000040000000000000000000
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: 2.044. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 1110 MKeys/s, Err: 0, DPs: 216K/2411K, Time: 0d:00h:00m, Est: 0d:00h:02m
MAIN: Speed: 1529 MKeys/s, Err: 0, DPs: 450K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1521 MKeys/s, Err: 0, DPs: 684K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1517 MKeys/s, Err: 0, DPs: 899K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 1133K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 1367K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 1600K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 1834K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2067K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 2301K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 2516K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 2750K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 2985K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1502 MKeys/s, Err: 0, DPs: 3219K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 3453K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 3669K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3903K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4137K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 4371K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4604K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4838K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1506 MKeys/s, Err: 0, DPs: 5053K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 5287K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 5522K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1506 MKeys/s, Err: 0, DPs: 5756K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1493 MKeys/s, Err: 0, DPs: 5990K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 6206K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 6441K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1502 MKeys/s, Err: 0, DPs: 6675K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
ubkey 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.6/12.6
GPU 0: NVIDIA GeForce RTX 2070, 8.00 GB, 36 CUs, cap 7.5, PCI 1, L2 size: 4096 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: 726B574F193E374686D8E12BC6E4142ADEB06770E0A2856F5E4AD89F66044755
Y: 9B15322E6707090A4DB3F09C7E6632A26DB57F03EB07B40979FC01C827E1B0A3
Offset: 0000000000000000000000000000000000000000000040000000000000000000
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: 2.044. DP overhead is big, use less DP value if possible!
GPU 0: allocated 3477 MB, 1179648 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 1110 MKeys/s, Err: 0, DPs: 216K/2411K, Time: 0d:00h:00m, Est: 0d:00h:02m
MAIN: Speed: 1529 MKeys/s, Err: 0, DPs: 450K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1521 MKeys/s, Err: 0, DPs: 684K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1517 MKeys/s, Err: 0, DPs: 899K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 1133K/2411K, Time: 0d:00h:00m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 1367K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 1600K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 1834K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 2067K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 2301K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1509 MKeys/s, Err: 0, DPs: 2516K/2411K, Time: 0d:00h:01m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 2750K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 2985K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1502 MKeys/s, Err: 0, DPs: 3219K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1515 MKeys/s, Err: 0, DPs: 3453K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 3669K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 3903K/2411K, Time: 0d:00h:02m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4137K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1513 MKeys/s, Err: 0, DPs: 4371K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4604K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1511 MKeys/s, Err: 0, DPs: 4838K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1506 MKeys/s, Err: 0, DPs: 5053K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 5287K/2411K, Time: 0d:00h:03m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 5522K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1506 MKeys/s, Err: 0, DPs: 5756K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1493 MKeys/s, Err: 0, DPs: 5990K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1504 MKeys/s, Err: 0, DPs: 6206K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1512 MKeys/s, Err: 0, DPs: 6441K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
MAIN: Speed: 1502 MKeys/s, Err: 0, DPs: 6675K/2411K, Time: 0d:00h:04m, Est: 0d:00h:01m
Waouhhh merci retiredcoder de l’avoir adapté et optimisé pour les cartes séries 20xx et 10xx quel bel outil et quelle vitesse incroyable 17 min pour une #85bit je suis bluffé bravo à toi !
@RetiredCoder Maybe you can share networking and dp load/save options. Do you have any plan on it?
I'm not going to create serious ready-to-use open-source solution for cracking really high ranges. You should do it by yourself if you want to crack #135 and get a lot of money
But I'm going to update RCKangaroo to support old cards better (+higher speed) when I have time.
The 135 remains technically feasible with very large resources like that used by retiredcoder (400 GPU 4090) and with a very well optimized RCKangaroo, depending on the position of the privateKey it would take between 0 and 1.2 years to resolve it. Depending on the price of bitcoin, the operation can be profitable but it must be possible to do so with such a resource.
Intriguing all the same, this RetiredCoder his way of writing, of composing his posts and some facts intrigue me (1 example DO NOT POST SESC LINKS ) I'm probably wrong but satoshi_rider= RetiredCoder=satoshi why not 🤔?! I don't understand the meaning of some of his messages including the one in the signature of #130 involving a famous quote from Jules Verne?? nor why this one….nor even how it was a clue if not a message or rather an implied clue free to everyone to appreciate its significance. Why is it he who gives the explanation then the privkey on how to achieve it and not the strange brief solver
compared to its first two mini puzzles this one is much less interesting in terms of difficulty/gain but that's just my opinion I spent almost 5 hours on it today to come up with no clue while the second which I saw too late was resolved in 5 minutes for me 
As much for me 26 bTC I had not noticed that for #120 the price had not yet been *10! the reward remains correct. Thank you for your response and the details but 400 RTX 4090 for 2 months is colossal and impossible for 99.9% of people!! Well done anyway
wow, congratulations to you for finding #120, 125 and 130 (probably a world record for 130). Your skills have been rewarded with over 37 BTC recovered. How many GPUs did you have to use to find the 130? Have you used an optimized version of your RCKangaroo or another tool?
Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
Oh, you are rigth seems interesting.
But there is no any output
yes that's right that's why I said it's strange 
But there is no any output
.....I try to understand how this can happen but Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
ok albert0bsd but my remark came from the fact that the explorer shows $2.07 sent as well as the difference between the total received and the final balance
Re: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==
It's strange did you notice that on #66 there is an output awaiting validation 2.07$
https://www.blockchain.com/fr/explorer/addresses/btc/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
It is not validated so the pubkey is not broadcast but the scale takes it into account without any validation
It doesn't exist on the other # yet. How can this happen?
https://www.blockchain.com/fr/explorer/addresses/btc/13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
It is not validated so the pubkey is not broadcast but the scale takes it into account without any validation
It doesn't exist on the other # yet. How can this happen?