Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Niekko]

From my perspective and the searching on the old puzzles, the distribution is based on a specific pattern. And from what i see where is the distribution high, for example over 15 prefixes in a range 44, there are big chances to find the remaining G. On old puzzles there is a little numbers 1-2 for spcific prefixes that are found on specific keys and is progressing with each puzzle. If anyone checked after puzzle 60 will see what i am saying.

the MSB byte pattern is choose hand-on from the creator for adjust the range.

[daly8]

No mathematical function has been found that generates a sequence of known keys.
No recurrent relationship was found between neighboring keys.
No signs of a simple PRNG or a known generator were found.
No statistically significant internal structure was found to predict the following keys.
No signs of encoding of physical quantities, physical objects, or known physical laws were found.
No evidence of correspondence to models of quantum mechanics, fields, waves, or other physical systems was found.
No signs were found that the keys are states of any known dynamic system.
No evidence has been found for analogies with game theory (including chess) that would allow the recovery of unknown keys.
No signs of musical, geometric, symmetrical, or other compositional structure suitable for sequence prediction were found.
No key representation was found that would give an advantage when searching for the next unknown keys.

After all this, there is only one explanation that fully agrees with the author's words.:

"There is no pattern. These are just consecutive keys from a deterministic wallet (disguised by leading digits 000...0001 to give the desired difficulty). It is simply a crude benchmark of the community's cracking strength."

If you take these words literally, then the Puzzle is not a mathematical puzzle, it does not encode a hidden structure and does not require searching for a special model. This is an open experiment to measure the community's ability to find private keys.

[crypto_user_new]

Let me to dissagree you. Everybody is trusting someone, but you forget that there should be 1 people in 6 billions that can solve this issue in different method.
This is that nobody understand: everything has a solution. if you believe someone that say NO, in that moment you refuse all other posibilities without searching....
Why nobody created something similar to google maps until now to see the BTC each address on a MAP? Think about google maps coordonates of the globe and is the same thing...
The solution of puzzle 71 will not be found with traditional formulas of Bernoulli or Gaus...also the decoding of BTC address is a complex formula that soon will be found. I do not say that i do that, but very soon someone will move a dormand wale by this formula.

[SRG02289]

If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...

There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.

1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB
1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx

SRG02289, please don't feint the comunity.

There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB.

Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff.

I sent some dust on them. We'll see about the time...
Address: 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx  Private Key: 000000000000000000000000000000000000000000000075.f.4.b.5.2.1.f.0 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rJ55ek...qy...qnET7.

[detechs]

No mathematical function has been found that generates a sequence of known keys.
No recurrent relationship was found between neighboring keys.
No signs of a simple PRNG or a known generator were found.
No statistically significant internal structure was found to predict the following keys.
No signs of encoding of physical quantities, physical objects, or known physical laws were found.
No evidence of correspondence to models of quantum mechanics, fields, waves, or other physical systems was found.
No signs were found that the keys are states of any known dynamic system.
No evidence has been found for analogies with game theory (including chess) that would allow the recovery of unknown keys.
No signs of musical, geometric, symmetrical, or other compositional structure suitable for sequence prediction were found.
No key representation was found that would give an advantage when searching for the next unknown keys.

After all this, there is only one explanation that fully agrees with the author's words.:

"There is no pattern. These are just consecutive keys from a deterministic wallet (disguised by leading digits 000...0001 to give the desired difficulty). It is simply a crude benchmark of the community's cracking strength."

If you take these words literally, then the Puzzle is not a mathematical puzzle, it does not encode a hidden structure and does not require searching for a special model. This is an open experiment to measure the community's ability to find private keys.

I have found similar things, after studying the BTC Genesis block before sha256 is added is the most useful insight I found so far. I have invented novel maths to try solve all 160-256 puzzles, I have been designing a btc live block miner now since the puzzles look like a distraction

[Ali_555]

If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...

There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.

1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB
1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx

SRG02289, please don't feint the comunity.

There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB.

Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff.

