Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Jorge54PT]

Everyone comments on everyone's methods, but what I know is that 67 is still intact

[mcdouglasx]

I would not have thought the year 2025 would be the war of the prefixes.
You guys really need to understand this. You literally change 1 character and the prefix has no use. 1BY8GQbnuXX can be at the start of the range, while 1BY8GQbnuXXY can be at the very end of the range. There's no link. You can't reverse it. I'm having a hard time to even express this because it's such a stupid idea.
I won't be contributing to this thread until Bitcoin leaves the 100k quack range and reaches 59k what I call the "sanity range" where more normal theories are being discussed.

What I understand here is the following: 1. They gather a series of prefixes and catalog them to average the distances between each prefix (pattern). 2. They search by probability in the approximate ranges to the next possible pattern.
Since the puzzle is in a small range compared to 256 bits, it is not unreasonable to use predictions, although it is not precise, it has its logic.

[kTimesG]

I would not have thought the year 2025 would be the war of the prefixes.
You guys really need to understand this. You literally change 1 character and the prefix has no use. 1BY8GQbnuXX can be at the start of the range, while 1BY8GQbnuXXY can be at the very end of the range. There's no link. You can't reverse it. I'm having a hard time to even express this because it's such a stupid idea.
I won't be contributing to this thread until Bitcoin leaves the 100k quack range and reaches 59k what I call the "sanity range" where more normal theories are being discussed.

What I understand here is the following: 1. They gather a series of prefixes and catalog them to average the distances between each prefix (pattern). 2. They search by probability in the approximate ranges to the next possible pattern.
Since the puzzle is in a small range compared to 256 bits, it is not unreasonable to use predictions, although it is not precise, it has its logic.

Yeah, this is why the thread has become the daily journal of "prefix of the day". The guy who started this daily blog was first under the impression that there are only 4 prefixes of some kind, and he then was proven wrong (correct value was somewhere around 1000 prefixes). And now we're all anxiously watching his catalog progress, one prefix at a time, for years to come.

I would laugh so hard to know that the real answer to 67 is just a few keys away from an already found prefix, in a range that was definitely dismissed because someone thinks he can outsmart a random noise distribution.

[bibilgin]

Yeah, this is why the thread has become the daily journal of "prefix of the day". The guy who started this daily blog was first under the impression that there are only 4 prefixes of some kind, and he then was proven wrong (correct value was somewhere around 1000 prefixes). And now we're all anxiously watching his catalog progress, one prefix at a time, for years to come.

I would laugh so hard to know that the real answer to 67 is just a few keys away from an already found prefix, in a range that was definitely dismissed because someone thinks he can outsmart a random noise distribution.

Yes, KTimesG I think you didn't understand. Your other friends may be confused.

The 4 intervals with the prefix 1BY8GQbnueY are important to me.
(Between 6A... and 7D...)

I determine the AVERAGE interval of the 1BY8GQbnue prefixes with my PROBABILITY and MATHEMATICAL calculations.

Are you saying that the 1BY8GQbnueY prefix is ​​over 1000?
Be patient a little longer, as I said when it is finished I will share the Hex code, SHA256 and SHA512.

[hotmoney]

THERE ARE MULTIPLE COMBINATIONS THESE ADDRESSES EXIST WE JUST DON'T HAVE THEIR PRIVATE KEYS YET BUT THERE ARE ENDLESS COMBINATIONS... I FOUND THESE THIS MONTH

Someone send me some money to help with energy I will continue publishing but addresses thank you      my address donate       1ericoPSxFdQWGAE6iDcdc2jc3HBRYpEC

PubAddress: 1BY8GQbnu1DPVT6c66yLZRvMRcugu41i4v
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qb1BpUpTPTMZvzTW6w38
Priv (HEX): 62AD2731CC3285DB2 (67 bit)

PubAddress: 1BY8GQbnu6v7Ux8krR8URwodBWm1SawLnr
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qb1AmPhsuXNqMapR1bpb
Priv (HEX): 62A9AA2EB577A9FF8 (67 bit)

PubAddress: 1BY8GQbnu8jSXMYE4o2ZfzFSv3D7fX7BGC
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qatTWrxLTZsfBbss3EQ2
Priv (HEX): 5DA0791C09C3BBAC4 (67 bit)

PubAddress: 1BY8GQbnu9Pr3u4dLhGZo2vCrQswS8fZTz
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qabYU6bF3ZDDBjJh2kNQ
Priv (HEX): 50EF4226B89DF60AA (67 bit)

PubAddress: 1BY8GQbnub1JKjz49sq9NhHUXVjujDNXFp
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qawb2V4cHnNNhpXYUVP1
Priv (HEX): 5FF9A24218EA189F4 (67 bit)

