== Bitcoin challenge transaction: ~1000 BTC total bounty to solvers! ==UPDATED==

[ColorlessK]

...

You don't seem to have read a lot first in this thread, did you?

All puzzles which are multiples of 5 have their public key deliberately exposed. Only for those you could use methods like Kangaroo. Next unsolved in this category is puzzle #135 which still needs computing power expensive enough that is's likely in the ballpark of the puzzle's prize, of course depending on how fast the solver wants to solve it. (I haven't done the calculation, it's an educated guess and depending how "lucky" one could be).

Unsolved Puzzle #71 and onward, not divisible by 5 has no exposed public key, so you can only scan the key space by any brute-force method you deem fit or "more successful" than simple scanning from one end or another (there seems to be no superior method from my humble understanding, but you can believe what you want).

Thanks for the answer Cricktor. I saw that, I was a bit confused about the fact that P2PKH keys are public and honestly did not really understand at first that it is merely a hash and not the public key itself. Still lots of learning to do, I don't expect I'll ever be able to solve one of the keys but this seemed like a fun challenge and wanted to get in on the fun.

So I'm guessing for all the puzzles that aren't solved people use VanitySearch or Bitcrack? Vanitysearch site seems to be down though, where can one find it now ? Anyway, thanks again for the answer

[AdaSl0t]

...

You don't seem to have read a lot first in this thread, did you?

All puzzles which are multiples of 5 have their public key deliberately exposed. Only for those you could use methods like Kangaroo. Next unsolved in this category is puzzle #135 which still needs computing power expensive enough that is's likely in the ballpark of the puzzle's prize, of course depending on how fast the solver wants to solve it. (I haven't done the calculation, it's an educated guess and depending how "lucky" one could be).

Unsolved Puzzle #71 and onward, not divisible by 5 has no exposed public key, so you can only scan the key space by any brute-force method you deem fit or "more successful" than simple scanning from one end or another (there seems to be no superior method from my humble understanding, but you can believe what you want).

Thanks for the answer Cricktor. I saw that, I was a bit confused about the fact that P2PKH keys are public and honestly did not really understand at first that it is merely a hash and not the public key itself. Still lots of learning to do, I don't expect I'll ever be able to solve one of the keys but this seemed like a fun challenge and wanted to get in on the fun.

So I'm guessing for all the puzzles that aren't solved people use VanitySearch or Bitcrack? Vanitysearch site seems to be down though, where can one find it now ? Anyway, thanks again for the answer

https://github.com/10gic/vanitygen-plusplus

But it will take etarnal time.

[Cricktor]

Normal vanitysearch is completely the wrong tool to attack any of the remaining puzzle due to the way "normal" vanitysearch works.

Because I don't care to hunt for a puzzle solution myself, I don't know if there are variants of vanitysearch that can pay tribute to the limited key space range of a certain puzzle. I guess there are, because otherwise it won't make any sense at all.

From my understanding of traditional vanitysearch (I used it years ago myself to create a few "vanity" legacy addresses), it iterates and creates randomly generated private keys, derives the (computationally expensive) public key and from that the public address to check if it meets your "vanity look" criteria.

For one of the puzzles without a public key your "vanity" address is the given puzzle's public address, so you need to match a whole 160bit hash, well, the whole P2PKH public address in the end. Your sole bonus is that a puzzle's key space region is artificially limited by design rules of the puzzle, but still pretty huge for puzzle #71 and the next unsolved puzzle doubles it with each increment.

Any software that doesn't use GPU compute power isn't worth the energy and time, that should be pretty obvious.

[mahurovihamilo]

Hi there,

Is this challenge still going today in 2025? is it worth putting my GPU rig to work on it?  Thanks.

[AdaSl0t]

Hi there,

Is this challenge still going today in 2025? is it worth putting my GPU rig to work on it?  Thanks.

Until the last private key is solved, the puzzle is not solved, so yes, this  challenge continues.
https://privatekeys.pw/puzzles/bitcoin-puzzle-tx
For this addr (as previous gentlemens tell, without public key Kangoroo will not effective)
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
start searching in next ranges:
86.1%:0x771a9fbe76c8b43957
86.8%:0x778d4fdf3b645a1cab
or in this:
13.2%:0x4872b020c49ba5e354
13.9%:0x48e5604189374bc6a8

[kTimesG]

For this addr (as previous gentlemens tell, without public key Kangoroo will not effective)
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
start searching in next ranges:
86.1%:0x771a9fbe76c8b43957
86.8%:0x778d4fdf3b645a1cab
or in this:
13.2%:0x4872b020c49ba5e354
13.9%:0x48e5604189374bc6a8