I sent some dust on them. We'll see about the time...
Address: 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx  Private Key: 000000000000000000000000000000000000000000000075.f.4.b.5.2.1.f.0 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rJ55ek...qy...qnET7.

000000000000000000000000000000000000000000000075dfb41bc502e1cf50

[brainless]

If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...

There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.

1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB
1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx

SRG02289, please don't feint the comunity.

There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB.

Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff.

I sent some dust on them. We'll see about the time...
Address: 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx  Private Key: 000000000000000000000000000000000000000000000075.f.4.b.5.2.1.f.0 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rJ55ek...qy...qnET7.

000000000000000000000000000000000000000000000075dfb41bc502e1cf50

Use crunch and brainflayer together and job could done in second

[zahid888]

Very interesting the Vanitysearch from Jean Luc. I added a new feature to check anywhere in the BTC address

 These features were available right from the start when vanitygen or vanitysearch was introduced.
 using hash160 would be more preferable over base58. like below :

Code:

match.exe --address 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU --matching 16 --range 400000000000000000:40000000ffffffffff --grid 512,512 --deterministic

======================================================================================
|                         CUDA_Hash160 v1.3 by Zahid888                              |
======================================================================================

 [+] Address              : 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
 [+] Hash160              : f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8
 [+] Range                : 400000000000000000 : 40000000ffffffffff
 [+] Matching hex chars   : 16 / 40

=================================== GPU Setup ========================================

 [+] Device               : NVIDIA GeForce RTX 3060 Ti (compute 8.6)
 [+] SMs                  : 38
 [+] Threads/Block        : 256
 [+] Blocks               : 19456
 [+] Point batch size     : 512 (cap 512)
 [+] Batches/SM           : 512
 [+] Steps/launch         : 16
 [+] Flush threshold      : 16384 hashes
 [+] Memory utilization   : 24.0% (1.92 GB / 8.00 GB)

======================================================================================

[-] Total Speed: 1258.50 MK/s [-] [00:00:02 Elapsed Time] [Progress: 0 %] | Matching [0]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1dwdXuAyvH5JVn3Nh1hCWb8AykTmcv3fe  06fc93cd0c3d8b61ce8aceaa84e844e784a0afb6        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                                   ^^  ^ ^       ^ ^^^   ^  ^ ^    ^^^^ ^         |
|------------------------------------------------------------------------------------|
|  Public Key  : 03283B555328640E29F91AE06412FA8503BE89B2DCD8C03E0847D32A05C2F18C1F  |
|  Private Key : 000000000000000000000000000000000000000000000040000000008EDC1497    |
======================================================================================

[/] Total Speed: 1268.86 MK/s [/] [00:00:05 Elapsed Time] [Progress: 0 %] | Matching [1]

======================================================================================
|                    Total Matching character in hash160: 17                         |
|------------------------------------------------------------------------------------|
| 1Q4XUEv4T4bGRWz56PjuqnWYzQnaknxvUe fcf59360f55bfebc5280dd9cf21b473c348f33d7        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^          ^                       ^ ^^ ^   ^ ^^ ^   ^ ^^^ ^   ^^ ^ ^              |
|------------------------------------------------------------------------------------|
|  Public Key  : 02036806EBCBAB1D0B836C327D5EFBD52FA19EF3AF625AAE115400860159E61CEE  |
|  Private Key : 00000000000000000000000000000000000000000000004000000001466E2212    |
======================================================================================



======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1NuWwKN44j5J48cZgf7qFV4uiTkhFoTJe1 f04942dde5bbffb14f98d19afc38320c7dfab5a8        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^        ^            ^            ^   ^  ^ ^^^^ ^^    ^ ^^^      ^     ^ ^        |
|------------------------------------------------------------------------------------|
|  Public Key  : 024F6F5021C7B2DB7BD1F289D9AB54560D210962B3CF68CE2A57F2DCDAFABD3808  |
|  Private Key : 00000000000000000000000000000000000000000000004000000001817EAA49    |
======================================================================================