PubAddress: 1BY8GQbnucXmpBfXmSaqrYfmyE8v2dh2uA
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaccTEqzmmLtkcQBnFEz
Priv (HEX): 51BC8D6E6A141E38D (67 bit)

PubAddress: 1BY8GQbnuGbW7BppF1HchbeneV2gG1Gh7B
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qakTBCawW4YR6tnWw8UX
Priv (HEX): 579E96EC070A54893 (67 bit)

PubAddress: 1BY8GQbnugVjgeL43mD1SqXpAFU8mqSE5R
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaTR8PhQPcePBUvstdff
Priv (HEX): 4AD6304048C00378A (67 bit)

PubAddress: 1BY8GQbnujgvke9PYWMpNbwTs9Jdvv7KTe
Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qaZ5BRtJYKA7J2VEVaaa
Priv (HEX): 4F14B15F5AE4EF20A (67 bit)PubAddress: 1BY8GQbnuy3wbCC9Gorrhi6PijfdRjtQXT

Priv (WIF): p2pkh: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qai7oV99TmLWDasNfzvh
Priv (HEX): 55DE3B4E1A5DEFA73 (67 bit)



1BY8GQbnueY1 xxxxxx
1BY8GQbnueY2 xxxxxx
1BY8GQbnueY3 xxxxxx
1BY8GQbnueY4 xxxxxx
1BY8GQbnueY5 xxxxxx
1BY8GQbnueY6 xxxxxx
1BY8GQbnueY7 xxxxxx
1BY8GQbnueY8 xxxxxx
1BY8GQbnueY9 xxxxxx
1BY8GQbnueY0 xxxxxx

1BY8GQbnueY1A xxxxx
1BY8GQbnueY1a xxxxx

1BY8GQbnueY1B xxxxx
1BY8GQbnueY1b xxxxx

1BY8GQbnueYC xxxx
1BY8GQbnueY1c xxxx  


1BY8GQbnueA
1BY8GQbnuea

1BY8GQbnueB
1BY8GQbnueb

1BY8GQbnueC
1BY8GQbnuec

1BY8GQbnueD
1BY8GQbnued

1BY8GQbnueE
1BY8GQbnuee

1BY8GQbnueF
1BY8GQbnuef

1BY8GQbnueG
1BY8GQbnueg

1BY8GQbnueH
1BY8GQbnueh

1BY8GQbnueI
1BY8GQbnuei

1BY8GQbnueJ
1BY8GQbnuej

1BY8GQbnueK
1BY8GQbnuek

1BY8GQbnueL
1BY8GQbnuel

1BY8GQbnueM
1BY8GQbnuem

1BY8GQbnueN
1BY8GQbnuen

1BY8GQbnueO
1BY8GQbnueo

1BY8GQbnueP
1BY8GQbnuep

1BY8GQbnueQ
1BY8GQbnueq

1BY8GQbnueR
1BY8GQbnuer

1BY8GQbnueS
1BY8GQbnues

1BY8GQbnueT
1BY8GQbnuet

1BY8GQbnueU
1BY8GQbnueu

1BY8GQbnueV
1BY8GQbnuev

1BY8GQbnueW
1BY8GQbnuew

1BY8GQbnueX
1BY8GQbnuex

1BY8GQbnueY
1BY8GQbnuey

1BY8GQbnueZ
1BY8GQbnuez


1BY8GQbnueA
1BY8GQbnuea

1BY8GQbnueB
1BY8GQbnueb

1BY8GQbnueC
1BY8GQbnuec

1BY8GQbnueD
1BY8GQbnued

1BY8GQbnueE
1BY8GQbnuee

1BY8GQbnueF
1BY8GQbnuef

1BY8GQbnueG
1BY8GQbnueg

1BY8GQbnueH
1BY8GQbnueh

1BY8GQbnueI
1BY8GQbnuei

1BY8GQbnueJ
1BY8GQbnuej

1BY8GQbnueK
1BY8GQbnuek

1BY8GQbnueL
1BY8GQbnuel

1BY8GQbnueM
1BY8GQbnuem

1BY8GQbnueN
1BY8GQbnuen

1BY8GQbnueO
1BY8GQbnueo

1BY8GQbnueP
1BY8GQbnuep

1BY8GQbnueQ
1BY8GQbnueq

1BY8GQbnueR
1BY8GQbnuer

1BY8GQbnueS
1BY8GQbnues

1BY8GQbnueT
1BY8GQbnuet

1BY8GQbnueU
1BY8GQbnueu

