Search content
Sort by
Showing 20 of 44 results by MrGPBit
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I created this helper app, it has both the modes, auto or manual/personalized mode. In auto mode it first pick a random number and check if its it is already scanned or not and apply filters, if everything is ok it creates a command and pass it to new cmd and wait for the search to complete. It also has an option to divide the full rane in to multiple parts and search N number of ranges in each parts.
https://postimg.cc/6810xJJL
https://postimg.cc/w79Mg19g
[/quote]
Can you publish your app on github?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
P71.. 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
found 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
Does anyone have any idea how far apart the two might be (64bit?)
63f651bb9c47645cd6 1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU +64bit
649a3dd0486c96e70b 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
found 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH
Does anyone have any idea how far apart the two might be (64bit?)
63f651bb9c47645cd6 1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU +64bit
649a3dd0486c96e70b 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
Can you tell us the HEX code of 1PWo3JeB9jrG prefix thanks
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Why not reach these addresses yet?
Each of these is in completely different points, as I may think that there is no!
1PWo3JeB9jrGwfHDNpdGK54CRas7BJwzGg
1PWo3JeB9jrGwfHDNpdGK54CRas8JAZddJ
1PWo3JeB9jrGwfHDNpdGK54CRas7sVHpYM
Each of these is in completely different points, as I may think that there is no!
1PWo3JeB9jrGwfHDNpdGK54CRas7BJwzGg
1PWo3JeB9jrGwfHDNpdGK54CRas8JAZddJ
1PWo3JeB9jrGwfHDNpdGK54CRas7sVHpYM
1PWo3JeB9jrGwfHDNpdGK54CRas7o1Quvw
1PWo3JeB9jrGwfHDNpdGK54CRas7SKdbnS
1PWo3JeB9jrGwfHDNpdGK54CRas7JiafEz
1PWo3JeB9jrGwfHDNpdGK54CRas79PsfyU
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Quote
I also agree with your opinion. That user "@MrGPBit"
In the chat before me, I also asked the keys I had given and provided me, and now I wrote to me the philosopher wandering the keys !!! This means ridiculing the rest of the users, I only provided these to the progress of users' analysis to get the solution, and nothing else,
In the chat before me, I also asked the keys I had given and provided me, and now I wrote to me the philosopher wandering the keys !!! This means ridiculing the rest of the users, I only provided these to the progress of users' analysis to get the solution, and nothing else,
@mahmood1356
These prefixes belong
Wandering Philosopher
he published it for everyone
His statement
I haven't searched for 71 in a few weeks, and I am not sure I will get back to searching for it. I'm working on a bigger project and as all of us know, there are only so many minutes in a day lol. But I do have these 48+ bit h160 matches that maybe someone can find useful and maybe lead them to the target address. I am sharing because at the moment, they are of no value to me. Hopefully they will be for someone. Enjoy. Keep hunting. Shooters shoot!
And something you might want to know is the method I used to search for the prefixes—you can use this code, and it’s not difficult at all.
git clone https://github.com/brichard19/bitcrack.git
cd bitcrack
mkdir build
cd build
cmake ..
make
./bitcrack -c -t 256 -p 1PWo3JeB9j -r 400000000000000000:7FFFFFFFFFFFFFFFFF -o ~/Desktop/matching_prefixes.txt
You have not found the prefix, this prefix was published long time ago by the owner
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I also agree with your opinion. That user "@MrGPBit"
In the chat before me, I also asked the keys I had given and provided me, and now I wrote to me the philosopher wandering the keys !!! This means ridiculing the rest of the users, I only provided these to the progress of users' analysis to get the solution, and nothing else,
[/quote]
These prefixes belong
Wandering Philosopher
His statement
I haven't searched for 71 in a few weeks, and I am not sure I will get back to searching for it. I'm working on a bigger project and as all of us know, there are only so many minutes in a day lol. But I do have these 48+ bit h160 matches that maybe someone can find useful and maybe lead them to the target address. I am sharing because at the moment, they are of no value to me. Hopefully they will be for someone. Enjoy. Keep hunting. Shooters shoot!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
@MrGPBit
I wrote several times that this person is unreliable. I gave him another chance. But he has shown himself unreliable again.
Right now, he wants to come to our group all the time. By creating fake accounts.
He has no place in our group and is on the list of unreliable people.
https://i.ibb.co/VYTd5Wr9/Ekran-Al-nt-s.png
I also agree with your opinion. That user "@MrGPBit"I wrote several times that this person is unreliable. I gave him another chance. But he has shown himself unreliable again.
Right now, he wants to come to our group all the time. By creating fake accounts.
He has no place in our group and is on the list of unreliable people.
https://i.ibb.co/VYTd5Wr9/Ekran-Al-nt-s.png
In the chat before me, I also asked the keys I had given and provided me, and now I wrote to me the philosopher wandering the keys !!! This means ridiculing the rest of the users, I only provided these to the progress of users' analysis to get the solution, and nothing else,
@mahmood1356
You distribute the prefixes where Wandering Philosopher has made them public
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I mean these prefixes.
1PWo3JeB9jNkTL28QqVi3EvU93LJuZa4JR
1PWo3JeB9jP8jxGWV1eAGXThNbxEhtxuq4
1PWo3JeB9jPUEeDgSsBmZV2oxdmYtogaMX
1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak
1PWo3JeB9jS1ttWtFXgTCy2hnCYcW1dD6V
1PWo3JeB9jSUU4ueEp5sSK6i9P26yBWfJh
1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD
1PWo3JeB9jSiimGHNbZUoc9hfVe9Ko5SGr
1PWo3JeB9jT926gmLys26TBwr6pwStgwLb
1PWo3JeB9jUAfYHTXQjUYuS6timskdRieF
1PWo3JeB9jUiESdtipzxqWJWTANVYiydnN
1PWo3JeB9jV9ZdU1LBAwHodBvV8fRZdZ1w
1PWo3JeB9jVxkSLg1WgymVexXayVHeBGSM
1PWo3JeB9jVyFtMXcuR7ffrdPkNSLgsePc
1PWo3JeB9jY39MsnvSJSVCdaJegFQzxvzV
1PWo3JeB9jZt9nTjxVcQu2aNrNwEenZcjG
1PWo3JeB9jdMGJNFxwckqgV7HxyrRxWL9R
1PWo3JeB9jddiHUfRfYqBAVjd6HRMEoycu
1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU
1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2
1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw
1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jNkTL28QqVi3EvU93LJuZa4JR
1PWo3JeB9jP8jxGWV1eAGXThNbxEhtxuq4
1PWo3JeB9jPUEeDgSsBmZV2oxdmYtogaMX
1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak
1PWo3JeB9jS1ttWtFXgTCy2hnCYcW1dD6V
1PWo3JeB9jSUU4ueEp5sSK6i9P26yBWfJh
1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD
1PWo3JeB9jSiimGHNbZUoc9hfVe9Ko5SGr
1PWo3JeB9jT926gmLys26TBwr6pwStgwLb
1PWo3JeB9jUAfYHTXQjUYuS6timskdRieF
1PWo3JeB9jUiESdtipzxqWJWTANVYiydnN
1PWo3JeB9jV9ZdU1LBAwHodBvV8fRZdZ1w
1PWo3JeB9jVxkSLg1WgymVexXayVHeBGSM
1PWo3JeB9jVyFtMXcuR7ffrdPkNSLgsePc
1PWo3JeB9jY39MsnvSJSVCdaJegFQzxvzV
1PWo3JeB9jZt9nTjxVcQu2aNrNwEenZcjG
1PWo3JeB9jdMGJNFxwckqgV7HxyrRxWL9R
1PWo3JeB9jddiHUfRfYqBAVjd6HRMEoycu
1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU
1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2
1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw
1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
Provide the HEX values
0x5b4ea19e845df8dc31 1PWo3JeB9jP8jxGWV1eAGXThNbxEhtxuq4
0x549778cd7b98124c10 1PWo3JeB9jPUEeDgSsBmZV2oxdmYtogaMX
0x649a103b78b3e74856 1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak
0x649a0ad2d9876795c4 1PWo3JeB9jS1ttWtFXgTCy2hnCYcW1dD6V
0x51da1e8db3710da999 1PWo3JeB9jSUU4ueEp5sSK6i9P26yBWfJh
0x649ade9933e47de861 1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD
0x651c1bd5cef37d5b35 1PWo3JeB9jSiimGHNbZUoc9hfVe9Ko5SGr
0x649a05d73d20978e62 1PWo3JeB9jT926gmLys26TBwr6pwStgwLb
0x6518732b2b56b3697c 1PWo3JeB9jUAfYHTXQjUYuS6timskdRieF
0x54add2baaad428adc5 1PWo3JeB9jUiESdtipzxqWJWTANVYiydnN
0x520da9a70715947fbe 1PWo3JeB9jV9ZdU1LBAwHodBvV8fRZdZ1w
0x65a6144aea3216f036 1PWo3JeB9jVxkSLg1WgymVexXayVHeBGSM
0x4620ed669f1b496ec2 1PWo3JeB9jVyFtMXcuR7ffrdPkNSLgsePc
0x7c270c663877b2616c 1PWo3JeB9jY39MsnvSJSVCdaJegFQzxvzV
0x5485e6ee348118068c 1PWo3JeB9jZt9nTjxVcQu2aNrNwEenZcjG
0x40174800c9c91ea596 1PWo3JeB9jdMGJNFxwckqgV7HxyrRxWL9R
0x542234dd5176d05a5f 1PWo3JeB9jddiHUfRfYqBAVjd6HRMEoycu
0x63f651bb9c47645cd6 1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU
0x649a3dd0486c96e70b 1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
0x649a737f258abb8058 1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2
0x649af9e3471ed5c49b 1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw
0x649aa0a809fe13a924 1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY
0x7c26f7d7a330e3cf99 1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
0x7c26f7d7a330e3cf99 1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
You got the list from Wandering Philosopher he made himself public
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I mean these prefixes.
1PWo3JeB9jNkTL28QqVi3EvU93LJuZa4JR
1PWo3JeB9jP8jxGWV1eAGXThNbxEhtxuq4
1PWo3JeB9jPUEeDgSsBmZV2oxdmYtogaMX
1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak
1PWo3JeB9jS1ttWtFXgTCy2hnCYcW1dD6V
1PWo3JeB9jSUU4ueEp5sSK6i9P26yBWfJh
1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD
1PWo3JeB9jSiimGHNbZUoc9hfVe9Ko5SGr
1PWo3JeB9jT926gmLys26TBwr6pwStgwLb
1PWo3JeB9jUAfYHTXQjUYuS6timskdRieF
1PWo3JeB9jUiESdtipzxqWJWTANVYiydnN
1PWo3JeB9jV9ZdU1LBAwHodBvV8fRZdZ1w
1PWo3JeB9jVxkSLg1WgymVexXayVHeBGSM
1PWo3JeB9jVyFtMXcuR7ffrdPkNSLgsePc
1PWo3JeB9jY39MsnvSJSVCdaJegFQzxvzV
1PWo3JeB9jZt9nTjxVcQu2aNrNwEenZcjG
1PWo3JeB9jdMGJNFxwckqgV7HxyrRxWL9R
1PWo3JeB9jddiHUfRfYqBAVjd6HRMEoycu
1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU
1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2
1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw
1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jNkTL28QqVi3EvU93LJuZa4JR
1PWo3JeB9jP8jxGWV1eAGXThNbxEhtxuq4
1PWo3JeB9jPUEeDgSsBmZV2oxdmYtogaMX
1PWo3JeB9jRLz2NjTHsZ8uTBnqcjnu66Ak
1PWo3JeB9jS1ttWtFXgTCy2hnCYcW1dD6V
1PWo3JeB9jSUU4ueEp5sSK6i9P26yBWfJh
1PWo3JeB9jSVntJs1FpYM2iTNAoADNv2YD
1PWo3JeB9jSiimGHNbZUoc9hfVe9Ko5SGr
1PWo3JeB9jT926gmLys26TBwr6pwStgwLb
1PWo3JeB9jUAfYHTXQjUYuS6timskdRieF
1PWo3JeB9jUiESdtipzxqWJWTANVYiydnN
1PWo3JeB9jV9ZdU1LBAwHodBvV8fRZdZ1w
1PWo3JeB9jVxkSLg1WgymVexXayVHeBGSM
1PWo3JeB9jVyFtMXcuR7ffrdPkNSLgsePc
1PWo3JeB9jY39MsnvSJSVCdaJegFQzxvzV
1PWo3JeB9jZt9nTjxVcQu2aNrNwEenZcjG
1PWo3JeB9jdMGJNFxwckqgV7HxyrRxWL9R
1PWo3JeB9jddiHUfRfYqBAVjd6HRMEoycu
1PWo3JeB9jdv1SaFoJK7SynTq94JFdbagU
1PWo3JeB9jdvp56gzG8navJjUMFQxxb997
1PWo3JeB9jeFuotNeYDrWkEhqyZ359abB2
1PWo3JeB9jgFbdXaZG1h8ng9hpYzg3CAPw
1PWo3JeB9jgLYkm8cEj6yywPn3kk41BFaY
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
1PWo3JeB9jgfLmhDhuZofG3Gzfzd5FzBvU
Provide the HEX values
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Why do you always have to lie and sell yourself as a smart person here
You can never prove your statements
You can never prove your statements
Look kid, I hate or ignore people who talk nonsense without knowing anything.
You don't have a grain of sand of an idea about the things I know.
If you want, I don't know @onepuzzle. I wrote him what he needed about the creator. If I don't know anything, @onepuzzle can say that.
You made mistakes before. I warned you.
TelegramName = @bytizi34
Name = By Tizi
BitcoinTalk Username= bibilgin
Many greetings to Türkiye.!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Did you know, that if the puzzle creator spent so much money so easily, how many bitcoins does he still have left? (rhetorically)
I have detected around 28500 BTC, there may be wallets that I have not detected.
Why do you always have to lie and sell yourself as a smart person here
You can never prove your statements
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Quite the opposite is true. saatoshi_rising himself explains that he did not hand-pick 256 separate keys, but used a deterministic wallet generator:
No matter how hard it is but this was a very tempting approach which i tried also a year ago https://github.com/iceland2k14/btc_words/blob/main/seed_puzzle.py. Off course as expected no success. Good for only playing and Dreaming of hitting all the Puzzles together in 1 shot.
Well, you could make it GPU compatible and break the seeds faster, then your dreams would quickly come true.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Burned that $100 in fees.
Miners: Thank you, bro.
Miners: Thank you, bro.
Code:
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Monitored addr: 1FXsMVXVV52zyLhHzZKg6wGous6KzMW6bM
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] RIPEMD-160: 9f6845cc702a6b162fce0255387c8f7c609d72e6
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: a39c45e65f35ff4398d98332fa3f4b6aaabe1316391711441b00556803b89f29 {0}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: abfbbafd607c51d723b321a632967bb12fb23642a03b52ddc76be6166e9f773b {1}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] maxOutVal: 98363 estTxSz: 339 useful UTXOs: 2
2025-06-24 13:21:56,174 [INFO ] [p71_3dm] [MP] Found unconfirmed TX
2025-06-24 13:21:56,175 [INFO ] [root] Processing TX ID: bb74f418b8b8ea18bb1c81451d7059a79e36a11289de3a765b9e71cd370fa694
2025-06-24 13:21:56,175 [INFO ] [p71_3dm] [MP] TX fee: 14366 sat; 42 sat/vB
2025-06-24 13:21:56,175 [INFO ] [root] [p71_3dm] Solving pubKey: 0216aebfc21a9b8c831a4dba02bdb08067fcd7b96a6f2f6ce2ed5300993ebc3be1
2025-06-24 13:21:59,384 [INFO ] [p71_3dm] Private key: 0x42341f438010c1b651
2025-06-24 13:21:59,385 [INFO ] [p71_3dm] Full-width private key: 000000000000000000000000000000000000000000000042341f438010c1b651
2025-06-24 13:21:59,386 [INFO ] [root] New key: 463f1adbfeb068e1981302eed3adb9ceb387dda6f90145b4cf92f856447db129
2025-06-24 13:21:59,386 [INFO ] [root] New address: 1Gw9sm693wfvMr11g6M1NuqtEnF8FFniyG
2025-06-24 13:21:59,387 [INFO ] [root] Creating TX with out value 83658
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] RIPEMD-160: 9f6845cc702a6b162fce0255387c8f7c609d72e6
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: a39c45e65f35ff4398d98332fa3f4b6aaabe1316391711441b00556803b89f29 {0}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] Mon UTXO: abfbbafd607c51d723b321a632967bb12fb23642a03b52ddc76be6166e9f773b {1}
2025-06-24 13:21:45,019 [INFO ] [p71_3dm] maxOutVal: 98363 estTxSz: 339 useful UTXOs: 2
2025-06-24 13:21:56,174 [INFO ] [p71_3dm] [MP] Found unconfirmed TX
2025-06-24 13:21:56,175 [INFO ] [root] Processing TX ID: bb74f418b8b8ea18bb1c81451d7059a79e36a11289de3a765b9e71cd370fa694
2025-06-24 13:21:56,175 [INFO ] [p71_3dm] [MP] TX fee: 14366 sat; 42 sat/vB
2025-06-24 13:21:56,175 [INFO ] [root] [p71_3dm] Solving pubKey: 0216aebfc21a9b8c831a4dba02bdb08067fcd7b96a6f2f6ce2ed5300993ebc3be1
2025-06-24 13:21:59,384 [INFO ] [p71_3dm] Private key: 0x42341f438010c1b651
2025-06-24 13:21:59,385 [INFO ] [p71_3dm] Full-width private key: 000000000000000000000000000000000000000000000042341f438010c1b651
2025-06-24 13:21:59,386 [INFO ] [root] New key: 463f1adbfeb068e1981302eed3adb9ceb387dda6f90145b4cf92f856447db129
2025-06-24 13:21:59,386 [INFO ] [root] New address: 1Gw9sm693wfvMr11g6M1NuqtEnF8FFniyG
2025-06-24 13:21:59,387 [INFO ] [root] Creating TX with out value 83658
etc... fought to the very end.
Thx for the exercise though.
Is it possible to limit maximum fee somehow? Any ideas?
Also, where to view all mempool RBF timeline? mempool.space definitely not shows all.
Also, where to view all mempool RBF timeline? mempool.space definitely not shows all.
Did you scroll the RBF timeline on mempool.space? It shows the TX has been replaced 51 times.
Two of those were mine. But looking at the timeline, it seems that the owner of the address 158tuQVCj6DTPxBawCFQcpiVVs5qkmieLY was replacing its own TX many times in a row, which is a hint of a bad coded bot.
@kTimesG
Can you please share your bot script? Thanks
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
There's no way this can be solved this way. .. go away now. 
Here is the whole code
https://github.com/AkitoHosana/mnemonic-puzzle-solver
Unfortunately this link does not exist you made a mistake
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
keep in mind, there is a difference in base58 prefixes and h160 bits. It feels like you are mixing the two up/together.
I'm not mixing anything. These are all (and only) the possible H160 values that convert back to a "1PWo3JeB9jrGw" address prefix.
Code:
Unfilled base58 digits: 21
Adjusting min H160 up from "1PWo3JeB9jrGvzzzzzzzzzzzzzzzza76BM"
min NB+H160+CS: 00f6f5431d25bbf7b129329c4be9ce9c7064f457fc76e8cd54 len: 25 minAddr: 1PWo3JeB9jrGw1111111111111117sfssh
Address right before the computed minimum: 1PWo3JeB9jrGvzzzzzzzzzzzzzzzza76BM
max NB+H160+CS: 00f6f5431d25bbf7b1314bbfcb22658f6370ac8ac91e478669 len: 25 maxAddr: 1PWo3JeB9jrGwzzzzzzzzzzzzzzzwVNymA
Address right after the computed maximum: 1PWo3JeB9jrGx11111111111111163WUG8
H160 target prefix len: 67 bits
Total possible H160: 2506270853702237716179595982 = 91.01760089767902 bits
Expected average in subset: 2.02
99% confidence interval: [0, 6] successes
Adjusting min H160 up from "1PWo3JeB9jrGvzzzzzzzzzzzzzzzza76BM"
min NB+H160+CS: 00f6f5431d25bbf7b129329c4be9ce9c7064f457fc76e8cd54 len: 25 minAddr: 1PWo3JeB9jrGw1111111111111117sfssh
Address right before the computed minimum: 1PWo3JeB9jrGvzzzzzzzzzzzzzzzza76BM
max NB+H160+CS: 00f6f5431d25bbf7b1314bbfcb22658f6370ac8ac91e478669 len: 25 maxAddr: 1PWo3JeB9jrGwzzzzzzzzzzzzzzzwVNymA
Address right after the computed maximum: 1PWo3JeB9jrGx11111111111111163WUG8
H160 target prefix len: 67 bits
Total possible H160: 2506270853702237716179595982 = 91.01760089767902 bits
Expected average in subset: 2.02
99% confidence interval: [0, 6] successes
And matching the first 67 bits in the RIPEMD hash yields
Code:
Total possible H160: 9903520314283042199192993792 = 93.0 bits
Expected average in subset: 8.00
99% confidence interval: [2, 16] successes
Expected average in subset: 8.00
99% confidence interval: [2, 16] successes
Hence, matching H160 prefixes will provide many results which don't result in the 1+12 b58 prefix. Simply because most of those fall below and above the min/max BOUNDED H160s that convert to the desired base58 1+12 prefix.
I think it’s your original wording.
Also, without a script and just reading your results, is it saying for an h160 of a minimum of 67 bits, there will be only 2^91?
In 2^70 hash trials, there is a 100% confidence of between 0 and 2^71 h160s having that base58 property?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
There's at least one other address starting with "1PWo3JeB9jrGw" in the 71 range.
No matter how you search, people should reflect on this fact: there's a 50% chance you'd first find this other address, before actually finding the correct one, and way way ... way later after dealing with half of the other 395.000 unique addresses (plus or minus 2000) that match the first 1+9 base58 chars.
It's even worse if matching just the H160 bits for efficiency. The number of comparable H160s is 3 to 4 times higher than b58 matches, because a lot of those won't match the desired b58 pattern, even though they have lots of matching bits.
No matter how you search, people should reflect on this fact: there's a 50% chance you'd first find this other address, before actually finding the correct one, and way way ... way later after dealing with half of the other 395.000 unique addresses (plus or minus 2000) that match the first 1+9 base58 chars.
It's even worse if matching just the H160 bits for efficiency. The number of comparable H160s is 3 to 4 times higher than b58 matches, because a lot of those won't match the desired b58 pattern, even though they have lots of matching bits.
Code:
import base58
min = base58.b58decode('1PWo3JeB9jrGw111111111111111111111').hex()
max = base58.b58decode('1PWo3JeB9jrGwzzzzzzzzzzzzzzzzzzzzz').hex()
# Get total possibilities, and remove checksum bytes
n = (int(max, 16) - int(min, 16) + 1) >> 32
# Get AVERAGE count over ANY 40 bits set
n = n / (2**(160 - 70))
print(n)
= 2.0245494726457194min = base58.b58decode('1PWo3JeB9jrGw111111111111111111111').hex()
max = base58.b58decode('1PWo3JeB9jrGwzzzzzzzzzzzzzzzzzzzzz').hex()
# Get total possibilities, and remove checksum bytes
n = (int(max, 16) - int(min, 16) + 1) >> 32
# Get AVERAGE count over ANY 40 bits set
n = n / (2**(160 - 70))
print(n)
There are exactly only 2 1PWo3JeB9jrGw
LMAO you do realize that I'm the one who posted that code snippet, right?
Anyway, it's slightly wrong (min and max H160 need to actually be valid). The actual code that handles these issues is much longer than that snippet.
After computing a Poisson confidence interval, there are, with a 99% chance, anywhere between 2 and 6 H160 values in 2**70 hash trials, which end up with an address having the mentioned base58 prefix.
A confidence of 100% is that there are anywhere between 0 and 2**71 H160 having that property.
keep in mind, there is a difference in base58 prefixes and h160 bits. It feels like you are mixing the two up/together.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
There's at least one other address starting with "1PWo3JeB9jrGw" in the 71 range.
No matter how you search, people should reflect on this fact: there's a 50% chance you'd first find this other address, before actually finding the correct one, and way way ... way later after dealing with half of the other 395.000 unique addresses (plus or minus 2000) that match the first 1+9 base58 chars.
It's even worse if matching just the H160 bits for efficiency. The number of comparable H160s is 3 to 4 times higher than b58 matches, because a lot of those won't match the desired b58 pattern, even though they have lots of matching bits.
No matter how you search, people should reflect on this fact: there's a 50% chance you'd first find this other address, before actually finding the correct one, and way way ... way later after dealing with half of the other 395.000 unique addresses (plus or minus 2000) that match the first 1+9 base58 chars.
It's even worse if matching just the H160 bits for efficiency. The number of comparable H160s is 3 to 4 times higher than b58 matches, because a lot of those won't match the desired b58 pattern, even though they have lots of matching bits.
Code:
import base58
min = base58.b58decode('1PWo3JeB9jrGw111111111111111111111').hex()
max = base58.b58decode('1PWo3JeB9jrGwzzzzzzzzzzzzzzzzzzzzz').hex()
# Get total possibilities, and remove checksum bytes
n = (int(max, 16) - int(min, 16) + 1) >> 32
# Get AVERAGE count over ANY 40 bits set
n = n / (2**(160 - 70))
print(n)
min = base58.b58decode('1PWo3JeB9jrGw111111111111111111111').hex()
max = base58.b58decode('1PWo3JeB9jrGwzzzzzzzzzzzzzzzzzzzzz').hex()
# Get total possibilities, and remove checksum bytes
n = (int(max, 16) - int(min, 16) + 1) >> 32
# Get AVERAGE count over ANY 40 bits set
n = n / (2**(160 - 70))
print(n)
There are exactly only 2 1PWo3JeB9jrGw
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Great speed but dont have range Start and End.
I have modified FixedPaul VanitySearch, which allow custom start:end range and add new totally random mode without any sequential approach, but since i also create my own version of range slicing code, i use sequential in this process :
Code:
PS C:\Users\Asus\Desktop\Vanbitxx> ./x64/Release/VanitySearch.exe -gpuId 0 -f newrx.txt -seq 1PWo3JeB
VanitySearch-Bitcrack v2.2 by FixedPaul
[*] Processing range file: newrx.txt
[*] Found range file at: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
[*] Loading ranges from file: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
[*] File size: 16669574 bytes
[*] Parsed 438673 non-empty lines
[*] Found 438673 ranges in file
[*] Successfully loaded 438673 ranges into cache
Range file: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
Range: 40BD1588A9B58ADC43 -> 40BD1588AC0996C042 (Keys: 10000000000, Remaining: 438672)
Initial range from file:
Start: 40BD1588A9B58ADC43
End: 40BD1588AC0996C042
Next: 40BD1588A9B58ADC43
Sequential Mode Enabled !
Search: 1PWo3JeB [Compressed]
Current task START time: Sun Jun 15 20:58:00 2025
GPU: GPU #0 NVIDIA GeForce RTX 2050 (16x128 cores) Grid(2048x256)
Starting keys set in 0.21 seconds
Range: 465C3F524916AE3D6E -> 465C3F524B6ABA216D (Keys: 10000000000, Remaining: 438561) - Speed: 564.2 [MK/s] - Found: 0
Public Addr: 1PWo3JeBFpmV6hk6gyvUHRZ5yMtLSySU8p
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qzbxieRo41BuDkkstQDr
Priv (HEX): 0x0000000000000000000000000000000000000000000000465C3F524B26D02B36
Range: 4AD8C8A8E1D4D5FB6D -> 4AD8C8A8E428E1DF6C (Keys: 10000000000, Remaining: 438449) - Speed: 564.0 [MK/s] - Found: 1
Public Addr: 1PWo3JeBHpRhh6uasKKNBSVFcREHB5X9P8
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3r2FdEJec4RhDmzHm8GkV
Priv (HEX): 0x00000000000000000000000000000000000000000000004AD8C8A8E2772B6382
Range: 45B791FF293F7EC654 -> 45B791FF2B938AAA53 (Keys: 10000000000, Remaining: 438272) - Speed: 564.7 [MK/s] - Found: 2
VanitySearch-Bitcrack v2.2 by FixedPaul
[*] Processing range file: newrx.txt
[*] Found range file at: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
[*] Loading ranges from file: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
[*] File size: 16669574 bytes
[*] Parsed 438673 non-empty lines
[*] Found 438673 ranges in file
[*] Successfully loaded 438673 ranges into cache
Range file: C:\Users\Asus\Desktop\Vanbitxx\newrx.txt
Range: 40BD1588A9B58ADC43 -> 40BD1588AC0996C042 (Keys: 10000000000, Remaining: 438672)
Initial range from file:
Start: 40BD1588A9B58ADC43
End: 40BD1588AC0996C042
Next: 40BD1588A9B58ADC43
Sequential Mode Enabled !
Search: 1PWo3JeB [Compressed]
Current task START time: Sun Jun 15 20:58:00 2025
GPU: GPU #0 NVIDIA GeForce RTX 2050 (16x128 cores) Grid(2048x256)
Starting keys set in 0.21 seconds
Range: 465C3F524916AE3D6E -> 465C3F524B6ABA216D (Keys: 10000000000, Remaining: 438561) - Speed: 564.2 [MK/s] - Found: 0
Public Addr: 1PWo3JeBFpmV6hk6gyvUHRZ5yMtLSySU8p
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qzbxieRo41BuDkkstQDr
Priv (HEX): 0x0000000000000000000000000000000000000000000000465C3F524B26D02B36
Range: 4AD8C8A8E1D4D5FB6D -> 4AD8C8A8E428E1DF6C (Keys: 10000000000, Remaining: 438449) - Speed: 564.0 [MK/s] - Found: 1
Public Addr: 1PWo3JeBHpRhh6uasKKNBSVFcREHB5X9P8
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3r2FdEJec4RhDmzHm8GkV
Priv (HEX): 0x00000000000000000000000000000000000000000000004AD8C8A8E2772B6382
Range: 45B791FF293F7EC654 -> 45B791FF2B938AAA53 (Keys: 10000000000, Remaining: 438272) - Speed: 564.7 [MK/s] - Found: 2
Can you please upload your version to github?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
So I created this thing for the 1000 Bitcoin puzzle:
https://github.com/mrwhalebones/puzzlesolver
https://privatekeys.pw/puzzles/bitcoin-puzzle-tx
I found this forum through there and am just sharing the work I did. One script, has pause/save/load states for workers and I'm working on including GPU workers.
It's a standalone non-internet dependent puzzle solver with no undermining. Best of luck!
Edit: just a heads up on how the workers act on threads. Each "worker" in Linear mode, creates two threads moving forward and backward in the nonce range. I included a hybrid and random mode as well. You can change the nonce range and search for more than one winning address at a time. I missed the deadline for making money through the Google hackathon, so just enjoy. I'll be adding support for GPU threads as well. I bricked a couple laptops, so I'm starting with a raspberry pi 400 setup as the initial GPU release.
https://github.com/mrwhalebones/puzzlesolver
https://privatekeys.pw/puzzles/bitcoin-puzzle-tx
I found this forum through there and am just sharing the work I did. One script, has pause/save/load states for workers and I'm working on including GPU workers.
It's a standalone non-internet dependent puzzle solver with no undermining. Best of luck!
Edit: just a heads up on how the workers act on threads. Each "worker" in Linear mode, creates two threads moving forward and backward in the nonce range. I included a hybrid and random mode as well. You can change the nonce range and search for more than one winning address at a time. I missed the deadline for making money through the Google hackathon, so just enjoy. I'll be adding support for GPU threads as well. I bricked a couple laptops, so I'm starting with a raspberry pi 400 setup as the initial GPU release.
and again a chatgpt AI script