[-] Total Speed: 1258.75 MK/s [-] [00:00:06 Elapsed Time] [Progress: 1 %] | Matching [3]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1Kf4pGz9oieZAa33XFNNSVpyhS6YqvgmBP cca5415ddab8f4935e854107f5b3475048e0aaa0        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                                     ^^  ^  ^ ^    ^^     ^^ ^^^^ ^  ^^           |
|------------------------------------------------------------------------------------|
|  Public Key  : 0231B1CDED7793DE068B390AE244E4FA49EBD747E00D1F5C2B9C08086D6D406B7F  |
|  Private Key : 000000000000000000000000000000000000000000000040000000019F725084    |
======================================================================================

[\] Total Speed: 1295.70 MK/s [\] [00:00:07 Elapsed Time] [Progress: 1 %] | Matching [4]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1J1cH3WxV4m6Y6TsYNnHx3wChsNT8f9PT  0337943d965bf3018e8a7c9a73e31b7af4d0a9b8        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                      ^                  ^   ^^  ^ ^^^  ^^  ^^     ^ ^^ ^^        |
|------------------------------------------------------------------------------------|
|  Public Key  : 022006B4A3ABF949E2FE8439260F58AF96406228106FD8F6A323282FE8FD4FCA79  |
|  Private Key : 000000000000000000000000000000000000000000000040000000020D2F8E76    |
======================================================================================

[/] Total Speed: 1276.17 MK/s [/] [00:00:13 Elapsed Time] [Progress: 1 %] | Matching [5]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1MyxuwSnfTZzpcfPH15gqHrZPTSjwsty28 e6287baee5bdffb1488edec0f3e0f80444a039b8        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                            ^      ^       ^^ ^ ^^  ^ ^   ^ ^     ^^^^  ^^        |
|------------------------------------------------------------------------------------|
|  Public Key  : 02D817DADA812C7E48400D8E6AFAA577331D7EF8807EEA4E251CA014D02408700D  |
|  Private Key : 000000000000000000000000000000000000000000000040000000039F346E76    |
======================================================================================
.
.
.
.
.
.
.
.
.
.
.
======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 13zc6v3pJUD1E7Ms2HTQsKojyiDDZ5eqt6 20d54356d6bbf0118e5cdd1a65e74b504a9850aa        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                                     ^^^    ^^^  ^ ^  ^^ ^ ^^ ^ ^ ^               |
|------------------------------------------------------------------------------------|
|  Public Key  : 024DAD1EFF8706C7639132E7D8EC93279239BC6F888C8D18E2235B1D44EA8A29B1  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FCD3E3982B    |
======================================================================================

[-] Total Speed: 1242.92 MK/s [-] [00:15:16 Elapsed Time] [Progress: 99 %] | Matching [448]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 136QwF2xnLBXu5XmT4iPsVD84aujoc1NE5 16f64fbd2f6bf11dce10d59a0bef495cec4e95dc        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                        ^          ^^ ^  ^^  ^^    ^  ^ ^^  ^ ^ ^^     ^          |
|------------------------------------------------------------------------------------|
|  Public Key  : 0311AE18C88562E7A076ABE1325CFDC7AB998F01A4CC93C9BF19A2C6FC17164CC7  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FD638B2ACE    |
======================================================================================

[/] Total Speed: 1242.48 MK/s [/] [00:15:19 Elapsed Time] [Progress: 99 %] | Matching [449]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1NwM2GNrxENWAkvoXxEF76SP8spQ7Y13ed f0a1d11765b2f65127aa43dff5e3625240a06be9        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                                  ^     ^  ^^ ^  ^^  ^    ^^^^  ^ ^ ^^            |
|------------------------------------------------------------------------------------|
|  Public Key  : 024A6144625DEF187B55D34D120F656271EE8C907D1E6AA13925920B98D847CCCC  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FE58579C1D    |
======================================================================================