1BY8GQbnueV
1BY8GQbnuev

1BY8GQbnueW
1BY8GQbnuew

1BY8GQbnueX
1BY8GQbnuex

1BY8GQbnueY
1BY8GQbnuey

1BY8GQbnueZ
1BY8GQbnuez

[bibilgin]

THERE ARE MULTIPLE COMBINATIONS THESE ADDRESSES EXIST WE JUST DON'T HAVE THEIR PRIVATE KEYS YET BUT THERE ARE ENDLESS COMBINATIONS... I FOUND THESE THIS MONTH

This month?

I can find all of these in 1 day, even in half a day.

[bitcoinpuzzles621]

A long time ago, I would think that the prefixes were important too and that I could somehow use them in my code.  But eventually I just realized they dont help very much.  Its still all just a random search space and the solution could still be anywhere.  My code though is also terrible and can only find 1BY8G prefixes most days.  So you guys are far ahead of me in your progress if you believe that the longer prefixes are important.   I just am trying to say that I dont believe they are as important anymore.  I am more in agreement with the skeptics that post here recently about the prefixes instead.   

[hotmoney]

bibilgin  How so, Bibilgin? I use an RTX 4060, and it goes to 1320 MH/s overclocked. Which card do you use, Bibilgin?

[b0dre]

I can find all of these in 1 day, even in half a day.

Which tools are you using?

[hotmoney]

I discovered last month the correct way to transfer without being robbed, without RBF. The method I use to transfer funds from wallets with 66 to 70 bits—I tested everything, especially 67—works with the method I created, without Marapool or Electrum. And it works. I even tried to steal from myself, and I had friends with powerful cards try

as well. I made the transfer, and 10 friends tried to steal from me, but it didn’t work. Even I tried to do an RBF, but it doesn’t replace the transaction, no matter how high I set the fee.

I found the flaw that allows thieves to steal, and if you use my method, it prevents this. If anyone wants to test with me, just let me know—I’m available. Forget Marapool and forget mining your own blocks. This is the only way I’ve managed to make it work.  I set a super low fee, and it stayed there for about 17 minutes, and no one

managed to steal it—not even I was able to replace the transaction. The only way to accelerate it was by doing a CPFP (Child Pays for Parent) on the receiver's side, and that’s it.  f anyone wants to test with me or talk to me, feel free. I had to study a lot to achieve this. Currently, I’m using a Raspberry Pi and some additional tools to make the

transfer. No boot has been able to steal from me—I’ve even tested it in under 5 seconds, and it doesn’t perform an RBF or manage to replace the transaction.

If anyone wants to test with me today, I can transfer $10 for you to try and steal it with your boots. I'll create a 67-bit key and share the address with you, okay? You can get the public key from the mempool with your bots, but you won’t be able to steal it.

Does anyone want to collaborate with a few dollars to do this today? I’ll leave the wallet here—I'll do it at 10 PM tonight. I'm in Uruguay, sorry for my bad English.

This will be the wallet (67-bit):

1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR

Let me know who will try to steal it today and who will send some funds to this wallet!

[WanderingPhilospher]

I discovered last month the correct way to transfer without being robbed, without RBF. The method I use to transfer funds from wallets with 66 to 70 bits—I tested everything, especially 67—works with the method I created, without Marapool or Electrum. And it works. I even tried to steal from myself, and I had friends with powerful cards try

as well. I made the transfer, and 10 friends tried to steal from me, but it didn’t work. Even I tried to do an RBF, but it doesn’t replace the transaction, no matter how high I set the fee.

I found the flaw that allows thieves to steal, and if you use my method, it prevents this. If anyone wants to test with me, just let me know—I’m available. Forget Marapool and forget mining your own blocks. This is the only way I’ve managed to make it work.  I set a super low fee, and it stayed there for about 17 minutes, and no one

managed to steal it—not even I was able to replace the transaction. The only way to accelerate it was by doing a CPFP (Child Pays for Parent) on the receiver's side, and that’s it.  f anyone wants to test with me or talk to me, feel free. I had to study a lot to achieve this. Currently, I’m using a Raspberry Pi and some additional tools to make the

transfer. No bot has been able to steal from me—I’ve even tested it in under 5 seconds, and it doesn’t perform an RBF or manage to replace the transaction.

Just post your step by step method or don't talk about it. Mara works and the step by step is out there.

Lemme guess you will "help" the finder out for a small 3 BTC fee, lol.

[hotmoney]