Great. We just need someone to grant us 25.000 $ to scan those tiny ranges so we can add them to either the "it's not there, man" or the "yey, key was found" public knowledge. Risk/reward ratio: 70 in 71 chances that the money's gone.

[shenzhou680]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

[AdaSl0t]

#71 the captital privatekey is 7C

Thank you. Open your PM.
Oh. I think than you tell me about public key.
And #71 is
 
Key Range (Bits):
270...271
Key Range (HEX):
400000000000000000:7fffffffffffffffff
Bitcoin Address:
C
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
https://privatekeys.pw/puzzles/bitcoin-puzzle-tx

[AdaSl0t]

Okay, this is going to be harder than I expected. aLL SCRIPTsIG CONTAINS pub keys from other addresses. How can I extract pubkey from witness (I do not found any way to do it)?

Transaction ID: 8aa20456d64c7969d0546cd819437275e78d9bcbc692e93b26129faa98de5cd7
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 10975}]
Outputs: [{'witness': '76a91405c7080643ca36e4334a3bbe0cb5c816c88754f188ac', 'amount': 1}, {'witness': '76a91405c7080bdbd71e0d5c6e9db2f9076be2c241bf6888ac', 'amount': 1}, {'witness': '76a91405db3044a8f6ccdb106cd48ea899a4a97394faca88ac', 'amount': 1}, {'witness': '76a91405db30a4dc9471f12250156e5a107ebf3f8a3a4588ac', 'amount': 1}, {'witness': '76a91405db322d80caa87aff32461588b78ea76c70f24188ac', 'amount': 1}, {'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 2}, {'witness': '00148696b4773069de76e56830f625f02b0e909e3e5a', 'amount': 9670}]
========================================
Transaction ID: 9540c7d4ca42c32cafa643f4dd3f0a4c3beca2fc3c585cd980f474acb6a0267c
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 622400}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 1000}, {'witness': '0020b683fe45faef7631fb5e9a7b420f599487308ddfdbdce8bbec7e16cf018376a3', 'amount': 621200}]
========================================
Transaction ID: c03df28a719a110c50b51e92a0831c28433d6b12180a94e63c4c519b28654e1b
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': '47304402203050be2ecc233b838d42e481dd6e5b7c7d75a6288a8a2095ae2dda638514d6e402206 5173288a1b5ef74521ecc6a97fc5dcf34b2e21bb691ce99ba8258e41813c5a50121033055ad5087 044775129386be7d3a463b5c2da11d01c6fc820519488d217950d5', 'amount': 7226}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 898}, {'witness': '76a9141ea6c20c43168d397c6b2f2d7730b78cd3219dbf88ac', 'amount': 5824}]
========================================
Transaction ID: dc895ad8b1eb570560326bd0f9c8504304cf03f51c0ce2a753fc4cf29108d24b
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 9012}]
Outputs: [{'witness': '6a1549274d2041424f555420544f2047455420594f5521', 'amount': 0}, {'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 710}, {'witness': '0014b49e238dac40602ddb7e794234f90282d6a0a743', 'amount': 7701}]
========================================
Transaction ID: 966c854ce03054ef38f6fdf5ee9a746f03bb34d2ec86101e214d22b2f15b0f0f
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 15622}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 1767}, {'witness': '00149ba6f76c4851618c96be8cb752a4b5d59044f393', 'amount': 13581}]
========================================
Transaction ID: 72fa88fe21d2cb40c1af0a3022d4e5736ae1c66c6f1afe72463e1791706629c5
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 5734}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 1000}, {'witness': '0014db68c4ed2eaaf5987c0b5333d338223e77314772', 'amount': 4302}]
========================================
Transaction ID: e29e1a2200867cbd886a42c8222f0dee1a53b83aa577df5e477d11e3fa9e90cc
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': '47304402202c34c15067877dd7a47bb14fb9d5c25e4629258a76752b597d4e62280ace541302206 5af77b6232cb0bcb3f083bfacfaf258e503bf8180fe24c5017690803d41318b012102416e5c98ef 14620fdfa557b2b9ec278e9215c18bba2fdd6b954544f1ade0f36e', 'amount': 532300}]
Outputs: [{'witness': '6a45757365206274636b657967656e2e636f6d202d2066697273742076697375616c20626974636 f696e2076697375616c2067656e657261746f722c2073696e63652032303139', 'amount': 0}, {'witness': '76a91404e0fb570daf91ea5cb64443d05989979a6716de88ac', 'amount': 522500}, {'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 8880}]
========================================
Transaction ID: 076d820e3100580012a1bcca15987c0d8638cae912f1f4421f05e97cbcdec3b9
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 12136}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 1}, {'witness': '76a914f6f5431d25bbf7ca7bffba74248c39d5fca025b088ac', 'amount': 1}, {'witness': '0014d9833b60c5663b3ef0f027398a770ccc8eaa081d', 'amount': 11600}]
========================================
Transaction ID: b30914607fed925b42a87004ed3b373bd413ac35302d007f28ffbb738c63245e
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': None, 'amount': 191912}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 1000}, {'witness': '00146483b812bc02e434b7a96232344a477e68679f17', 'amount': 147700}]
========================================
Transaction ID: 8c75b040d6f335cd1965b205938435baa6bb1b8a2b00038f71d991fd3c7dc0b7
Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Inputs: [{'scriptSig': '47304402201fa0f3efdcf5c8d60ddd58b8ad42c412243e931d9549a49773255dcdbf78c7e102201 41dcae8c0feb2d85b469209b10dc60cf8a0b7c5a638241f80a2cbe9b090d008012102fba7a69f53 850585d5bdcb4653e3570c1d461ee17672de2d17b82ce286a55d79', 'amount': 794}]
Outputs: [{'witness': '76a914f6f5431d25bbf7b12e8add9af5e3475c44a0a5b888ac', 'amount': 600}]
========================================