[\] Total Speed: 1268.62 MK/s [\] [00:15:21 Elapsed Time] [Progress: 99 %] | Matching [450]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1PUfH2KFiQax2enBR32aNwEz1yNdAH6UGu f68df31a2ecd317a928adb7a85e343cf46c0f597        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^^                                 ^^   ^^ ^         ^^^  ^ ^^^^   ^  ^ ^          |
|------------------------------------------------------------------------------------|
|  Public Key  : 03A9D3EBFB80F6F860C5F221E6967F46421123B0075C1C164E27B27E443D7809A4  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FEE9F4AEC7    |
======================================================================================

[|] Total Speed: 1247.80 MK/s [|] [00:15:22 Elapsed Time] [Progress: 100 %] | Matching [451]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 1Ny8aax7gEkPtT8aCNS39TVFrh7JZ9jwzZ f0f8431252858a91243e218115e3b1dc4490ad88        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^                                  ^ ^ ^^^        ^^        ^^^   ^^^ ^^  ^        |
|------------------------------------------------------------------------------------|
|  Public Key  : 0243F44F978BFD6128CE9831B54A922DBE6151A3FE8BC1378456424351C09E7416  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FF29A91CF5    |
======================================================================================

[/] Total Speed: 1217.31 MK/s [/] [00:15:23 Elapsed Time] [Progress: 100 %] | Matching [452]

======================================================================================
|                    Total Matching character in hash160: 16                         |
|------------------------------------------------------------------------------------|
| 13eFDtwBaRtoDQrg2SHDpLmjBRCSMN3U6s 1cfb83ad28b5f911938bfa9af53358274fb0c50b        |
| 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8        |
| ^      ^                             ^  ^ ^^ ^ ^  ^  ^   ^^^^ ^    ^  ^ ^          |
|------------------------------------------------------------------------------------|
|  Public Key  : 023302A7435D28FCC2F89BFF0C4179373293E752233AC86AD63FDBB884D520340A  |
|  Private Key : 000000000000000000000000000000000000000000000040000000FF4A299A3A    |
======================================================================================

[\] Total Speed: 1235.12 MK/s [\] [00:15:25 Elapsed Time] [Progress: 100 %] | Matching [453]

==================================== [ KeySpace End ] ================================

But remember, all of these are absurd.

[crypto_user_new]

This is just random data. This program is doing exactly what vanity is doing...generate and after that make a filter...Now depends where you want to make the filter on GPU or CPU for accuracy.
Vanity is doing on GPU  on prefix search, but you can implement also the suffix filter or even hash160 filter as you want.
I have now based on hash160 20 characters matching and on BTC address something similar, but is not helping me with anything...just random data that is matching.

[detechs]

Your fruit is not ripe enough, I leave the garden. As is has been sprayed with pesticide by its owner. I now return back to the current garden. With my willing prize in hand. No reason for me to return. Thank you, from aotearoa.

[satashi_nokamato]

I strongly doubt that other than a few highly skilled coders being a member of this forum any one else know or even care about this.

If you want a global effort with all hands on, spend 100BTC to advertise first, and then let go of 10 K BTC by distributing them over several addresses.  Let the unaware geniuses of coding and math rush to the place and start a brain storm on how to find short cuts.

Anyways, working on puzzles above 70 is a total waste of time, ok maybe not 70 but above 75.

[Realman121]

No mathematical function has been found that generates a sequence of known keys.
No recurrent relationship was found between neighboring keys.
No signs of a simple PRNG or a known generator were found.
No statistically significant internal structure was found to predict the following keys.
No signs of encoding of physical quantities, physical objects, or known physical laws were found.
No evidence of correspondence to models of quantum mechanics, fields, waves, or other physical systems was found.
No signs were found that the keys are states of any known dynamic system.
No evidence has been found for analogies with game theory (including chess) that would allow the recovery of unknown keys.
No signs of musical, geometric, symmetrical, or other compositional structure suitable for sequence prediction were found.
No key representation was found that would give an advantage when searching for the next unknown keys.

You've got a big schedule of "no" but is it enough?
So I add some "no" in my little list so as never to forget.

