Search content
Sort by
Showing 20 of 22 results by bcchanger
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I noticed that some people in the group are searching for prefixes of the Bitcoin address:
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
The purpose is jump between prefixs for reduce scanning, but the problem is the distance between prefixs target is not same because the distribution is not predictable.1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
this the example of scanning with sequential, you can see the distance is can't predicted. Even when we use average distance but that not guarantee the calculation not skipped the puzzle target.
Public Addr: 1PWo3JeBbURW5W5W6exwvLHfvRMRQ28SP7
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DAnemGxU2wWDbE7V
Priv (HEX): 0x 794B37D7B6E94E4F5F
Public Addr: 1PWo3JeBWCXEVkzycsVwm5bs3d3aj2J9hB
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBLVYzWiZu3f2zSc
Priv (HEX): 0x 794B37D9EDA9E85057
Public Addr: 1PWo3JeBeJfj6GY3Uk2zX6ZCMxJtPNsGTF
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBTAE2PrM7wGtNtM
Priv (HEX): 0x 794B37DA6453F75BF3
Public Addr: 1PWo3JeBergQXkCKD1gTN29HZXRTgEJw8h
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBaxzNYdiPxBUSxr
Priv (HEX): 0x 794B37DAEF465C322C
I believe that if there's any way to predict the next range or even just determine the maximum possible prefixes, it would be a game changer. It could help avoid wasting time and resources.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I noticed that some people in the group are searching for prefixes
You are not missing anything. They just try to be creative, that's all.As you mentioned, it does not make sense. But if they are having fun with it, let it be.
I noticed that some people in the group are searching for prefixes of the Bitcoin address:
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
The purpose is jump between prefixs for reduce scanning, but the problem is the distance between prefixs target is not same because the distribution is not predictable.1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
this the example of scanning with sequential, you can see the distance is can't predicted. Even when we use average distance but that not guarantee the calculation not skipped the puzzle target.
Public Addr: 1PWo3JeBbURW5W5W6exwvLHfvRMRQ28SP7
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DAnemGxU2wWDbE7V
Priv (HEX): 0x 794B37D7B6E94E4F5F
Public Addr: 1PWo3JeBWCXEVkzycsVwm5bs3d3aj2J9hB
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBLVYzWiZu3f2zSc
Priv (HEX): 0x 794B37D9EDA9E85057
Public Addr: 1PWo3JeBeJfj6GY3Uk2zX6ZCMxJtPNsGTF
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBTAE2PrM7wGtNtM
Priv (HEX): 0x 794B37DA6453F75BF3
Public Addr: 1PWo3JeBergQXkCKD1gTN29HZXRTgEJw8h
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3rKL1DBaxzNYdiPxBUSxr
Priv (HEX): 0x 794B37DAEF465C322C
Thank you for your responses
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I noticed that some people in the group are searching for prefixes of the Bitcoin address:
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
For example: 1PWo3JeB, and so on.
Can anyone with experience explain the reasoning behind this?
It doesn’t make sense to me, since the private key is what gets incremented, and each key generates a completely different Bitcoin address.
What am I missing here?!!!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Something I had forgotten to mention: while the prefix method does not represent a global improvement over the sequential method, this only applies in cases where 100% of the ranges are being scanned. However, if one is testing luck rather than exhaustive searching, the prefix method is always the better choice. If we exclude the option of scanning omitted ranges in extreme cases, the prefix method will achieve the objective faster, with fewer checks, and a 90% success rate.
The times when sequential search statistically matches the prefix method occur in its worst-case scenarios, which only represent 10% of instances. Therefore, since most users are not attempting to scan the full range 71, the best option remains the prefix method, as it provides the greatest statistical advantages with just a 10% risk.
In the unlikely event that one reaches that point in the process, those omitted ranges could always be saved for future reference in a text file.
do you have a script of your method ?The times when sequential search statistically matches the prefix method occur in its worst-case scenarios, which only represent 10% of instances. Therefore, since most users are not attempting to scan the full range 71, the best option remains the prefix method, as it provides the greatest statistical advantages with just a 10% risk.
In the unlikely event that one reaches that point in the process, those omitted ranges could always be saved for future reference in a text file.
What script do you need?! Generating prefixes is like handling ≈60 million prefixes and brute-forcing them one by one until you get it. The game isn’t about scripts... it’s about hardware. You need a ton of GPUs. You have to find the key inside this number:
1,180,591,620,717,411,303,424
Read the number twice.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Let's make this thread useful and provide a range for everyone to scan.
I've created a private Telegram group, but it's only for those who are serious about working on this puzzle.
Let's avoid duplicating efforts. At 100 trillion keys per second, scanning will take about 60 days for ranges like 4X, 5X, 6X, or 7X.
What do you think? Can we do this together? If you're lucky, you're lucky. I just don't trust the solo pools out there.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
There is no best method—each one is good if you have enough hardware resources. If you don’t, none of them will work. 
So, the dude with 3000 GPUs always wins...
Focus on the game, not people . More resources more chances like mining..
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Consult the crystal ball. 
I have one, but I don’t want to look at it. So, random mode is the best. The percentages are the same as the prefixes. There’s no connection anywhere here
A waste of time. Trust me, I’ve done tons of tests and confirmed that random can be fast (especially on low 44-bit ranges), but it can scan 4 times the entire range without a single result. That means duplication, and avoiding it completely is nearly impossible. Totally a waste of time.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
P.S. puzzle 69 is an anomaly certainly with 0.7205156139362787731%
Holy s... To how many decimal places do you calculate the percentages from the beginning of the puzzle range?
100 decimal places
Bro, this doesn't make sense if you think there's a hidden message. Compare it with the previously solved one.
Puzzle | Private Key (Decimal) | Percentage in Range
------ | --------------------- | -------------------
20 | 863317 | 64.6647733016458542745%
21 | 1811764 | 72.7833488305557542379%
22 | 3007503 | 43.4089390797324560797%
23 | 5598802 | 33.4858497347473465794%
24 | 14428676 | 72.0032300952947253340%
25 | 33185509 | 97.8010533929499025911%
26 | 54538862 | 62.5384766619943577646%
27 | 111949941 | 66.8184126439454055420%
28 | 227634408 | 69.6008508622709725966%
29 | 400708894 | 49.2756957161266197120%
30 | 1033162084 | 92.4414345853802460905%
31 | 2102388551 | 95.8001919051634072374%
32 | 3093472814 | 44.0510533023863347724%
33 | 7137437912 | 66.1814263244581935751%
34 | 14133072157 | 64.5306143635570321190%
35 | 20112871792 | 17.0723221274716967093%
36 | 42387769980 | 23.3646470943746578150%
37 | 100251560595 | 45.8852211296599885264%
38 | 146971536592 | 6.9358670735305049098%
39 | 323724968937 | 17.7704576319875576069%
40 | 1003651412950 | 82.5631285011378406643%
41 | 1458252205147 | 32.6272654430182476658%
42 | 2895374552463 | 31.6663907556774876824%
43 | 7409811047825 | 68.4795972283992522528%
44 | 15404761757071 | 75.1318650016372807687%
45 | 19996463086597 | 13.6667326966126931173%
46 | 51408670348612 | 46.1122290851689658731%
47 | 119666659114170 | 70.0565506925083533439%
48 | 191206974700443 | 35.8607269000652867471%
49 | 409118905032525 | 45.3482330164936277165%
50 | 611140496167764 | 8.5603600202070292375%
51 | 2058769515153876 | 82.8554654496163348436%
52 | 4216495639600700 | 87.2500216926509640780%
53 | 6763683971478124 | 50.1839535284626881282%
54 | 9974455244496707 | 10.7386987053338945607%
55 | 30045390491869460 | 66.7854215396361620574%
56 | 44218742292676575 | 22.7316645332392908910%
57 | 138245758910846492 | 91.8545307495002251710%
58 | 199976667976342049 | 38.7616882344719702794%
59 | 525070384258266191 | 82.1703844225954604322%
60 | 1135041350219496382 | 96.8982876430173221559%
61 | 1425787542618654982 | 23.6673560967931578683%
62 | 3908372542507822062 | 69.4986400587870082602%
63 | 8993229949524469768 | 95.0095889787226701437%
64 | 17799667357578236628 | 92.9843801860564223898%
65 | 30568377312064202855 | 65.7115054554830663249%
66 | 46346217550346335726 | 25.6216743864282766670%
67 | 132656943602386256302 | 79.7836830612427722341%
68 | 219898266213316039825 | 49.0088612214206556115%
69 | 297274491920375905804 | 0.7205156139362787731%
70 | 970436974005023690481 | 64.3984180432040121775%
75 | 22538323240989823823367 | 19.3168897561606557021%
80 | 1105520030589234487939456 | 82.8929472184889752772%
I compared them all
I appreciate your efforts, but bro, nothing is clear here :
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
P.S. puzzle 69 is an anomaly certainly with 0.7205156139362787731%
Holy s... To how many decimal places do you calculate the percentages from the beginning of the puzzle range?
100 decimal places
Bro, this doesn't make sense if you think there's a hidden message. Compare it with the previously solved one.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
think like the creator: is the key at the beginning, middle, or end? 
.
.You don’t even need to think about it—this is pure statistics. Put it on paper neatly and see.
What do you mean? Should we list all the existing solutions and see where the most keys fit?
Isn't that logical?
P.S. puzzle 69 is an anomaly certainly with 0.7205156139362787731%
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I beelieve puzzle 71 will be the final tough challenge to crack, boasting an impressive total key count of 1,180,591,620,717,411,303,424
Solo pooling seems the way to go. I'm considering forming a private group, as I’m wary of existing solo pools,if you catch my drift. The group would have a system where members share their scanned ranges, but stats would only be visible to those who contribute at least 20 range scans.
How do we verify contributions? Simple!members provide keys for specific addresses within their range.
Does this setup sound solid? I think it’s a fair, efficient way to tackle the puzzle, ensuring the lucky winner earns it through a level playing field while avoiding duplicate efforts and wasted resources.
After analyzing the puzzle, it’s clear the creator initially used Mersenne’s law and XOR for earlier puzzles but switched tactics later. I’ve tried every approach to replicate earlier results and came to one conclusion: the creator likely selects addresses from specific ranges, though it’s hard to accept. I’m unsure if this is the work of an individual or a group.
It’s evident they anticipated attempts to crack the formula, so they leaned on randomness to keep it unpredictable. So, @Bam, don’t waste your time with analysis, the only way forward is to think like the creator: is the key at the beginning, middle, or end?.
Solo pooling seems the way to go. I'm considering forming a private group, as I’m wary of existing solo pools,if you catch my drift. The group would have a system where members share their scanned ranges, but stats would only be visible to those who contribute at least 20 range scans.
How do we verify contributions? Simple!members provide keys for specific addresses within their range.
Does this setup sound solid? I think it’s a fair, efficient way to tackle the puzzle, ensuring the lucky winner earns it through a level playing field while avoiding duplicate efforts and wasted resources.
After analyzing the puzzle, it’s clear the creator initially used Mersenne’s law and XOR for earlier puzzles but switched tactics later. I’ve tried every approach to replicate earlier results and came to one conclusion: the creator likely selects addresses from specific ranges, though it’s hard to accept. I’m unsure if this is the work of an individual or a group.
It’s evident they anticipated attempts to crack the formula, so they leaned on randomness to keep it unpredictable. So, @Bam, don’t waste your time with analysis, the only way forward is to think like the creator: is the key at the beginning, middle, or end?
.Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
The next thing I’m going to update is SECP256K1 itself—I’ve already removed some unnecessary files from Git
How fast can this go?
For example, the Ryzen 9 7940HS achieves ~10 MK/s when using 1 thread and ~67 MK/s with 16 threads. Performance also depends on how it is compiled—using GCC, Clang, etc...
Any chance you could compile a Windows compatible version?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hello everyone, a question from a newbie
How to know that the github scripts around here thats belongs to smart dudes like albert or nomachine or wondering P ....don't have some hidden commands that send the keyfound.txt file back to the script creator when the script find some key
Excuse my nativity
How to know that the github scripts around here thats belongs to smart dudes like albert or nomachine or wondering P ....don't have some hidden commands that send the keyfound.txt file back to the script creator when the script find some key
Excuse my nativity
Test it on easy puzzles and then use firewall
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
We got robbed of Puzzle 69.
Hello, we are coming out to claim we are the group that solved puzzle 69.
We are a group consisting of 12 software developers in Asia with interest in cryptography. We have been scanning puzzle 66, 67, 68 and 69 since last year.
We have rented several GPUs online to use for the puzzles. Unfortunately, puzzle 66 was solved by
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd (not us)
but got stolen using RBF. Puzzles 67 and 68 were solved by 1 person and then finally we were able to solve puzzle 69.
We are using our custom software written using CUDA C++. Each member has several GPUs which will be given a range to scan. It was really a eureka moment when we were notified that a match was found by one of our members.
We are aware of RBF attack so we used a wallet software (we prefer not to say which one) which does not enable RBF by default, to transfer the coins. But when we checked the transaction, before it was confirmed, another transaction was created.
This is really heartbreaking for me and my group because we spent months scanning the range only for it to be stolen by others. We are contributing part of our savings to pay our GPU bills monthly. We might resort to contacting the wallet software provider but we know that our 6.9 BTC is long gone forever.
Now, our problem is how to pay our remaining GPU bill which amounts to $158,954.07. This is so frustrating! Why can't people play fair and square???
We are accepting donations to help us pay our remaining GPU bill in these addresses:
1BMWUDeiq15EDZETNG49YfdQvLoEzGBjxm
bc1q2pqem06ad053rnt656dta4nej6uqe9p786kjls
Hello, we are coming out to claim we are the group that solved puzzle 69.
We are a group consisting of 12 software developers in Asia with interest in cryptography. We have been scanning puzzle 66, 67, 68 and 69 since last year.
We have rented several GPUs online to use for the puzzles. Unfortunately, puzzle 66 was solved by
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd (not us)
but got stolen using RBF. Puzzles 67 and 68 were solved by 1 person and then finally we were able to solve puzzle 69.
Code:
0x101d83275fb2bc762d
0x101d83275fb2bc7ba7
0x101d83275fb2bc7f4e
0x101d83275fb2bc7604
0x101d83275fb2bc7e0c
Match found!
Private Key: 0x101d83275fb2bc7e0c
Compressed Public Key: 024babadccc6cfd5f0e5e7fd2a50aa7d677ce0aa16fdce26a0d0882eed03e7ba53
We are using our custom software written using CUDA C++. Each member has several GPUs which will be given a range to scan. It was really a eureka moment when we were notified that a match was found by one of our members.
We are aware of RBF attack so we used a wallet software (we prefer not to say which one) which does not enable RBF by default, to transfer the coins. But when we checked the transaction, before it was confirmed, another transaction was created.
This is really heartbreaking for me and my group because we spent months scanning the range only for it to be stolen by others. We are contributing part of our savings to pay our GPU bills monthly. We might resort to contacting the wallet software provider but we know that our 6.9 BTC is long gone forever.
Now, our problem is how to pay our remaining GPU bill which amounts to $158,954.07. This is so frustrating! Why can't people play fair and square???
We are accepting donations to help us pay our remaining GPU bill in these addresses:
1BMWUDeiq15EDZETNG49YfdQvLoEzGBjxm
bc1q2pqem06ad053rnt656dta4nej6uqe9p786kjls
Sign the receiving wallet ( the first receiving wallet ) if you claim that you are the winner
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Guys, is there any software better than BitCrack that works with CUDA?
BitCrack is extremely slow.
Make your own.BitCrack is extremely slow.
Thank you.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Are you brute-forcing using a paper? How many keys per... ehm... day?
I can brute the last 12 digit for 3 hours in 3080
I have 6x 3080. So every 3 hours i can verify 6 guesses that i wrote on papers😅
Puzzle 69 start with 1 so im guessing 6 hex after 1
Every day i verify 18 guesses , i change range manually 🙃😅
This doesn't make sense for me why you brute force the first 6 digits ?!!!
Huh its like lottery ticket
You guess 1+6 hex ( ticket)
Last 12 digit brute by my rig
I dont brute the first 6 digit , in that paper is my 6 hex guesses. Add 1 in front so 7 digit 😅.
For puzzle 71 this example guesess list ✌️
0x45219D3
0x45E3C04
0x466A1EF
.....
Wish you a good luck with 71..
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Are you brute-forcing using a paper? How many keys per... ehm... day?
I can brute the last 12 digit for 3 hours in 3080
I have 6x 3080. So every 3 hours i can verify 6 guesses that i wrote on papers😅
Puzzle 69 start with 1 so im guessing 6 hex after 1
Every day i verify 18 guesses , i change range manually 🙃😅
This doesn't make sense for me why you brute force the first 6 digits ?!!!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Nice to see the bots battling it out for 69.
Did anyone even get close? I scanned 101C76FE and 101E4D0B...
0000000000000000000000000000000000000000000000101D7D849C924530B1 02FFE0AE1C43AC1535AF17A4F7553BBD7BBD4502D4984E766BE9BB05EC44CBE9CF 61eb8a5005b20ad4b35cadfbbcd3d36ca2b40bfaDid anyone even get close? I scanned 101C76FE and 101E4D0B...
Hi,
What type of search you were conducting? random ?!!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
On a serious note...congrats to all the sub 1%'ers. You all kicked some azz, especially one of you, this time around! Woop woop! You sub one percenters have made me smile and even, giggle, a little bit
Now, which one of you, or how many of you, crazy fools are going to be in the next, sub one percenters club??
Now, which one of you, or how many of you, crazy fools are going to be in the next, sub one percenters club??
I've tested your software and I must say, excellent work!
I was curious if there's a feature to prevent the reuse of duplicate keys.
In my tests using a small range, keys were often found quickly, but at times it took longer than the total key space, suggesting that some keys might be repeating.