WanderingPhilosopher, look, I don’t trust Marapool. Either they or someone there might have bad intentions. I don’t want any fees, I won’t charge 3 BTC or anything like that, but feel free to try. I also have bills to pay, and energy is expensive here. I know there’s an easy tutorial with Marapool, but it usually doesn’t work, and it says it's offline. So I don’t trust it; I’ve tried it before, and it took a long time. I prefer to do it my way—nothing works better.

As for RBF, there’s a lot of FOMO (fear of missing out) and fear involved. It’s not easy to steal from someone if the parameters are set correctly.

[mcdouglasx]

I discovered last month the correct way to transfer without being robbed, without RBF. The method I use to transfer funds from wallets with 66 to 70 bits—I tested everything, especially 67—works with the method I created, without Marapool or Electrum. And it works. I even tried to steal from myself, and I had friends with powerful cards try

as well. I made the transfer, and 10 friends tried to steal from me, but it didn’t work. Even I tried to do an RBF, but it doesn’t replace the transaction, no matter how high I set the fee.

I found the flaw that allows thieves to steal, and if you use my method, it prevents this. If anyone wants to test with me, just let me know—I’m available. Forget Marapool and forget mining your own blocks. This is the only way I’ve managed to make it work.  I set a super low fee, and it stayed there for about 17 minutes, and no one

managed to steal it—not even I was able to replace the transaction. The only way to accelerate it was by doing a CPFP (Child Pays for Parent) on the receiver's side, and that’s it.  f anyone wants to test with me or talk to me, feel free. I had to study a lot to achieve this. Currently, I’m using a Raspberry Pi and some additional tools to make the

transfer. No boot has been able to steal from me—I’ve even tested it in under 5 seconds, and it doesn’t perform an RBF or manage to replace the transaction.

If anyone wants to test with me today, I can transfer $10 for you to try and steal it with your boots. I'll create a 67-bit key and share the address with you, okay? You can get the public key from the mempool with your bots, but you won’t be able to steal it.

Does anyone want to collaborate with a few dollars to do this today? I’ll leave the wallet here—I'll do it at 10 PM tonight. I'm in Uruguay, sorry for my bad English.

This will be the wallet (67-bit):

1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR

Let me know who will try to steal it today and who will send some funds to this wallet!

This test with your friends is not valid for multiple reasons, since you have exposed this address, I invite you to fund it and give a notice here of the time and day you will do it, and you will see if your method works or not.
Even knowing how bitcoin works, if you transmit your transaction and its pk is in bit67 it will surely be replaced, because I doubt there is a different technique that has not been previously raised here.

[hotmoney]

message   15/01/2025 hotmoney


address    1BY8GQbBPGYEC58s9ckHmqf9doEX9mCKPR


signature   H0J+wKAwGGMiVWHLuwEaZpLePkQAYx0HoTVvEZJu/wx3N6QYbUJMuajlj//yyjD7WLh42Ydlg+/vTJm50Td1LS0=



I can financially manage, yes, but if someone is willing to send a small amount for testing, $10 or $20 should be enough. Once the value enters, I will withdraw it to another 67-bit wallet to keep trying to see if any bot can catch it, though I’m sure they won’t succeed. It can be today if someone sends $10, I can do this.

It can be today at 22:00 o'clock. I’m sure no one will be able to override the RBF, not even the most powerful bot will succeed.

Of course, if someone knows the same thing I discovered, they won't publish it. There are a lot of good software that no one will put here for free, because those who know how to fish good fish will fish for themselves and won't show the techniques to others.

[WanderingPhilospher]

WanderingPhilosopher, look, I don’t trust Marapool. Either they or someone there might have bad intentions. I don’t want any fees, I won’t charge 3 BTC or anything like that, but feel free to try. I also have bills to pay, and energy is expensive here. I know there’s an easy tutorial with Marapool, but it usually doesn’t work, and it says it's offline. So I don’t trust it; I’ve tried it before, and it took a long time. I prefer to do it my way—nothing works better.

As for RBF, there’s a lot of FOMO (fear of missing out) and fear involved. It’s not easy to steal from someone if the parameters are set correctly.

Just because you couldn't get it to work, doesn't mean it doesn't. Several of us have tested this method and it has worked every time.

Spread solutions, instead of fear. Maybe if you post your fail-proof method, the solver may use it and donate you something. If not, I imagine they will use Mara or take a shot in the dark.

[hotmoney]

I am selling it for 1 BTC. If you are interested, feel free to contact me. Thank you. I will not share any further details—those willing to take a leap of faith or use Mara can proceed at their own risk.

There are proxies involved, and hackers can obtain your private key (PK) even through them. You managed to avoid this because the addresses you used were not part of the 67 range from the challenge. The challenge addresses are already configured with proxies and other hacker tools designed to extract the key in just 5 seconds using an RTX 4090, lol.