No vulnerability Elliptic Curve - not even up for discussion.
No algorithm inventing to help to fracture this conundrum.
No secret that there is not a cyclic process - nothing but chance.
No hidden pattern in this challenge.
No playing some sort of game - no need to decide but it is good to improve memory.

On one day a couple years ago I started looking the solution of this puzzle.
How much it will be in the next - three years? or this Fall? more? and now it's like pain to pack all my life in hurry.
Well-nevermind.
Until we find.
And the further I search - I think it is pointless to count the grains of sand in the sand.

But it's interesting to read the new capabilities of people and learn more that have.
As said user "eo_aa6b_ux" -
sorry, I don't remember what page was it -  "As some day it may hapen that answers must be found.
May be in one standart day. But it's doesn't matter who offer that decision to community. Don't miss that day. I really wished to you won your main purpose and secondary goals".

And as said user "by_path_ca_for5tune"
"Let me spill the tea for you - it was made with glue and don't ran so fast because you can stumble and what - of course all of us taunt you. Time goes" - we can believe that it being some nice joke but he's good human. 

PS. I'd like to have that unnamed exp. AI with "super power" that escaped - to solve this puzzle.
Nevermind. Take care.

[NUCLEAR7.1]

Proposed Redistribution Analysis of the Bitcoin Puzzle Rewards

To fund Puzzles 71 through 83, the creator must move the Bitcoin from the addresses of Puzzles 84–160 (excluding 135/140/145 to 160). Since the total reward for all 78 unsolved puzzles is 916.5 BTC, no new capital is introduced — the funds are simply reallocated from the higher, currently less attractive puzzles into the more acceptable  71–83 puzzles.

Analysis Date: July 2026  •  Reference Bitcoin Price ≈ $64,290

1. Current State of the Bitcoin Puzzle

• The challenge consists of 160 puzzles, each corresponding to a private key search space whose bit length matches the puzzle number.
• 82 puzzles have already been solved (Puzzles 1–70 in full, plus every multiple of five through Puzzle 130: 75, 80, 85...130).
• 78 puzzles remain unsolved, carrying a fixed combined reward of 916.5 BTC.
• The current reward for each unsolved puzzle follows this formula:
  
  Reward = Puzzle Number ÷ 10 BTC
  Example: Puzzle 71 currently pays 7.1 BTC.
• Six unsolved puzzles have had their public keys exposed since 2019: 135, 140, 145, 150, 155, 160. In theory these become reachable via Pollard's Kangaroo algorithm rather than pure brute force.
• There are documented cases illustrating the risks of public-key exposure: during the solving of Puzzles 66 and 69, attackers front-ran the original broadcast transactions in the mempool and claimed the rewards before confirmation.

2. Proposal — Reward Equal to Puzzle Number (BTC) for Puzzle 71 and Above

The proposal raises the reward of each eligible unsolved puzzle from:

Puzzle Number ÷ 10 BTC  →  Puzzle Number BTC

while keeping the total combined reward unchanged at 916.5 BTC. No external funding is required, and the six puzzles with exposed public keys (135–160) are intentionally left untouched, serving as a natural benchmark for tracking progress on Kangaroo-based attacks.


3. Scenario: Leaving Puzzles 135–160 Out of the Redistribution

If Puzzles 135, 140, 145, 150, 155, and 160 are left out of the redistribution — keeping their current rewards unchanged — their combined value is 88.5 BTC (13.5 + 14 + 14.5 + 15 + 15.5 + 16).

This reduces the amount available for redistribution from 916.5 BTC to 828 BTC.

Assuming each puzzle's new reward equals its own number, the cumulative allocation proceeds as follows:

Code:

Puzzle | New Reward (BTC) | Cumulative Total | Remaining of 828 BTC
-------|-------------------|-------------------|-----------------------
71     | 71                | 71.0              | 757.0
72     | 72                | 143.0             | 685.0
73     | 73                | 216.0             | 612.0
74     | 74                | 290.0             | 538.0
76     | 76                | 366.0             | 462.0
77     | 77                | 443.0             | 385.0
78     | 78                | 521.0             | 307.0
79     | 79                | 600.0             | 228.0
81     | 81                | 681.0             | 147.0
82     | 82                | 763.0             | 65.0
83     | 83                | 846.0             | −18.0  ← shortfall begins here

