Bitcoin puzzle transaction ~32 BTC prize to who solves it

[mcdouglasx]

Maybe but MARA panicked and already closed Slipstream.

Mara has never said that the service left permanently.

"Sorry for the inconvenience but we’re performing some maintenance at the moment. We’ll be back online shortly! If you need to, you can contact support."

I don't know why there's such a rush to get Mara working again, since it's most likely that no one has found the private key for any of the following vulnerable puzzles. And if, by some stroke of luck, someone has already found it, they probably have plenty of time to wait for the service to be back online.
I don't think the service is actually undergoing maintenance; they must be implementing some important changes.

[rt07]

Yes, with AI I did a summary.

Quantum computers → threaten old Bitcoin wallets → ~5.6M BTC are vulnerable → this creates two simultaneous crises: technical (BIP-361 proposes freezing the coins) and market-related (any freeze = panic and the worst day in Bitcoin's history).
MARA, as the largest public miner with 38,000+ BTC on its balance sheet, can't ignore this — and responds in four ways at once: launches the MARA Foundation for quantum research, pivots into AI/HPC data centers (hedging against Bitcoin instability), sold 15,133 BTC ($1.1B) to pay off debt, and in the process shuts down niche products like Slipstream.

Quantum computers will not threaten unspent keys

Maybe but MARA panicked and already closed Slipstream.

Man, I think there is a better alternative to Slipstream, and there will certainly be one in the future.  

I agree, but this is a big opportunity for scammers too, and there could be a lot of scams. Currently, ViaBTC, AntPool, and F2Pool are working, but support is slow, and there's no guarantee of confirmation.

Maybe but MARA panicked and already closed Slipstream.

Mara has never said that the service left permanently.

"Sorry for the inconvenience but we’re performing some maintenance at the moment. We’ll be back online shortly! If you need to, you can contact support."

I don't know why there's such a rush to get Mara working again, since it's most likely that no one has found the private key for any of the following vulnerable puzzles. And if, by some stroke of luck, someone has already found it, they probably have plenty of time to wait for the service to be back online.
I don't think the service is actually undergoing maintenance; they must be implementing some important changes.

Their actions explain something. Perhaps you're right, time will tell.

[abdenn0ur]

If i find the key, i'll simply send them the transaction hex via email, wait for 2-3 days, if they don't respond or process the transaction, i'll broadcast it publicly, with high fees, multiple times, and if the transaction gets hijacked, so be it, it is what it is

[Menowa*]

If i find the key, i'll simply send them the transaction hex via email, wait for 2-3 days, if they don't respond or process the transaction, i'll broadcast it publicly, with high fees, multiple times, and if the transaction gets hijacked, so be it, it is what it is

then i hope somebody else finds it before you

[eggsylacer]

Why haven't the off-topic posts been deleted yet, and why haven't the authors of these posts been temporarily suspended? I'm talking about a message about some kind of mara.

[ldabasim]

Because the discussion currently is about 71 and 135 and 71 cannot be swept without mara. So its not off-topic but 50% of the topic. If you're some sort of a Perelman-like character who has zero care about the monetary rewards and is just interested in the solution, you're probably the only one.

[Ali_555]

https://sandbox.mara.com/


Who knows these are scammers?

[NUCLEAR7.1]

https://sandbox.mara.com/


Who knows these are scammers?

bro, they have thousands of Bitcoins and you think they're going to waste years chasing after just 7 Bitcoins?  

[rt07]

https://sandbox.mara.com/


Who knows these are scammers?

Sandbox.mara.com is a test site. Transactions there may not go into the real blockchain. For actually withdrawing you need to use the main slipstream.mara.com it's currently under maintenance.

[0xastraeus]

ENOUGH with MARA this and MARA that...

Slipstream has gone down many times previously for maintenance, it'll come back when it comes back.

The sandbox link is clearly a test subdomain much like how any other site might have a dev subdomain.

Leave them be and quit fearmongering.

[analyticnomad]

ENOUGH with MARA this and MARA that...

Slipstream has gone down many times previously for maintenance, it'll come back when it comes back.

The sandbox link is clearly a test subdomain much like how any other site might have a dev subdomain.

Leave them be and quit fearmongering.

Agreed. This thread is even more annoying than usual. MARA is fine. Everyone chill and try to find some keys.

[Diaghilev]

If I send a HEX (raw) transaction through a private miner, like VIA BTC, will they be able to find out my private key from my HEX transaction?

[rt07]

If I send a HEX (raw) transaction through a private miner, like VIA BTC, will they be able to find out my private key from my HEX transaction?

The private key cannot be find out from a HEX transaction. But ViaBTC works with public mempool, the transaction still ends up in the mempool and becomes visible to bots. With Slipstream the transaction goes directly to the pool, bypassing the public mempool.

[Cricktor]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

[NUCLEAR7.1]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

[Grzegorz2022]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

How did you reduce puzzle 71 to 64?? Having only the address, since Public Key → SHA-256 Hash means you lose the original structure of the public key, then SHA-256 Hash → RIPEMD-160 loses the length and bit uniqueness. The result is shortened from 256 bits to 160 bits (20 bytes). So based on the address, it is impossible to reduce it — the only reduction is the disclosed range in which the address is located.

[stillhere@2009]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

How did you reduce puzzle 71 to 64?? Having only the address, since Public Key → SHA-256 Hash means you lose the original structure of the public key, then SHA-256 Hash → RIPEMD-160 loses the length and bit uniqueness. The result is shortened from 256 bits to 160 bits (20 bytes). So based on the address, it is impossible to reduce it — the only reduction is the disclosed range in which the address is located.

The vulnerability I discovered is difficult to find, so the creator thought no one would be able to access it, but I did. He mentioned in his post that there's no definitive pattern, but there are two possibilities: either he wasn't aware of the serious vulnerability, or he was aware of it but didn't expect anyone to discover it. Regarding image, 71 puzzle, it falls within the red line. In the next step, this is a 100% certain prediction; it can't be outside the red line. Therefore, the area to be scanned is quite large, but fortunately, the maximum area is 65 bits, so I don't have to scan all 71 bits. After some in-depth research, I found another method that allowed me to reduce the 65 bits to approximately 62 bits. This image is just one of dozens I have, and it doesn't represent the complete method yet because the details are much deeper, and I don't want to share them. https://imgur.com/a/fA9O7Aw 

Someone please install an update on this guy’s brain

[NUCLEAR7.1]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

How did you reduce puzzle 71 to 64?? Having only the address, since Public Key → SHA-256 Hash means you lose the original structure of the public key, then SHA-256 Hash → RIPEMD-160 loses the length and bit uniqueness. The result is shortened from 256 bits to 160 bits (20 bytes). So based on the address, it is impossible to reduce it — the only reduction is the disclosed range in which the address is located.

The vulnerability I discovered is difficult to find, so the creator thought no one would be able to access it, but I did. He mentioned in his post that there's no definitive pattern, but there are two possibilities: either he wasn't aware of the serious vulnerability, or he was aware of it but didn't expect anyone to discover it. Regarding image, 71 puzzle, it falls within the red line. In the next step, this is a 100% certain prediction; it can't be outside the red line. Therefore, the area to be scanned is quite large, but fortunately, the maximum area is 65 bits, so I don't have to scan all 71 bits. After some in-depth research, I found another method that allowed me to reduce the 65 bits to approximately 62 bits. This image is just one of dozens I have, and it doesn't represent the complete method yet because the details are much deeper, and I don't want to share them. https://imgur.com/a/fA9O7Aw  

Someone please install an update on this guy’s brain

I think you're the one who needs a brain update , considering your advanced age. My brain is currently in a growth phase, accepting pure and logical analysis. For example, on March 21, 2026, at 02:37:00 AM, you said, "I would have solved the 71 problem in a few months if I had an RTX 5090 graphics card." Even a baby could understand that you wouldn't be able to find the key with a single 5090, even if you were the luckiest person, not even an astronomical stroke of luck would work. You must accept that someone from the new generation found a vulnerability and you didn't.  

[analyticnomad]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

How did you reduce puzzle 71 to 64?? Having only the address, since Public Key → SHA-256 Hash means you lose the original structure of the public key, then SHA-256 Hash → RIPEMD-160 loses the length and bit uniqueness. The result is shortened from 256 bits to 160 bits (20 bytes). So based on the address, it is impossible to reduce it — the only reduction is the disclosed range in which the address is located.

The vulnerability I discovered is difficult to find, so the creator thought no one would be able to access it, but I did. He mentioned in his post that there's no definitive pattern, but there are two possibilities: either he wasn't aware of the serious vulnerability, or he was aware of it but didn't expect anyone to discover it. Regarding image, 71 puzzle, it falls within the red line. In the next step, this is a 100% certain prediction; it can't be outside the red line. Therefore, the area to be scanned is quite large, but fortunately, the maximum area is 65 bits, so I don't have to scan all 71 bits. After some in-depth research, I found another method that allowed me to reduce the 65 bits to approximately 62 bits. This image is just one of dozens I have, and it doesn't represent the complete method yet because the details are much deeper, and I don't want to share them. https://imgur.com/a/fA9O7Aw  

Someone please install an update on this guy’s brain

I think you're the one who needs a brain update , considering your advanced age. My brain is currently in a growth phase, accepting pure and logical analysis. For example, on March 21, 2026, at 02:37:00 AM, you said, "I would have solved the 71 problem in a few months if I had an RTX 5090 graphics card." Even a baby could understand that you wouldn't be able to find the key with a single 5090, even if you were the luckiest person, not even an astronomical stroke of luck would work. You must accept that someone from the new generation found a vulnerability and you didn't.  

A single 5090 has a significantly higher probability of finding the key at random within the next ten minutes than you having "found a vulnerability".

[NUCLEAR7.1]

...

What do you mean by "a private miner"? A miner with a private aka non-public mempool or what else?

I'm not aware that ViaBTC has a public service with a private mempool.

You also don't say anything about which puzzle solution's transaction you are talking about. A withdrawal of coins with a solution for puzzle #135 can be broadcasted to public mempools. A withdrawal of coins with a solution for puzzle #71 needs to be broadcasted non-publicly otherwise bots can steal the public key from the transaction in public mempools and find private key in seconds and then the RBF transaction replacement war begins.

This topic is always repeated. Look for another topic such as how to provide some GPUs almost for free. Regarding the 71-bit puzzle, I was able to reduce it to 64-bit. The biggest challenge to solve puzzle 71 is to provide at least 5090x10 to find the key within months.

How did you reduce puzzle 71 to 64?? Having only the address, since Public Key → SHA-256 Hash means you lose the original structure of the public key, then SHA-256 Hash → RIPEMD-160 loses the length and bit uniqueness. The result is shortened from 256 bits to 160 bits (20 bytes). So based on the address, it is impossible to reduce it — the only reduction is the disclosed range in which the address is located.

The vulnerability I discovered is difficult to find, so the creator thought no one would be able to access it, but I did. He mentioned in his post that there's no definitive pattern, but there are two possibilities: either he wasn't aware of the serious vulnerability, or he was aware of it but didn't expect anyone to discover it. Regarding image, 71 puzzle, it falls within the red line. In the next step, this is a 100% certain prediction; it can't be outside the red line. Therefore, the area to be scanned is quite large, but fortunately, the maximum area is 65 bits, so I don't have to scan all 71 bits. After some in-depth research, I found another method that allowed me to reduce the 65 bits to approximately 62 bits. This image is just one of dozens I have, and it doesn't represent the complete method yet because the details are much deeper, and I don't want to share them. https://imgur.com/a/fA9O7Aw  

Someone please install an update on this guy’s brain

I think you're the one who needs a brain update , considering your advanced age. My brain is currently in a growth phase, accepting pure and logical analysis. For example, on March 21, 2026, at 02:37:00 AM, you said, "I would have solved the 71 problem in a few months if I had an RTX 5090 graphics card." Even a baby could understand that you wouldn't be able to find the key with a single 5090, even if you were the luckiest person, not even an astronomical stroke of luck would work. You must accept that someone from the new generation found a vulnerability and you didn't.  

A single 5090 has a significantly higher probability of finding the key at random within the next ten minutes than you having "found a vulnerability".

The probability within 10 minutes is not zero, but it is so small that it is practically impossible.  0.0000002% That means 1 chance in 500 million This means you need, on average, hundreds of millions of the same attempt (10 minutes).   |  The comparison you made to me is scientifically illogical; it's merely an offensive response and not a genuine analysis.

The vulnerability is not a matter of "probability" but a matter of "proof".