Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
Ovixx
on 26/03/2025, 07:38:19 UTC
For anyone still seeing [1;1H instead of proper terminal controls...

I used to get Egyptian hieroglyphs in the Cyclone in the terminal, but it's better now.  Grin


It works now. I'm running for a single address with 24 threads... the speed is ~91 Mkeys/s but it decreases ... after 3 minutes it reached 62 Mkeys/s

I get a constant 40–41 Mkeys/s with 12 cores on biCyclone by nomachine. The speed only goes down if I start a game on the same PC  Tongue

Hey speed enthusiasts,

Let’s clear the air—don’t overload your addresses.txt with tons of addresses unless you really need to! Too many addresses can tank your speed big time. Stick to 1 address like other Cyclones do, and you’ll cruise at a steady 4.5–4.8 Mkeys/s per core. With a 12-core beast, that’s at least 48 Mkeys/s! Hunting all 80 puzzle balance addresses? You’ll still hit a solid 3 Mkeys/s minimum. So, @Ovixx, with your 24-core monster [From 2^68 to 2^160], you should be rocking 24 × 3 = 72 Mkeys/s. Dropping to 62? Might be extra addresses or background tasks sneaking in—give your PC some breathing room and watch it fly!

Even if this PuzzleFinder runs at 1 Mkeys/s, it’s still better than most out there! Why? It uses a random method that’s totally different from anything else. This unique trick gives you a big advantage in finding those puzzle keys. It’s all crystal clear now! This PuzzleFinder’s got its groove, and it’s unlike anything out there. Now it’s your call—love it, rock it, or roll your own way. The choice is yours, and either way, you’re the boss of this treasure hunt!

Catch you on the flip side! happy hunting!

Code:
D:\Personal\PuzzleFinder-main\PuzzleFinder-main>PuzzleFinder.exe -t 24 -i addresses.txt -sbl 71 -ebl 72 -p 8

*===============================================================*
*                Bitcoin Random PuzzleFinder                    *
*                       By Zahid888                             *
*            1BGvwggxfCaHGykKrVXX7fk8GYaLQpeixA                 *
*                                                               *
*                [From Bit 2^71 To Bit 2^72]                    *
*===============================================================*

[+] Input File       : addresses.txt
[+] Addresses Loaded : 1
[+] Prefix Length    : 8
[+] Started at       : Tue Mar 25 16:12:03 2025
[+] CPU threads used : 24

[Speed : Mkeys/s 103.68] [CPU Threads : (24)] [Total Checked : 4320256] [Elapsed Time : 00:00:01] [Bit Length : 2^072] [[Speed : Mkeys/s 100.42] [CPU Threads : (24)] [Total Checked : 8369152] [Elapsed Time : 00:00:02] [Bit Length : 2^072] [[Speed : Mkeys/s 98.77] [CPU Threads : (24)] [Total Checked : 12347392] [Elapsed Time : 00:00:03] [Bit Length : 2^072] [[Speed : Mkeys/s 97.93] [CPU Threads : (24)] [Total Checked : 16323072] [Elapsed Time : 00:00:04] [Bit Length : 2^071] [[Speed : Mkeys/s 98.49] [CPU Threads : (24)] [Total Checked : 20519936] [Elapsed Time : 00:00:05] [Bit Length : 2^072] [[Speed : Mkeys/s 98.14] [CPU Threads : (24)] [Total Checked : 24536064] [Elapsed Time : 00:00:06] [Bit Length : 2^072] [[Speed : Mkeys/s 97.60] [CPU Threads : (24)] [Total Checked : 28467200] [Elapsed Time : 00:00:07] [Bit Length : 2^072] [[Speed : Mkeys/s 97.64] [CPU Threads : (24)] [Total Checked : 32546304] [Elapsed Time : 00:00:08] [Bit Length : 2^071] [[Speed : Mkeys/s 97.54] [CPU Threads : (24)] [Total Checked : 36579328] [Elapsed Time : 00:00:09] [Bit Length : 2^072] [[Speed : Mkeys/s 97.56] [CPU Threads : (24)] [Total Checked : 40651776] [Elapsed Time : 00:00:10] [Bit Length : 2^072] [[Speed : Mkeys/s 97.44] [CPU Threads : (24)] [Total Checked : 44661248] [Elapsed Time : 00:00:11] [Bit Length : 2^071] [[Speed : Mkeys/s 97.56] [CPU Threads : (24)
In this benchmark, you get an average of 4 Mkeys/s per core, possibly because this version uses a fully random approach, which impacts the speed.
Only the name of the file is "addresses.txt", but it contains only one target address. Initially I created a file called 71.txt but the application gave me the error "file 71.txt cannot be opened".
The first PC I tested has an i9 13900K CPU and I had other applications open and the Chrome browser with about 14 pages open.
Now I'm testing on an i9 14900K without any other applications open, with 32 threads and I see that it stays constant at 126 Mkeys/s. The first time I searched like a fool, address #71 and in the range of 72. Now I set -sbl 71 -ebl 71 and it's ok, I'm not running around the field after butterflies anymore.