Puzzle Overview

Puzzles that can be fully funded:

• 71
• 72
• 73
• 74
• 76
• 77
• 78
• 79
• 81
• 82

Puzzles left out of the redistribution:

• 135
• 140
• 145
• 150
• 155
• 160

Puzzles not included because they are already solved:

• 75
• 80
• Every multiple of five from 85 through 130

Outcome

Under this scenario, only 10 puzzles can be fully funded — Puzzles 71 through 82, excluding 75 and 80, which are already solved. This requires a total of 763 BTC, leaving 65 BTC unused. That remainder is not enough to fund Puzzle 83, which requires 83 BTC, producing a shortfall of 18 BTC. The puzzle creator could close this gap by contributing the difference from an external source, without touching any of the already-funded rewards.

In short, leaving Puzzles 135, 140, 145, 150, 155, and 160 unchanged reduces the amount available for redistribution to 828 BTC, setting the practical ceiling at Puzzle 82. Funding Puzzle 83 within that amount is not possible without additional external contribution.


4. Puzzle Data — Bit Length, Key Range & Reward (Puzzles 71–83)

Code:

Puzzle | Bits | Key Range Start (hex)         | Key Range End (hex)             | Reward   | USD Value
-------|------|-------------------------------|-----------------------------------|----------|---------------
71     | 71   | 0x400000000000000000          | 0x7fffffffffffffffff              | 71 BTC   | $4,564,590
72     | 72   | 0x800000000000000000          | 0xffffffffffffffffff               | 72 BTC   | $4,628,880
73     | 73   | 0x1000000000000000000         | 0x1ffffffffffffffffff              | 73 BTC   | $4,693,170
74     | 74   | 0x2000000000000000000         | 0x3ffffffffffffffffff              | 74 BTC   | $4,757,460
75     | 75   | (already solved)              | (already solved)                   | —        | —
76     | 76   | 0x8000000000000000000         | 0xfffffffffffffffffff              | 76 BTC   | $4,886,040
77     | 77   | 0x10000000000000000000        | 0x1fffffffffffffffffff             | 77 BTC   | $4,950,330
78     | 78   | 0x20000000000000000000        | 0x3fffffffffffffffffff             | 78 BTC   | $5,014,620
79     | 79   | 0x40000000000000000000        | 0x7fffffffffffffffffff             | 79 BTC   | $5,078,910
80     | 80   | (already solved)              | (already solved)                   | —        | —
81     | 81   | 0x100000000000000000000       | 0x1ffffffffffffffffffff            | 81 BTC   | $5,207,490
82     | 82   | 0x200000000000000000000       | 0x3ffffffffffffffffffff            | 82 BTC   | $5,271,780
83     | 83   | 0x400000000000000000000       | 0x7ffffffffffffffffffff            | 83 BTC   | $5,336,070

5. Puzzle Classification

Code:

Category                                    | Puzzles
---------------------------------------------|------------------------------------------------
Fully funded (proposed)                     | 71, 72, 73, 74, 76, 77, 78, 79, 81, 82
Left unchanged (Kangaroo benchmark)         | 135P (2^67.5), 140P (2^70), 145P ( 2^72.5), 150P ( 2^75), 155P (2^77.5), 160P ( 2^80)
Already solved                              | 75, 80, and every multiple of five from 85–130

6. Totals

Code:

Group                        | BTC       | USD Value
------------------------------|-----------|------------------
Fully funded (71–82)         | 763 BTC   | $49,053,270
Left unchanged (135–160)     | 88.5 BTC  | $5,689,665

7. Why Funding Puzzles 71–82 Is a Rational Choice

• Every puzzle in this range is an address-only target with no exposed public key.
• Pure brute force remains the only known method of attack.
• Required computation roughly doubles with each additional bit, which is why the rewards became economically unattractive.
• Raising the reward to roughly $4.5–5.3 million per puzzle creates a much stronger incentive for serious investment in GPU/FPGA hardware.

