Bitcoin Forum
October 23, 2026, 10:57:15 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 [61] 62 »
  Print  
Author Topic: == Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==  (Read 65329 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (11 posts by 1+ user deleted.)
king_of_1
Newbie
*
Offline

Activity: 6
Merit: 1


View Profile
February 13, 2026, 04:59:49 PM
 #1201

I will solve puzzle 74 soon!

And share related 19 digit hexadecimal  Wink

0x...................
yeah, may be, you are right.
.
even me, I am going to solve puzzle # 79. I will let you know when i am done. Grin
mahurovihamilo
Jr. Member
*
Offline

Activity: 50
Merit: 2


View Profile
February 23, 2026, 07:10:42 PM
 #1202


VanitySearch performance list

GPU:
GeForce RTX 2080 Ti: ~2564 Mkeys/s
GeForce RTX 2080 SUPER: ~2001 Mkeys/s**
Tesla V100-SXM2-16GB: ~1815 Mkeys/s
Tesla A10: ~1400 Mkeys/s**
GeForce RTX 2080 EVGA XC ULTRA: ~1425 Mkeys/s
GeForce RTX 2070: ~1470 Mkeys/s
GeForce RTX 2060 SUPER: ~1361 Mkeys/s**
GeForce GTX 1660 Ti: ~960 Mkeys/s
GeForce GTX 1080 Ti: ~900 Mkeys/s
GeForce GTX 1660: ~839 Mkeys/s
GeForce GTX 1080: ~672 Mkeys/s
GeForce GTX 1650: ~511 Mkeys/s
GeForce GTX 980: ~375 Mkeys/s
GeForce GTX 970: ~330 Mkeys/s
GeForce GTX 1060 3GB: ~321 Mkeys/s
GeForce GTX 1050 Ti: ~220 Mkeys/s
Tesla M60: ~185 Mkeys/s
GeForce GTX 960M: ~117 Mkeys/s
GeForce GTX 750: ~95 Mkeys/s
GeForce GT 520M: ~7 Mkeys/s

Compilation types of VanitySearch:
default is 128Mb threads for GPU
** - 256Mb threads for GPU
*** - 512Mb threads for GPU
Generally, it is confirmed that each higher thread compilation is more efficient and significantly increases the performance, but it is also worth noting that the latest cards (starting from RTX) do not work on the 512Mb version due to the changed architecture. For these, the 256Mb version is recommended

CPU:
i7-7700K CPU: ~22 Mkeys/s | using 8 threads [-t 8]

Many thanks to DaveF who has collected the vast majority of the data here.
It was thanks to him that I decided to put this data here and express my willingness to supplement it with more items.

If you have equipment that is not listed above - I will be grateful for info on its performance in VanitySearch (version with integrated BitCrack options).
If you have the equipment listed above and you managed to get better performance - also let us know how you did it (additional start command, gridsize etc.) for the update.

Latest VanitySearch builds with BitCrack features working on all NVIDIA cards

Compilations made with the use of CUDA version 11.6, so for the program to work it is necessary to update the drivers in the system to the latest ones that are available. I have compiled for each GPU architecture separately - as listed below

LINUX

After downloading, execute the command chmod +x vanitysearch in linux
The downloaded file is ready, for example, to start working with the ttd client needed to start participating in pool #64.
Just download the selected compilation to the same folder as the ttdclient and the settings.ini file

For the lazy, I also provide ttdclient to work with the above in linux: http://zielar.pl/ttdclient [run the chmod +x ttdclient command after the download], and sample settings.ini: http://zielar.pl/settings.ini

MS Windows:
comming soon


NVIDIA Kepler GPUs: GeForce 700, GT-730, Tesla K40 [SM_35]; Tesla K80 [SM_37]
NVIDIA Maxwell GPUs: Tesla/Quadro M series [SM_50]; Quadro M6000 , GeForce 900, GTX-970, GTX-980, GTX Titan X [SM_52]; Tegra (Jetson) TX1 / Tegra X1, Drive CX, Drive PX, Jetson Nano [SM_53]
NVIDIA Pascal GPUs: Quadro GP100, Tesla P100, DGX-1 (Generic Pascal) [SM_60]; GTX 1080, GTX 1070, GTX 1060, GTX 1050, GTX 1030 (GP108), GT 1010 (GP108) Titan Xp, Tesla P40, Tesla P4, Discrete GPU on the NVIDIA Drive PX2 [SM_61]; Integrated GPU on the NVIDIA Drive PX2, Tegra (Jetson) TX2 [SM_62]
NVIDIA Volta GPUs: DGX-1 with Volta, Tesla V100, GTX 1180 (GV104), Titan V, Quadro GV100 [SM_70]
NVIDIA Xavier GPUs: Jetson AGX Xavier, Drive AGX Pegasus, Xavier NX [SM_72]
NVIDIA Turing GPUs: GTX/RTX Turing – GTX 1660 Ti, RTX 2060, 2070, 2080, Titan RTX, Quadro RTX 4000, 5000, 6000, 8000, Quadro T1000/T2000, Tesla T4 [SM_75]
NVIDIA Ampere GPUs: NVIDIA A100, NVIDIA DGX-A100 [SM_80]; Tesla GA10x cards, RTX 3050, 3060, 3070, 3080, 3090, RTX A2000, A3000, A4000, A5000, A6000, NVIDIA A40, A10, A16, A40, A2 Tensor Core GPU [SM_86]


Hi there..
I am trying to download and get going these:

SM_61 [Pascal]: http://zielar.pl/vslinux/sm_61/vanitysearch
SM_62 [Pascal]: http://zielar.pl/vslinux/sm_62/vanitysearch

the links are DEAD ....

Can I find them somewhere else?

Please let me know, Thanks !!
mahurovihamilo
Jr. Member
*
Offline

Activity: 50
Merit: 2


View Profile
February 23, 2026, 07:14:37 PM
 #1203

Hi there,

Is there a pool I can chain my mining rigs to help solve this puzzle? only honest reliable ones please....

Thanks.
OzBtcOz
Newbie
*
Offline

Activity: 27
Merit: 0


View Profile WWW
March 31, 2026, 07:11:27 AM
 #1204

I'm facing interesting things while solving Puzzle 71.
My math theorem produce several address with begins "1PWo3J" only between a small (1,539,149,486 keys) gap.

1PWo3J2aAy3LSRmJnWvozpXD5X2koiXkRT
1PWo3J1k9eY1CprChGugYKxPdR26JYGCVQ
1PWo3JqJrd82DP3Pf2KkdKpbyJJpfMucKr

Is there any pattern or something like that?
Cricktor
Legendary
*
Offline

Activity: 1652
Merit: 4632



View Profile
March 31, 2026, 06:49:18 PM
 #1205

Hmm, your math theorem... now that's something fancy, tell us more about it! Nevermind...

Frankly, I don't know what you're trying to achieve by hunting and collecting prefixes for #71, but what do I know about your so-called "math theorem".

Code:
1PWo3J2aAy3LSRmJnWvozpXD5X2koiXkRT
1PWo3J1k9eY1CprChGugYKxPdR26JYGCVQ
1PWo3JqJrd82DP3Pf2KkdKpbyJJpfMucKr

Have you checked that the private keys for those actually fall in the key range of puzzle #71?

I'd say, this should be an obvious given, but we've seen something else in the other puzzle mega-thread.


OzBtcOz
Newbie
*
Offline

Activity: 27
Merit: 0


View Profile WWW
April 01, 2026, 02:09:15 PM
Last edit: April 07, 2026, 12:01:02 PM by OzBtcOz
 #1206

Hmm, your math theorem... now that's something fancy, tell us more about it! Nevermind...

Frankly, I don't know what you're trying to achieve by hunting and collecting prefixes for #71, but what do I know about your so-called "math theorem".

Code:
1PWo3J2aAy3LSRmJnWvozpXD5X2koiXkRT
1PWo3J1k9eY1CprChGugYKxPdR26JYGCVQ
1PWo3JqJrd82DP3Pf2KkdKpbyJJpfMucKr

Have you checked that the private keys for those actually fall in the key range of puzzle #71?

I'd say, this should be an obvious given, but we've seen something else in the other puzzle mega-thread.



Do you think I am a stupid man? Of course all of them in range of puzzle71. I am still diggin it. I found several keys between a small gap.
All hexes start same prefixes, all addresses start same prefixes and all hash160s start same prefixes.

1PWo3JVzdvGKG2xVeKfqCQs86YTtkNRXbk
1PWo3J2Hg3ioAGr62z3u32jLdqXsP8zi46
1PWo3J8NJk3ZzhqbyEovMKF4RJSgpU6WaF
...


If you don't believe in me, please try to send some amount one of them above Smiley

Never mind! , there are thousand, millions, also billions addresses between same gap  Angry


shemshallah
Newbie
*
Offline

Activity: 1
Merit: 0


View Profile
April 15, 2026, 05:10:07 PM
 #1207

https://www.pasteboard.co/-3tAP35HWv5E.png

IF all the math is truly correct. Well this makes things a lot easier...You have to know how to talk to the LLMs in order to get them to produce something of this quality and intention.
akaros
Copper Member
Newbie
*
Offline

Activity: 57
Merit: 0

Builder of big stable mining farms since 2011.


View Profile
April 18, 2026, 11:40:29 PM
 #1208

Mempool sniping. What is the latest?

Puzzles 66 and 69 suffered mempool sniping by multiple entities. Any new sound techniques yet to avoid it? I already read about the private submission to well-known miners.


I am interested in solution also. Really don't know how to do. I need private submission Smiley

Miner from 2011
Cricktor
Legendary
*
Offline

Activity: 1652
Merit: 4632



View Profile
April 19, 2026, 10:08:50 AM
 #1209

I am interested in solution also. Really don't know how to do. I need private submission Smiley
Use https://slipstream.mara.com (when I checked a few minutes ago, the page is currently under maintenance) to submit standard or non-standard transactions to a private and hidden mempool of MARA pool. If accepted by Slipstream service your pending transaction won't be visible to the public and mempool snipers until it is confirmed and mined into a block of MARA pool.

Slipstream has worked as expected and reliable to withdraw solutions for puzzles #67 and #68.

See here for posts containing keyword slipstream in this topic: https://bitlist.co/search?content=slipstream&topic_id=5218972&limit=20

mjtpzfrl
Newbie
*
Offline

Activity: 1
Merit: 0


View Profile
April 27, 2026, 05:58:28 PM
 #1210

I'm facing interesting things while solving Puzzle 71.
My math theorem produce several address with begins "1PWo3J" only between a small (1,539,149,486 keys) gap.

1PWo3J2aAy3LSRmJnWvozpXD5X2koiXkRT
1PWo3J1k9eY1CprChGugYKxPdR26JYGCVQ
1PWo3JqJrd82DP3Pf2KkdKpbyJJpfMucKr

Is there any pattern or something like that?
....I HAVE DESIGNED A PYTHON SCRIPT FOR PUZZLE 71 BUT MY HARDWARE IS TOO WEAK FOR ACHIEVING: HERE IS A MY SCRIPT ABILITIES: This script is a Bitcoin private key search tool specifically designed for Puzzle 71. Let me explain exactly what it does:

Core Functionality
1. Key Generation Pattern
Generates private keys with this exact structure:

text
[46 ZEROS] + [2 HEX] + [16-char SUFFIX] = 64 hex characters (256 bits)
Example: 000...000 + 4a + 3f8d2c1b9e4a7b6c

2. For Each Selected 16-Char Suffix (from the clickable grid)
Cycles through all 64 two-hex combinations (4x-7x followed by 0-f)

Generates exactly 64 unique private keys per suffix

Total keys per suffix = 64

3. Cross-Region Parallel Scanning (The Key Innovation)
Divides the entire Puzzle 71 key space (0x40000000000000000 to 0x7FFFFFFFFFFFFFFFF) into 64 regions using a Hilbert curve

For each generated key, it extracts a block number from the key's last 18 characters (2hex + 16hex)

Then checks the SAME block number across ALL 64 regions simultaneously

Result: Each generated key effectively checks 64 different private keys (one from each region)!

4. Visual Interface (Pygame)
3D visualization of 64 color-coded regions (Hilbert curve partitioned space)

Clickable grid (bottom-right) for selecting 16-character suffixes (represents 16^16 = 18.4 quintillion possibilities)

Real-time display of:

Current generated key and its Bitcoin address

Current block number being checked across all regions

Scanning speed (keys/sec)

Progress percentage

FPS counter

Matched blocks found

5. Sample Recording Feature
Records the first 10 keys at each 1% progress (1% to 100%)

After completing all 64 key combinations for a suffix, processes all recorded sample keys

Ensures every percent threshold is checked

6. Performance Optimizations
Batch processing (generates 1000 keys at once)

Address caching (LRU cache of 100,000 addresses)

Multi-threading (uses all CPU cores minus one)

Progress saving (auto-saves every 50,000 keys to JSON)

Completed suffix persistence (saves and marks finished suffixes)

7. Controls
S: Start scanning

P: Pause/Resume

C: Copy current key to clipboard

L: Save progress manually

M: Resume from saved progress

R: Reset camera view

Q: Quit

Click grid: Change the 16-char suffix (resets progress)

What Makes This Script Unique
Unlike simple brute-forcers that scan keys sequentially, this script:

Generates keys with a specific pattern (46 zeros + 2hex + 16hex) - the puzzle creator may have chosen a key with this pattern

Uses the generated key to determine WHICH block number to check

Checks that block number across ALL 64 regions simultaneously - 64x speed advantage!

Does It Work?
Yes, the logic is correct. For each generated key:

It extracts a block number from that key

It checks ALL 64 regions at that block number

If ANY region's key at that block number matches the target address 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU, it reports a match

The Critical Assumption
This script will only find the private key if the actual Puzzle 71 key has the pattern:

46 leading zeros in its hex representation

Followed by any 2 hex chars (from the set 4x-7x + any second char)

Followed by any 16 hex chars

If the actual key doesn't match this pattern, the script will never find it. But if it does match, this script will find it efficiently.

Summary
This is a specialized, optimized, parallel search tool with a beautiful 3D visualization. It's not a general brute-forcer - it's designed for a very specific key pattern that the Puzzle 71 creator may have chosen. The parallel region scanning gives a 64x speed advantage over checking regions one by one.
ldabasim
Newbie
*
Offline

Activity: 19
Merit: 0


View Profile
April 27, 2026, 06:45:45 PM
 #1211

Are you aware that the private key is just a number and its how many point additions we do starting from the generator point to get to the publickey, what are you talking about prefixes and zeroes and the patterns...it doesn't have to be 64 characters. Checking more than one key on each point addition is possible only with a known public key its called BSGS. Also incrementing from the left means you're doing scalar multiplication each time instead of just a point addition, so even if you could speed up things 64x, you'll be taking about that much longer on each operation.
OzBtcOz
Newbie
*
Offline

Activity: 27
Merit: 0


View Profile WWW
May 04, 2026, 07:47:46 AM
 #1212

Below samples may help someone about the location of private key 71 ;

0000000000000000000000000000000000000000000000649a05d73d20978e62 = 1PWo3JeB9jT926gmLys26TBwr6pwStgwLb = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBinmvSXpixVnKso3SZd
0000000000000000000000000000000000000000000000649a103b78b3e74856 = 1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBinyJ7SyJ1aHWsGeWtv
0000000000000000000000000000000000000000000000649a3dd0486c96e70b = 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997 = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBioqBgemYg4VSEkEFo5
0000000000000000000000000000000000000000000000649a737f258abb8058 = 1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2 = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBipqwa1JY7VeYq3zfDL
0000000000000000000000000000000000000000000000649aa0a809fe13a924 = 1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBiqhNP4PNciudJAoe6j
0000000000000000000000000000000000000000000000649ade9933e47de861 = 1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBirsAZRi1dmwLPdfAD8
0000000000000000000000000000000000000000000000649af9e3471ed5c49b = 1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBisP2vxweiiYwjdEHkj

By the way, the private key WIF continue with KwD.....3rxxxxxxxxxxx.

So the space begins with 4770db3ea2444fe120, not 0x40000... It will make you 11,80% luckier.

Good luck all!

Donations to : bc1qj64tgge493a8jec597hynk82sy9zduyrzj9r82 Smiley
optioncmdPR
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile
May 06, 2026, 07:01:56 AM
 #1213

Code:



                                                                                20
                                                                              1024
                                                                           1048576
                                                                        1073741824
                                                                     1099511627776
                                                                  1125899906842620
                                                               1152921504606850000
                                                            1180591620717410000000
                                                         1208925819614630000000000
                                                      1237940039285380000000000000
                                                   1267650600228230000000000000000
                                                1298074214633710000000000000000000
                                             1329227995784920000000000000000000000
                                          1361129467683750000000000000000000000000
                                       1393796574908160000000000000000000000000000
                                    1427247692705960000000000000000000000000000000
                                 1461501637330900000000000000000000000000000000000
                              1496577676626840000000000000000000000000000000000000
                           1532495540865890000000000000000000000000000000000000000
                        1569275433846670000000000000000000000000000000000000000000
                     1606938044258990000000000000000000000000000000000000000000000
                  1645504557321210000000000000000000000000000000000000000000000000
               1684996666696920000000000000000000000000000000000000000000000000000
            1725436586697640000000000000000000000000000000000000000000000000000000
         1766847064778380000000000000000000000000000000000000000000000000000000000
 

0
14
190
100000
40000000
10000000000
1125899906842620
1152921504606850000
1180591620717410000000
1208925819614630000000000
1237940039285380000000000000
1267650600228230000000000000000
1298074214633710000000000000000000
1329227995784920000000000000000000000
1361129467683750000000000000000000000000
1393796574908160000000000000000000000000000
1427247692705960000000000000000000000000000000
1461501637330900000000000000000000000000000000000
1496577676626840000000000000000000000000000000000000
1532495540865890000000000000000000000000000000000000000
1569275433846670000000000000000000000000000000000000000000
1606938044258990000000000000000000000000000000000000000000000
1645504557321210000000000000000000000000000000000000000000000000
1684996666696920000000000000000000000000000000000000000000000000000
1725436586697640000000000000000000000000000000000000000000000000000000
17668470647783800000000000000000000000000000000000000000000000000000000

30 568 377 312 064 202 855

               
        INDEX AMT TOTAL   KEY            KEY SUM TOTAL             
_____________________________________________________________________           
1 001 001 1 1
2 002 003 3 4
3 003 006 7 11
4 004 010     8 19
5 005 015 21 40
6 006 021 49 89
7 007 028 76 165
8 008 036 224 389
9 009 045 467 856
10 010 055 514 1370
11 011 066 1155 2525
12 012 078 2683 5208
13 013 091 5216 10424
14 014 105 10544 20968
15 015 120 26867 47835

                16 016 136 51510 99345
17 017 153 95823 195168
18 018 171 198669 393837
        19 019 190 357535 751372
20 020 210 863317 1614689
21 021 231 1811764 3426453
22 022 253 3007503 6433956
23 023 276 5598802 31202758
24 024 300 14428676 26461434
25 025 325 33185509 59646943
26 026 351 54538862 114183805
27 027 378 111949941 226135746
28 028 406 227634408 453770154
29 029 435 400708894 854479048
30 030 465 1033162084 1887641132
31 031 496 2102388551 3990029683
32 032 528
33 033 561
34 034 595



                 1 3                                 7 8
                15 31                               4c e0
               1d3 202                             483 a7b
              1460 2930                           68f3 c936
             1764f 3080d                         5749f d2c55
            1ba534 2de40f                       556e52 dc2a04
           1fa5ee5 340326e                     6ac3875 d916ce8
          17e2551e 3d94cd64                   7d4fe747 b862a62e
         1a96ca8d8 34a65911d                 4aed21170 9de820a7c
        1757756a93 22382facd0               4b5f8303e9 e9ae4933d6
       153869acc5b 2a221c58d8f             6bd3b27c591 e02b35a358f
      122fca143c05 2ec18388d544           6cd610b53cba ade6d7ce3b9b
     174176b015f4d 22bd43c2e9354         75070a1a009d4 efae164cb9e3c
    180788e47e326c 236fb6d5ad1f43       6abe1f9b67e114 9d18b63ac4ffdf
   1eb25c90795d61c 2c675b852189a21     7496cbb87cab44f fc07a1825367bbe
  13c96a3742f64906 363d541eb611abee   7cce5efdaccf6808 f7051f27b09112d4
 1a838b13505b26867 2832ed74f2b5e35ee 730fc235c1942c1ae bebb3940cd0fc1491
101d83275fb2bc7e0c 349b84b6431a6c4ef1


This may require further study
satscollector
Newbie
*
Offline

Activity: 6
Merit: 0


View Profile
May 10, 2026, 07:10:23 PM
 #1214

Below samples may help someone about the location of private key 71 ;

0000000000000000000000000000000000000000000000649a05d73d20978e62 = 1PWo3JeB9jT926gmLys26TBwr6pwStgwLb = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBinmvSXpixVnKso3SZd
0000000000000000000000000000000000000000000000649a103b78b3e74856 = 1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBinyJ7SyJ1aHWsGeWtv
0000000000000000000000000000000000000000000000649a3dd0486c96e70b = 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997 = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBioqBgemYg4VSEkEFo5
0000000000000000000000000000000000000000000000649a737f258abb8058 = 1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2 = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBipqwa1JY7VeYq3zfDL
0000000000000000000000000000000000000000000000649aa0a809fe13a924 = 1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBiqhNP4PNciudJAoe6j
0000000000000000000000000000000000000000000000649ade9933e47de861 = 1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBirsAZRi1dmwLPdfAD8
0000000000000000000000000000000000000000000000649af9e3471ed5c49b = 1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw = KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rBisP2vxweiiYwjdEHkj

By the way, the private key WIF continue with KwD.....3rxxxxxxxxxxx.

So the space begins with 4770db3ea2444fe120, not 0x40000... It will make you 11,80% luckier.

Good luck all!

Donations to : bc1qj64tgge493a8jec597hynk82sy9zduyrzj9r82 Smiley

Looks like you used vanitysearch. It does not prove you have any type of "math theorem". And already asking for donations.

Code:
./VanitySearch -t 0 -gpu -gpuId 0,1 \
-r 649a00000000000000:649affffffffffffff \
1Pwo
e46996
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
May 24, 2026, 03:17:11 AM
 #1215

I modified Kangaroo for puzzles with pub key exposed.

a 2x increase in speed for searching by using a folding method.

Basically positive plot and negative plot are searched at the same time.

my rig:
laptop 3050 4gb

original base speed 
~479MK/s

With modification ~900 - 1000MK/s

I'm saving up right now to rent 16 5090's to run the modified code on puzzle 135 which should give me around 4.5+TK/s

Cricktor
Legendary
*
Offline

Activity: 1652
Merit: 4632



View Profile
May 24, 2026, 11:18:05 AM
 #1216

...
Have you actually tested that your modification to Kangaroo finds a solution faster than without it? You could either use already solved puzzles or create an own one.

I would assume so, but as you chose to only speak about it and not release your modification(s), I'd rather like to hear about an actual confirmation and solid evidence.

I don't want to destroy your dreams, but 16x 5090 GPUs won't be enough to solve puzzle #135in a reasonable time unless you're very very lucky. There's likely competition, too. I assess this compared to what gear was very likely required by @RetiredCoder to solve puzzle #130 in an economically reasonable time without too much risk to loose to a competitor.

e46996
Newbie
*
Offline

Activity: 2
Merit: 0


View Profile
May 24, 2026, 08:25:01 PM
 #1217

Yes I did test it on a already solved puzzle. I used #130 as a base and used a time based method kind of like a stopwatch to determine the speed, since the actual ui on kangaroo will not output the updated speed because of how the cpu and gpu talk, I'm to lazy to fix that.  

unfortunately I will not give out the code here for obvious reason (more competition). but it does work, will I hit it in my life time? probably not, but has better odds than the Powerball. Also given my current constraints (3050 gpu) I used the new speed to create a script to automate the kangaroo search by searching a random range within the larger range that will complete in a minute and just hop around the entire range randomly in those little slices which is slightly better than scanning the whole range at once.

the folding method i used was a Negation Map which folds by 2 so every point on an elliptic curve has a mirror image right across the x-axis. The point P and its negative -P share the exact same X-coordinate. Because Bitcoin public keys are heavily tied to that X-coordinate, the "fold" makes the search space cut in half. Whenever a wild kangaroo lands on an X-coordinate, the engine checks both the positive and negative Y-coordinates simultaneously. You cut the keyspace by exactly 50% without doing any extra jumps.
satashi_nokamato
Jr. Member
*
Offline

Activity: 82
Merit: 6

Originality of BTC is something else


View Profile
June 19, 2026, 09:04:30 PM
 #1218

Does anyone here know when 125 Private key was revealed? After solving 130 or before?

bc1qn55msljhk39mkq2xheswzj0kjtxyvgyzpdvcdk
Cricktor
Legendary
*
Offline

Activity: 1652
Merit: 4632



View Profile
June 20, 2026, 07:25:08 AM
Merited by satashi_nokamato (1)
 #1219

...
I don't recall all the details, but from blockchain it looks very much so. After @RetiredCoder redeemed bounty of challenge #125 on 2023-07-09 (Tx), the key remained hidden for some time and AFAIR RetiredCoder wanted to make some mini-puzzles for the altcoins that the private key still held.

After RetiredCoder redeemed bounty of challenge #130 on 2024-09-23 (Tx), next day some dude spread some dust over real and "speaking-nonsense" addresses (Tx) which remained unclaimed for quite some weeks.

Dust on challenge #125 was first collected on 2024-11-15 with Tx and this was way after challenge #130 was solved. RetiredCoder posted a mini-puzzle for key #125 here and the mini-puzzle was solved about a day later. It's safe to assume the mini-puzzle solver collected the dust and the more valuable altcoins of private key #125.

Dust on challenge #130 was first collected on 2024-12-15 with Tx. Very likely same happened here with #130 too, because RetiredCoder posted the mini-puzzle for #130 on 2024-12-14 and it apparently was solved about a day later and the solver collected altcoins and dust swiftly.


JDScreesh
Member
**
Offline

Activity: 75
Merit: 31


View Profile
July 28, 2026, 08:22:08 AM
 #1220

Wow.

Congratulations to the solver of the puzzle # 135.

I think that was @RetiredCoder again, because destination address is the same that was used for puzzle # 130.

 Smiley

For donations: BTC - bc1q9v9s9jtunr58pykwx77dpwzdupmfdn0x8jyt06 or 145u2ppTJhkXq11xnbBM5JgkQdgV9o1V42
For donations: LTC - LaAHGMjisi2NFMfHJpMywKm8ALzmivdRaq
Pages: « 1 ... 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 [61] 62 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!