I’m not saying that Mara doesn’t work; of course, it does, and it effectively hides the private key. However, you not tested it using the challenge addresses?. These addresses, starting from 67 and above, are actively monitored by hackers—even within Mara. They use SSH proxies and pre-configured scripts that might not even be known to the people running the system, but they are capable of extracting sensitive information in seconds.

With the wallets you tested, the bad hackers wouldn’t even bother trying to steal. Remember, the second mouse always gets the cheese.

[WanderingPhilospher]

I am selling it for 1 BTC. If you are interested, feel free to contact me. Thank you. I will not share any further details—those willing to take a leap of faith or use Mara can proceed at their own risk.

There are proxies involved, and hackers can obtain your private key (PK) even through them. You managed to avoid this because the addresses you used were not part of the 67 range from the challenge. The challenge addresses are already configured with proxies and other hacker tools designed to extract the key in just 5 seconds using an RTX 4090, lol.

I’m not saying that Mara doesn’t work; of course, it does, and it effectively hides the private key. However, you not tested it using the challenge addresses?. These addresses, starting from 67 and above, are actively monitored by hackers—even within Mara. They use SSH proxies and pre-configured scripts that might not even be known to the people running the system, but they are capable of extracting sensitive information in seconds.

With the wallets you tested, the bad hackers wouldn’t even bother trying to steal. Remember, the second mouse always gets the cheese.

Ok, it's obvious you have no clue what you are saying now. Did you test the address of a previous found wallet? No. If I had the priv key to the 66 or 67 wallet, I wouldn't run a test with it, I would just sweep it lol.

We all know about solving any key under 80 bits within mere seconds.

And why heck no I'm not interested in your 1 BTC method lol. And neither will no one on here. Watch how it all unfolds when 67 is found.

[fireman3100]

This is the first time I have posted here but have been reading this board for a few months. I am a math guy and am disabled.  Being disabled and not able to do much of anything physical I have dove head first in cryptography focusing on bitcoin wallets and these puzzles. Now I have finally found a pattern and mathematical equations to narrow down the location to within about 1-2% of a specific set of keys in the ranges where the private key is located. A lot of it I have to thank all of you and your posts concerning puzzle 67. Problem is that i have a crappy computer that can't scan private keys worth a damn. So still going through a quintillion set of keys still will take along time without having the resources to do so. And the cloud search on the website doesn't allow you to do custom range searches or I would have been done by now. Also I know a little code to get in trouble with but not enough to be fully able to write a python code for the other cloud search over on the other website.

With so many other people working on this puzzle I doubt if it will be unsolved much longer.

I have two other ways to solve the puzzles but once again don't have the coding experience and know how with python, java script, etc. to do it. I am not going to divulge the ways because then it would put me at a severe disadvantage because there are many programmers out there that would leave me and others in the dust with their coding superiority. For example, with all the information on this puzzle everyone has published on this forum gave me a plethora of information for me to spend the last three months to find my edge to narrow down the location. So I am not going to disclose here but would like to collaborate with people who are serious about solving these puzzles. Note that with what I have found and able to do all the puzzles became not impossible or improbable anymore. With bitcoin continuing to blow through the roof, this is life changing money for a lot of people including me.

So if you are serious and wish to collaborate, email me and we will talk. But I am not just gonna jump in with just anyone.

Also to show I am not shoveling a bunch of crap there are 73 plus quintillion keys in this puzzle. Each main range has roughly 18-19 quintillion keys, with roughly 1.1 or so quintillion keys in each sub range and so on and so forth. My computer can only scan roughly 1 trillion keys a day. And I only make a very small amount of money enough so I can't afford a new computer to get one with a GPU to scan faster. I know I don't have to explain myself but with some of the crackpots that have been on here I want to show that I am not one of them. Sorry for rambling.

My name is Lee and my email is freshstart2900@outlook.com.

[bibilgin]

bibilgin  How so, Bibilgin? I use an RTX 4060, and it goes to 1320 MH/s overclocked. Which card do you use, Bibilgin?

I have 3 4070 ti 7000m/sec speed. (approximately)

But I find around 15-20 1BY8GQbnu prefixes per day. Sometimes more.

Which tools are you using?

I use VanitySearch256.

Actually, the important thing here is to calculate the range you want to scan and where that range is before the program. In other words, I am working with PROBABILITY and MATHEMATICAL theorem.

[saatoshi_falling]

I am selling it for 1 BTC

lol

I am a math guy and am disabled.... Now I have finally found a pattern

and lol
I rarely laugh reading things but I swear you guys provide some level of entertainment not found elsewhere.