Important Point

A higher reward strengthens the economic incentive but does not eliminate the underlying computational difficulty. Current estimates suggest Puzzle 71 alone would still require roughly 421 years using today's publicly known aggregate computing power. Larger rewards could attract significantly more resources, but expected solving time would likely remain measured in decades rather than months — especially for higher-bit puzzles approaching Puzzle 82.

8. General Security Consideration

Any on-chain movement of funds inevitably reveals the corresponding public key once the spending transaction is broadcast. This opens a potential attack window in the mempool, particularly for puzzles whose key sizes sit close to those already compromised — such as Puzzles 66 and 69. It is recommended to use the Marapool slipstream service.

— Sorry if there are any mistakes.  Translation used  —

[detechs]

sorry I lied I'm back and I bring ripe fruit, currently mining the twin sha256 genesis blockchain, called taatautatau or chain3 it brings base 2 binary up to base 3, if my test run is successful I will broadcast to bitcoins genesis and see if it accepts the merge. Nothing harmful should happen to the blockchain, all new funds mined go to satoshis addresses. The block chain continues, but there will now be a verifier slowly crawling up from genesis, like a snail that never stops. Brute force will always hit a wall. But the snail will always continue no matter what. You either accept it and change to an ascending path or you eventually meet the snail. It's up to you all. mauri ora

[fecell]

How are 77 bits cracked in seconds?!

i have huge PTX optimized own app, but i'm shocked...

Code:

total bits: 135
range bits: 109
total iterations: 324,518,553,658,426,726,783,156,020,576,256
range step:       382,071,429,525,264,239,678,174,997,818,125
steps count:      57,000,000
total checks:     18,497,557,558,530,323,426,639,893,172,846,592,000,000

[!] Initializing GPU secp256k1...
Initializing secp256k1 for GPU...
secp256k1 constants initialized on GPU
Initializing precomputed table for base point G...
Table size: 256 entries (0.02 MB)
Precomputed table initialized successfully in global memory
secp256k1 GPU initialization complete!

=== GPU Device Information ===
Device Name:                NVIDIA GeForce GTX 1650 Ti
Compute Capability:         7.5
CUDA Driver Version:        13.3
CUDA Runtime Version:       13.3
Total Global Memory:        4.00 GB
Shared Memory per Block:    48.00 KB
Max Threads per Block:      1024
Max Block Dimensions:       1024 x 1024 x 64
Max Grid Dimensions:        2147483647 x 65535 x 65535
Warp Size:                  32
Number of Multiprocessors:  16
Memory Bus Width:           128 bits
Free Memory at startup:     3.21 GB
Total Memory (system view): 4.00 GB
===============================

[!] Allocating GPU memory...
[+] Base points loaded: basepoints_P135_step57000000.dat (57000000 entries)
[+] Check points loaded: checkpoints_P135_step57000000.dat (114000000 entries)
[+] Check map loaded: checkmap_P135_step57000000.dat (114000000 entries)
[+] Bloom filter loaded: bloom_P135_step57000000.dat (2185393344 bits, 13 hashes)
[!] Resuming from counter: 6,498,279,296
[!] Previous elapsed: 22:12:01

[!] Starting search...
[+] [8,318,960,000] S: 4638390344643.7 it/s, TE: 1d 04:23:49, E: 06:11:48, ETA: 126456304624308436992y

[crypto_user_new]

I am almost close: playing with the keys, the next jrG will be the key

1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB
1PWo3JeBjrG9NriYKvHamQknJEydb7su5y
1PWo3JeBFGyFqhK6a58EVxhxhBEjrGzSNx
1PWo3JeBDVjrG9Y88qM5n7AwxxgP6hdozP
1PWo3JeBUzuHQ4F2FzM3zbo7LdFWEjrGfx
1PWo3JeBW8TqBSBjrGNEBmbxbRwCxWSTCK
1PWo3JeBSUCyQwhLQtGYc2LLzPmugjrGKT