Best regards, Ada Sl|_|t. 

[kTimesG]

Okay, this is going to be harder than I expected. aLL SCRIPTsIG CONTAINS pub keys from other addresses. How can I extract pubkey from witness (I do not found any way to do it)?

There's no public key to extract from P2PKH UTXOs. Also, those are not even SegWit transactions, your decoded data makes no sense. Your "witnesses" are simply unlocking scripts containing the H160 20-byte values ("Bitcoin address"), which is what you're supposed to crack (assuming you understand the challenge itself, which is somehow like the first page to grasp, in any solver's schoolbook).

[randyrafaelcg]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

What makes you say that with such a confidence? 

[AdaSl0t]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

What makes you say that with such a confidence? 

Can I ask you is there any effectively algorithms than Kangaroo?

[randyrafaelcg]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

What makes you say that with such a confidence? 

Can I ask you is there any effectively algorithms than Kangaroo?

I am currently trying in a pool, you can find info in the github repo bitcrackrandomiser from ilkerccom, I am currently getting like ~300Mkey/s, the good thing of the pool is you avoid repeated and alredy tried ranges, and you can test different methods like bitcrack, vanity search.... I am still looking for a better ways to do it, but couldn't find a way. It is sad I feel like this is more for big farms who can afford real compute power, they have best odds 

[AdaSl0t]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

What makes you say that with such a confidence? 

Can I ask you is there any effectively algorithms than Kangaroo?

I am currently trying in a pool, you can find info in the github repo bitcrackrandomiser from ilkerccom, I am currently getting like ~300Mkey/s, the good thing of the pool is you avoid repeated and alredy tried ranges, and you can test different methods like bitcrack, vanity search.... I am still looking for a better ways to do it, but couldn't find a way. It is sad I feel like this is more for big farms who can afford real compute power, they have best odds 

Hmm... Okay, Docker... Using Docker or using Visual Studio. I don't even know which is worse. Are there any other options? And then, no one will give a guarantee that the pool is not a scam or an attempt to use your computing power for something. Okay, I'll throw out an idea - what if we make a board on FPGA, or even remake (using custom firmware+reverse engineering ) the so-called miner, for calculations in a given range?

Best regards, Ada.

[randyrafaelcg]

#71 the captital privatekey is 7C


#71 from 7c0000000...to  7cffffffff... have fun donate：1KGK6QdVqszsPYpn1UGSbJLj2AnzUTTf1H

What makes you say that with such a confidence? 

Can I ask you is there any effectively algorithms than Kangaroo?

I am currently trying in a pool, you can find info in the github repo bitcrackrandomiser from ilkerccom, I am currently getting like ~300Mkey/s, the good thing of the pool is you avoid repeated and alredy tried ranges, and you can test different methods like bitcrack, vanity search.... I am still looking for a better ways to do it, but couldn't find a way. It is sad I feel like this is more for big farms who can afford real compute power, they have best odds 

Hmm... Okay, Docker... Using Docker or using Visual Studio. I don't even know which is worse. Are there any other options? And then, no one will give a guarantee that the pool is not a scam or an attempt to use your computing power for something. Okay, I'll throw out an idea - what if we make a board on FPGA, or even remake (using custom firmware+reverse engineering ) the so-called miner, for calculations in a given range?

Best regards, Ada.

Fair enough, I've actually made a few changes on my end. Instead of using the pool’s prebuilt apps, I pointed the pool at the original BitCrack implementation by brichard19. I reviewed the pool’s code and didn’t see anything obviously malicious, but if you’re worried you can always run the original BitCrack (for puzzle 71) or Keyhunt bsgs mode (for puzzle 135) yourself.

I don’t think repurposing a mining ASIC is feasible: those chips and devices aren’t built for ECC scalar multiplications (the heavy math used to convert a private key into a secp256k1 public key) they only do SHA-256 hashing, not elliptic-curve math, so you’d need custom hardware/firmware and massive effort to make it worth it. Realistically the best options are either renting more compute power or join a pool. I try renting and tested Keyhunt on an AMD Ryzen 9 9950X3D with 96 GB RAM and saw around 2 Ekey/s, and with a RTX 5090 for BitCrack tests and got about 3900 Mkey/s. Even with those numbers, the odds of finding a target key for 71 or 135 are effectively zero, basically hundreds if not thousands of years on average. That’s why this kind of game favors big farms that can spend thousands on compute, for the rest of us it’s essentially gambling with almost no chance of success. But at least you can learn a few things about how bitcoin works and you realize how safe it actually is

[DrShams]

obviously ... it getting harder and harder
no one was able to crack it till now 
no solution yet for 135 or even 71

[FREIVOGEL231]

Perhaps a relationship with the Genesis block is there
Yes you may have group of number with no pattern but if you looked at where it all began you might find answers

Numbers are a pattern even if you choose to pick random mathematics they tend to unfold the more you go further

This is a list of keys that was produce using master key
Masking master key digits incrementaly (0000000000000000000000000000000000000000000004c5ce114686a1336e07)



1   2f6dafcbacd9e1ef15659
2  3a76cff6bedcce4bf09edf9
3  85c8b807e40cc2413a21011f9
4  479bd8cc6d5be75e1f35d391f9
5  49fa92c5870336903b71d6ccc91f9
6  4b2b80a74f0d38a7a8a78fb1ecc91f9
7  4bc429b526a1e2076667c29b15ecc91f9
8  4c10847fb0e2bd8bc745e5cc0795ecc91f9
9  4c36b2ad69d200ba51f5d1faf99795ecc91f9
10 4c49c9dd54c37d03b45fe47ea0ab9795ecc91f9
11 4c5355786c0b767eadc8fb4f1356eb9795ecc91f9
12 4c581b465be95aa6f3889a3321aa1eeb9795ecc91f9
13 4c5a7e2d605f89a86f89d0a66d74831eeb9795ecc91f9

14
4c5bafa0e42b88c6d8ae98c4cdb7cfa31eeb9795ecc91f9

15 4c5c485aa643a549c2a5827099b70333a31eeb9795ecc91f9

16  4c5c94b78755f729ae4d87fa1336e06fb3a31eeb9795ecc91f9

17  4c5cbae5f7dfe88d72f71cd54266dc0dffb3a31eeb9795ecc91f9

18  4c5ccdfd3024fa4dcf269985a84cdb81bfffb3a31eeb9795ecc91f9

19  4c5cd788cc47864fcc79ae2635099b7037ffffb3a31eeb9795ecc91f9

20  4c5cdc4e9a58ccb5050aa33f86a1336e06ffffffb3a31eeb9795ecc91f9

21
4c5cdeb181616ff428900b2550d4266dc0dfffffffb3a31eeb9795ecc91f9

22
4c5cdfe2f4e5c1954b3a5cc35a1a84cdb81bffffffffb3a31eeb9795ecc91f9

This was made by specific pattern sequence for masking a Main Wallet by false ones

[AdaSl0t]

Perhaps a relationship with the Genesis block is there
Yes you may have group of number with no pattern but if you looked at where it all began you might find answers

Numbers are a pattern even if you choose to pick random mathematics they tend to unfold the more you go further

This is a list of keys that was produce using master key
Masking master key digits incrementaly (0000000000000000000000000000000000000000000004c5ce114686a1336e07)



1   2f6dafcbacd9e1ef15659
2  3a76cff6bedcce4bf09edf9
3  85c8b807e40cc2413a21011f9
4  479bd8cc6d5be75e1f35d391f9
5  49fa92c5870336903b71d6ccc91f9
6  4b2b80a74f0d38a7a8a78fb1ecc91f9
7  4bc429b526a1e2076667c29b15ecc91f9
8  4c10847fb0e2bd8bc745e5cc0795ecc91f9
9  4c36b2ad69d200ba51f5d1faf99795ecc91f9
10 4c49c9dd54c37d03b45fe47ea0ab9795ecc91f9
11 4c5355786c0b767eadc8fb4f1356eb9795ecc91f9
12 4c581b465be95aa6f3889a3321aa1eeb9795ecc91f9
13 4c5a7e2d605f89a86f89d0a66d74831eeb9795ecc91f9

14
4c5bafa0e42b88c6d8ae98c4cdb7cfa31eeb9795ecc91f9

15 4c5c485aa643a549c2a5827099b70333a31eeb9795ecc91f9

16  4c5c94b78755f729ae4d87fa1336e06fb3a31eeb9795ecc91f9

17  4c5cbae5f7dfe88d72f71cd54266dc0dffb3a31eeb9795ecc91f9

18  4c5ccdfd3024fa4dcf269985a84cdb81bfffb3a31eeb9795ecc91f9

19  4c5cd788cc47864fcc79ae2635099b7037ffffb3a31eeb9795ecc91f9

20  4c5cdc4e9a58ccb5050aa33f86a1336e06ffffffb3a31eeb9795ecc91f9

21
4c5cdeb181616ff428900b2550d4266dc0dfffffffb3a31eeb9795ecc91f9

22
4c5cdfe2f4e5c1954b3a5cc35a1a84cdb81bffffffffb3a31eeb9795ecc91f9

This was made by specific pattern sequence for masking a Main Wallet by false ones

So, you telling that you figured out the pattern?  Can you tell me a link to tool for "masking".

[FREIVOGEL231]

Perhaps a relationship with the Genesis block is there
Yes you may have group of number with no pattern but if you looked at where it all began you might find answers

Numbers are a pattern even if you choose to pick random mathematics they tend to unfold the more you go further

This is a list of keys that was produce using master key
Masking master key digits incrementaly (0000000000000000000000000000000000000000000004c5ce114686a1336e07)



1   2f6dafcbacd9e1ef15659
2  3a76cff6bedcce4bf09edf9
3  85c8b807e40cc2413a21011f9
4  479bd8cc6d5be75e1f35d391f9
5  49fa92c5870336903b71d6ccc91f9
6  4b2b80a74f0d38a7a8a78fb1ecc91f9
7  4bc429b526a1e2076667c29b15ecc91f9
8  4c10847fb0e2bd8bc745e5cc0795ecc91f9
9  4c36b2ad69d200ba51f5d1faf99795ecc91f9
10 4c49c9dd54c37d03b45fe47ea0ab9795ecc91f9
11 4c5355786c0b767eadc8fb4f1356eb9795ecc91f9
12 4c581b465be95aa6f3889a3321aa1eeb9795ecc91f9
13 4c5a7e2d605f89a86f89d0a66d74831eeb9795ecc91f9

14
4c5bafa0e42b88c6d8ae98c4cdb7cfa31eeb9795ecc91f9

15 4c5c485aa643a549c2a5827099b70333a31eeb9795ecc91f9

16  4c5c94b78755f729ae4d87fa1336e06fb3a31eeb9795ecc91f9

17  4c5cbae5f7dfe88d72f71cd54266dc0dffb3a31eeb9795ecc91f9

18  4c5ccdfd3024fa4dcf269985a84cdb81bfffb3a31eeb9795ecc91f9

19  4c5cd788cc47864fcc79ae2635099b7037ffffb3a31eeb9795ecc91f9

20  4c5cdc4e9a58ccb5050aa33f86a1336e06ffffffb3a31eeb9795ecc91f9

21
4c5cdeb181616ff428900b2550d4266dc0dfffffffb3a31eeb9795ecc91f9

22
4c5cdfe2f4e5c1954b3a5cc35a1a84cdb81bffffffffb3a31eeb9795ecc91f9

This was made by specific pattern sequence for masking a Main Wallet by false ones

So, you telling that you figured out the pattern?  Can you tell me a link to tool for "masking".

You don't get it
The Puzzle wasn't about cracking wallet keys
Most of all used wallet keys not even in these ranges you can't even search them that's why the Puzzle leakage of Public keys and also was reduced to 160
Puzzle itself was a mask it was testing mining abilities in indirect way mining and cracking keys are no different
I think if someone is able to manipulate the comparison between target and calculated hash blocks are instantly approved system is switched of and Mark My Words

[ludibtc99]

Can anyone share scanned or unscanned ranges for puzzle 71?

I can't see that info on pools on the Internet...

the pool sorts two puzzles 71 and 72 in order without losing speed

https://bitcoinpuzzle.ru/forum/bitcoinpuzzle.html