Bitcoin puzzle transaction ~32 BTC prize to who solves it

[kuramuqnko]

I'll try to put this as clear as possible for the people reading here who don’t want to be misled. Who don’t want to get confused and, potentially, if they somehow manage to solve Puzzle 71, don’t want all their efforts, resources, or luck to go completely to waste.

There are two ways to take the funds from one of the puzzles: One is to find the private key of the  address and transfer the funds to another (your own) address. Finding the key is done through different forms of brute-forcing. The second way is to find the private key through reverse engineering from the public key. But in order to use the second method, someone must have already brute-forced the key and made a public transaction so that the public key becomes known. Different strategies. Personally, I find the second one much dirtier. In the first method, you're beating the game. In the second, you're screwing over a person.

Regarding the transactions. In the end, there are two ways to transfer the funds: via the public mempool and via the private mempool (MARA Slipstream). There have been many arguments about these two methods. Which one is the "right" one. Honestly, I think very few of those arguments have been sincere on either side. I believe that the people who claim that a transaction should go through the public mempool - only a very small portion of them genuinely believe that, and to me, they OBVIOUSLY don’t understand what would actually happen. The other part of people claiming that the public mempool should be used are simply those who also want to take the funds from Puzzle 71, but by using the second method. And if we say that even in MARA Slipstream the funds can be stolen is true, then in the worst case scenario the chances are 50/50. Let’s reduce this to the simplest math: with the public mempool, the chance of the funds being taken is 100 percent. With the private one  50.

Menowa* and Mafioso246 - I completely agree with both of you. And people like SimonNeedsBitcoin and mahmood1356 either have no idea how things actually work, or they’ve simply have a bot and choose to play dirty with the second method.

[Mafioso246]

I'll try to put this as clear as possible for the people reading here who don’t want to be misled. Who don’t want to get confused and, potentially, if they somehow manage to solve Puzzle 71, don’t want all their efforts, resources, or luck to go completely to waste.

There are two ways to take the funds from one of the puzzles: One is to find the private key of the  address and transfer the funds to another (your own) address. Finding the key is done through different forms of brute-forcing. The second way is to find the private key through reverse engineering from the public key. But in order to use the second method, someone must have already brute-forced the key and made a public transaction so that the public key becomes known. Different strategies. Personally, I find the second one much dirtier. In the first method, you're beating the game. In the second, you're screwing over a person.

Regarding the transactions. In the end, there are two ways to transfer the funds: via the public mempool and via the private mempool (MARA Slipstream). There have been many arguments about these two methods. Which one is the "right" one. Honestly, I think very few of those arguments have been sincere on either side. I believe that the people who claim that a transaction should go through the public mempool - only a very small portion of them genuinely believe that, and to me, they OBVIOUSLY don’t understand what would actually happen. The other part of people claiming that the public mempool should be used are simply those who also want to take the funds from Puzzle 71, but by using the second method. And if we say that even in MARA Slipstream the funds can be stolen is true, then in the worst case scenario the chances are 50/50. Let’s reduce this to the simplest math: with the public mempool, the chance of the funds being taken is 100 percent. With the private one  50.

Menowa* and Mafioso246 - I completely agree with both of you. And people like SimonNeedsBitcoin and mahmood1356 either have no idea how things actually work, or they’ve simply have a bot and choose to play dirty with the second method.

Simon was probably scammed in the past, which explains his attitude. But facts are facts. Mahmood, on the other hand, comes across as completely clueless. He clearly doesn’t understand, and he has this habit of forming opinions without having any real knowledge at least that’s what his posts suggest Their biggest issue is that there’s a 15-year-old thread full of context, and neither of them has read it. They fall into the trap of thinking their ideas are original, when in reality, they’re just rediscovering things that have been discussed for years.

[mahmood1356]

I'll try to put this as clear as possible for the people reading here who don’t want to be misled. Who don’t want to get confused and, potentially, if they somehow manage to solve Puzzle 71, don’t want all their efforts, resources, or luck to go completely to waste.

There are two ways to take the funds from one of the puzzles: One is to find the private key of the  address and transfer the funds to another (your own) address. Finding the key is done through different forms of brute-forcing. The second way is to find the private key through reverse engineering from the public key. But in order to use the second method, someone must have already brute-forced the key and made a public transaction so that the public key becomes known. Different strategies. Personally, I find the second one much dirtier. In the first method, you're beating the game. In the second, you're screwing over a person.

Regarding the transactions. In the end, there are two ways to transfer the funds: via the public mempool and via the private mempool (MARA Slipstream). There have been many arguments about these two methods. Which one is the "right" one. Honestly, I think very few of those arguments have been sincere on either side. I believe that the people who claim that a transaction should go through the public mempool - only a very small portion of them genuinely believe that, and to me, they OBVIOUSLY don’t understand what would actually happen. The other part of people claiming that the public mempool should be used are simply those who also want to take the funds from Puzzle 71, but by using the second method. And if we say that even in MARA Slipstream the funds can be stolen is true, then in the worst case scenario the chances are 50/50. Let’s reduce this to the simplest math: with the public mempool, the chance of the funds being taken is 100 percent. With the private one  50.

Menowa* and Mafioso246 - I completely agree with both of you. And people like SimonNeedsBitcoin and mahmood1356 either have no idea how things actually work, or they’ve simply have a bot and choose to play dirty with the second method.

Simon was probably scammed in the past, which explains his attitude. But facts are facts. Mahmood, on the other hand, comes across as completely clueless. He clearly doesn’t understand, and he has this habit of forming opinions without having any real knowledge at least that’s what his posts suggest Their biggest issue is that there’s a 15-year-old thread full of context, and neither of them has read it. They fall into the trap of thinking their ideas are original, when in reality, they’re just rediscovering things that have been discussed for years.

Why do you think that a history of posting and threads over many years can make your opinions correct or that other users should accept your words? In order for everyone to clearly see which one is correct,
 I would like to ask you and the rest of my friends if you or anyone else can tell us the private key to this address?
Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF



Certainly neither you nor any other 15-year-old user can do this in a few seconds. So stop your nonsense and don't be complacent about your perennial stalk, and I say that in these few years you have only wasted your time and if you had gone to another job instead of talking nonsense, it would have been more beneficial for you.

[Mafioso246]

I'll try to put this as clear as possible for the people reading here who don’t want to be misled. Who don’t want to get confused and, potentially, if they somehow manage to solve Puzzle 71, don’t want all their efforts, resources, or luck to go completely to waste.

There are two ways to take the funds from one of the puzzles: One is to find the private key of the  address and transfer the funds to another (your own) address. Finding the key is done through different forms of brute-forcing. The second way is to find the private key through reverse engineering from the public key. But in order to use the second method, someone must have already brute-forced the key and made a public transaction so that the public key becomes known. Different strategies. Personally, I find the second one much dirtier. In the first method, you're beating the game. In the second, you're screwing over a person.

Regarding the transactions. In the end, there are two ways to transfer the funds: via the public mempool and via the private mempool (MARA Slipstream). There have been many arguments about these two methods. Which one is the "right" one. Honestly, I think very few of those arguments have been sincere on either side. I believe that the people who claim that a transaction should go through the public mempool - only a very small portion of them genuinely believe that, and to me, they OBVIOUSLY don’t understand what would actually happen. The other part of people claiming that the public mempool should be used are simply those who also want to take the funds from Puzzle 71, but by using the second method. And if we say that even in MARA Slipstream the funds can be stolen is true, then in the worst case scenario the chances are 50/50. Let’s reduce this to the simplest math: with the public mempool, the chance of the funds being taken is 100 percent. With the private one  50.

Menowa* and Mafioso246 - I completely agree with both of you. And people like SimonNeedsBitcoin and mahmood1356 either have no idea how things actually work, or they’ve simply have a bot and choose to play dirty with the second method.

Simon was probably scammed in the past, which explains his attitude. But facts are facts. Mahmood, on the other hand, comes across as completely clueless. He clearly doesn’t understand, and he has this habit of forming opinions without having any real knowledge at least that’s what his posts suggest Their biggest issue is that there’s a 15-year-old thread full of context, and neither of them has read it. They fall into the trap of thinking their ideas are original, when in reality, they’re just rediscovering things that have been discussed for years.

Why do you think that a history of posting and threads over many years can make your opinions correct or that other users should accept your words? In order for everyone to clearly see which one is correct,
 I would like to ask you and the rest of my friends if you or anyone else can tell us the private key to this address?
Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF



Certainly neither you nor any other 15-year-old user can do this in a few seconds. So stop your nonsense and don't be complacent about your perennial stalk, and I say that in these few years you have only wasted your time and if you had gone to another job instead of talking nonsense, it would have been more beneficial for you.

I don't think there's anything I can do for you anymore, but you can do it yourself and Send money to that address and see how many seconds it takes for them to withdraw it

https://github.com/RetiredC/RCKangaroo
https://github.com/WanderingPhilosopher/RCKangaroo-Fork

Before vanishing into silence, feel free to share the result here no one’s going to judge you, don’t worry. You might get labeled a fool, but I’m sure you can live with that.

[onepuzzle]

Don't say this nonsense in this thread. What I said has nothing to do with standard transaction sending methods. Everyone has been using this method since the beginning of Bitcoin. Your nonsense is a misleading way of breaking the standard and normal principles of sending transactions. So stop telling your lies. Are you getting paid by Slipstream for these ads?

We all know what happened to the people who sent the transaction the normal way, and we know what happened to those who used Slipstream.

We’ve already played this game once; in the end, I won that round. There are already tests:

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.
30 usd price.
Public key will be exposed tomorrow 27 June 2025 between 13.00 and 14.00 UTC.
Every participant BTC address which will be visible at least once in mempool RBF timeline will get 10 usd in BTC.

Thanks.

Be smart and use it: https://github.com/onepuzzle/btc-transaction

[Mafioso246]

Don't say this nonsense in this thread. What I said has nothing to do with standard transaction sending methods. Everyone has been using this method since the beginning of Bitcoin. Your nonsense is a misleading way of breaking the standard and normal principles of sending transactions. So stop telling your lies. Are you getting paid by Slipstream for these ads?

We all know what happened to the people who sent the transaction the normal way, and we know what happened to those who used Slipstream.

We’ve already played this game once; in the end, I won that round. There are already tests:

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.
30 usd price.
Public key will be exposed tomorrow 27 June 2025 between 13.00 and 14.00 UTC.
Every participant BTC address which will be visible at least once in mempool RBF timeline will get 10 usd in BTC.

Thanks.

Be smart and use it: https://github.com/onepuzzle/btc-transaction

He doesn’t see it because he hasn’t read it and even if he does, he won’t understand what he’s reading. Maybe it’s a language barrier, but I doubt it. Right now, he’s probably trying to figure out what “kangaroo” or “bsgs” even means. If he’s testing RetiredCoder’s kangaroo implementation or WP’s fork, I’m almost certain he’ll see the results and think: “Omg, I found it so quickly! I should definitely try this on 135 too.” Then he’ll start brute-forcing that.

When he realizes it doesn’t work the same way, he’ll be disappointed. And of course, he’ll vanish into silence and return 3–5 months later with a new account and start posting again. Sadly, that’s the cycle this thread seems to follow for some users.

What I’ve come to understand is that being literate doesn’t mean you actually comprehend what you read. For the first time, I felt like I was talking to a wall. It’s sad, but true.

[mahmood1356]

Don't say this nonsense in this thread. What I said has nothing to do with standard transaction sending methods. Everyone has been using this method since the beginning of Bitcoin. Your nonsense is a misleading way of breaking the standard and normal principles of sending transactions. So stop telling your lies. Are you getting paid by Slipstream for these ads?

We all know what happened to the people who sent the transaction the normal way, and we know what happened to those who used Slipstream.

We’ve already played this game once; in the end, I won that round. There are already tests:

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.
30 usd price.
Public key will be exposed tomorrow 27 June 2025 between 13.00 and 14.00 UTC.
Every participant BTC address which will be visible at least once in mempool RBF timeline will get 10 usd in BTC.

Thanks.

Be smart and use it: https://github.com/onepuzzle/btc-transaction

He doesn’t see it because he hasn’t read it and even if he does, he won’t understand what he’s reading. Maybe it’s a language barrier, but I doubt it. Right now, he’s probably trying to figure out what “kangaroo” or “bsgs” even means. If he’s testing RetiredCoder’s kangaroo implementation or WP’s fork, I’m almost certain he’ll see the results and think: “Omg, I found it so quickly! I should definitely try this on 135 too.” Then he’ll start brute-forcing that.

When he realizes it doesn’t work the same way, he’ll be disappointed. And of course, he’ll vanish into silence and return 3–5 months later with a new account and start posting again. Sadly, that’s the cycle this thread seems to follow for some users.

What I’ve come to understand is that being literate doesn’t mean you actually comprehend what you read. For the first time, I felt like I was talking to a wall. It’s sad, but true.

Why do you resist understanding? Those who talk a lot think less!

[Mafioso246]

Don't say this nonsense in this thread. What I said has nothing to do with standard transaction sending methods. Everyone has been using this method since the beginning of Bitcoin. Your nonsense is a misleading way of breaking the standard and normal principles of sending transactions. So stop telling your lies. Are you getting paid by Slipstream for these ads?

We all know what happened to the people who sent the transaction the normal way, and we know what happened to those who used Slipstream.

We’ve already played this game once; in the end, I won that round. There are already tests:

Mempool bot competition #2:

Address: 12B2uyEpoRsLDmJDLHJK5n4LeG946XtqM2
Puzzle 75 address space.
30 usd price.
Public key will be exposed tomorrow 27 June 2025 between 13.00 and 14.00 UTC.
Every participant BTC address which will be visible at least once in mempool RBF timeline will get 10 usd in BTC.

Thanks.

Be smart and use it: https://github.com/onepuzzle/btc-transaction

He doesn’t see it because he hasn’t read it and even if he does, he won’t understand what he’s reading. Maybe it’s a language barrier, but I doubt it. Right now, he’s probably trying to figure out what “kangaroo” or “bsgs” even means. If he’s testing RetiredCoder’s kangaroo implementation or WP’s fork, I’m almost certain he’ll see the results and think: “Omg, I found it so quickly! I should definitely try this on 135 too.” Then he’ll start brute-forcing that.

When he realizes it doesn’t work the same way, he’ll be disappointed. And of course, he’ll vanish into silence and return 3–5 months later with a new account and start posting again. Sadly, that’s the cycle this thread seems to follow for some users.

What I’ve come to understand is that being literate doesn’t mean you actually comprehend what you read. For the first time, I felt like I was talking to a wall. It’s sad, but true.

Why do you resist understanding? Those who talk a lot think less!

From now on, I’ll just ignore you. Trying to understand a 48 year old teenager who seeks attention by saying 'I found these with just simple Python code" but using someone else’s list' is pointless. I wish you success, I truly hope you’re the one who finds 71, transfers it the in your groundbreaking way, and that others are genuinely happy about it.

[Spirik]

Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF

I have a modest rtx 2060S + GTX1060ti — solution in about 2-5 minutes. For the sake of decency, you could at least put 1 dollar there. 

Code:

~/RCKangaroo$ time ./rckangaroo -dp 16 -range 85 -start 1 -pubkey 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc -tames tames85.dat -max 13
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 2060 SUPER, 7.78 GB, 34 CUs, cap 7.5, PCI 3, L2 size: 4096 KB
GPU 1: NVIDIA GeForce GTX 1660 Ti, 5.79 GB, 24 CUs, cap 7.5, PCI 8, L2 size: 1536 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: AF13C80E78581D870A96F112CF681DB1CAD6F9DA26860F2C25DD9A9125B0BDFC
Y: C9EDCFE647622731DBE2E9E7291E8498BA0AFD44D3356C59B96F630218BDD3FB
Offset: 0000000000000000000000000000000000000000000000000000000000000001

Solving point: Range 85 bits, DP 16, start...
SOTA method, estimated ops: 2^42.702, RAM for DPs: 4.253 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^46.402, max RAM for DPs: 53.044 GB
Estimated DPs per kangaroo: 57.427.
load tames...
tames loaded
GPU 0: allocated 3284 MB, 1114112 kangaroos. OldGpuMode: Yes
GPU 1: allocated 2322 MB, 786432 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2074 MKeys/s, Err: 0, DPs: 1418283K/109142K, Time: 0d:00h:00m/0d:00h:57m
MAIN: Speed: 2758 MKeys/s, Err: 0, DPs: 1418714K/109142K, Time: 0d:00h:00m/0d:00h:43m
MAIN: Speed: 2745 MKeys/s, Err: 0, DPs: 1419132K/109142K, Time: 0d:00h:00m/0d:00h:43m
***
MAIN: Speed: 2695 MKeys/s, Err: 0, DPs: 1424111K/109142K, Time: 0d:00h:02m/0d:00h:44m
Stopping work ...
Point solved, K: 0.066 (with DP and GPU overheads)

PRIVATE KEY: 0000000000000000000000000000000000000000000000612E8BA2E8BAC75640

real	4m35,010s
user	1m11,596s
sys	0m45,348s[s][/s]

[Mafioso246]

Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF

I have a modest rtx 2060S + GTX1060ti — solution in about 2-5 minutes. For the sake of decency, you could at least put 1 dollar there. 

Code:

~/RCKangaroo$ time ./rckangaroo -dp 16 -range 85 -start 1 -pubkey 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc -tames tames85.dat -max 13
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 2060 SUPER, 7.78 GB, 34 CUs, cap 7.5, PCI 3, L2 size: 4096 KB
GPU 1: NVIDIA GeForce GTX 1660 Ti, 5.79 GB, 24 CUs, cap 7.5, PCI 8, L2 size: 1536 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: AF13C80E78581D870A96F112CF681DB1CAD6F9DA26860F2C25DD9A9125B0BDFC
Y: C9EDCFE647622731DBE2E9E7291E8498BA0AFD44D3356C59B96F630218BDD3FB
Offset: 0000000000000000000000000000000000000000000000000000000000000001

Solving point: Range 85 bits, DP 16, start...
SOTA method, estimated ops: 2^42.702, RAM for DPs: 4.253 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^46.402, max RAM for DPs: 53.044 GB
Estimated DPs per kangaroo: 57.427.
load tames...
tames loaded
GPU 0: allocated 3284 MB, 1114112 kangaroos. OldGpuMode: Yes
GPU 1: allocated 2322 MB, 786432 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2074 MKeys/s, Err: 0, DPs: 1418283K/109142K, Time: 0d:00h:00m/0d:00h:57m
MAIN: Speed: 2758 MKeys/s, Err: 0, DPs: 1418714K/109142K, Time: 0d:00h:00m/0d:00h:43m
MAIN: Speed: 2745 MKeys/s, Err: 0, DPs: 1419132K/109142K, Time: 0d:00h:00m/0d:00h:43m
***
MAIN: Speed: 2695 MKeys/s, Err: 0, DPs: 1424111K/109142K, Time: 0d:00h:02m/0d:00h:44m
Stopping work ...
Point solved, K: 0.066 (with DP and GPU overheads)

PRIVATE KEY: 0000000000000000000000000000000000000000000000612E8BA2E8BAC75640

real	4m35,010s
user	1m11,596s
sys	0m45,348s[s][/s]

All that effort for nothing (:  now he’ll show up with that brilliant brain and groundbreaking ideas and say:

“See? It gets found in 2 to 5 minutes, and during that time I can just pay a high fee and make a regular transfer.”

LMAO anyway, I had a lot of fun today.

[SimonNeedsBitcoin]

Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF

I have a modest rtx 2060S + GTX1060ti — solution in about 2-5 minutes. For the sake of decency, you could at least put 1 dollar there.  

Code:

~/RCKangaroo$ time ./rckangaroo -dp 16 -range 85 -start 1 -pubkey 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc -tames tames85.dat -max 13
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 2060 SUPER, 7.78 GB, 34 CUs, cap 7.5, PCI 3, L2 size: 4096 KB
GPU 1: NVIDIA GeForce GTX 1660 Ti, 5.79 GB, 24 CUs, cap 7.5, PCI 8, L2 size: 1536 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: AF13C80E78581D870A96F112CF681DB1CAD6F9DA26860F2C25DD9A9125B0BDFC
Y: C9EDCFE647622731DBE2E9E7291E8498BA0AFD44D3356C59B96F630218BDD3FB
Offset: 0000000000000000000000000000000000000000000000000000000000000001

Solving point: Range 85 bits, DP 16, start...
SOTA method, estimated ops: 2^42.702, RAM for DPs: 4.253 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^46.402, max RAM for DPs: 53.044 GB
Estimated DPs per kangaroo: 57.427.
load tames...
tames loaded
GPU 0: allocated 3284 MB, 1114112 kangaroos. OldGpuMode: Yes
GPU 1: allocated 2322 MB, 786432 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2074 MKeys/s, Err: 0, DPs: 1418283K/109142K, Time: 0d:00h:00m/0d:00h:57m
MAIN: Speed: 2758 MKeys/s, Err: 0, DPs: 1418714K/109142K, Time: 0d:00h:00m/0d:00h:43m
MAIN: Speed: 2745 MKeys/s, Err: 0, DPs: 1419132K/109142K, Time: 0d:00h:00m/0d:00h:43m
***
MAIN: Speed: 2695 MKeys/s, Err: 0, DPs: 1424111K/109142K, Time: 0d:00h:02m/0d:00h:44m
Stopping work ...
Point solved, K: 0.066 (with DP and GPU overheads)

PRIVATE KEY: 0000000000000000000000000000000000000000000000612E8BA2E8BAC75640

real	4m35,010s
user	1m11,596s
sys	0m45,348s[s][/s]

All that effort for nothing (:  now he’ll show up with that brilliant brain and groundbreaking ideas and say:

“See? It gets found in 2 to 5 minutes, and during that time I can just pay a high fee and make a regular transfer.”

LMAO anyway, I had a lot of fun today.

Besides the analysis of the private key from the public key, I'd like to ask: is the public key given directly to you? How do you know the winner is transferring and broadcasting the fund? Do you get the public key immediately after the winner broadcast the transation? Does this take time?

Also, once you have the private key, if you manually enter it and then transfer the funds using a higher fee, wouldn't that take a long time? Even if you use a bot, you'll need to construct a long transaction string, right? All of these take time.

Are those who claim theft can be done in seconds really that confident?

[kTimesG]

Besides the analysis of the private key from the public key, I'd like to ask: is the public key given directly to you? How do you know the winner is transferring and broadcasting the fund? Do you get the public key immediately after the winner broadcast the transation? Does this take time?

Also, once you have the private key, if you manually enter it and then transfer the funds using a higher fee, wouldn't that take a long time? Even if you use a bot, you'll need to construct a long transaction string, right? All of these take time.

Are those who claim theft can be done in seconds really that confident?

I kept silent because it wasn't worth my time but can I ask you something?

Why are you here? What is the purpose?

It takes less than 2 seconds to break the private key of Puzzle 71 (once the initial TX is in the mempool), create the TX, and broadcast it, and to get it accepted by any miner.

Please stop the non-sense, you are polluting the discussion.

Let me say it again: you might not have time to open a new browser tab and check your first TX, before it gets replaced.

[Menowa*]

Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF

I have a modest rtx 2060S + GTX1060ti — solution in about 2-5 minutes. For the sake of decency, you could at least put 1 dollar there. 

Code:

~/RCKangaroo$ time ./rckangaroo -dp 16 -range 85 -start 1 -pubkey 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc -tames tames85.dat -max 13
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 2060 SUPER, 7.78 GB, 34 CUs, cap 7.5, PCI 3, L2 size: 4096 KB
GPU 1: NVIDIA GeForce GTX 1660 Ti, 5.79 GB, 24 CUs, cap 7.5, PCI 8, L2 size: 1536 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: AF13C80E78581D870A96F112CF681DB1CAD6F9DA26860F2C25DD9A9125B0BDFC
Y: C9EDCFE647622731DBE2E9E7291E8498BA0AFD44D3356C59B96F630218BDD3FB
Offset: 0000000000000000000000000000000000000000000000000000000000000001

Solving point: Range 85 bits, DP 16, start...
SOTA method, estimated ops: 2^42.702, RAM for DPs: 4.253 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^46.402, max RAM for DPs: 53.044 GB
Estimated DPs per kangaroo: 57.427.
load tames...
tames loaded
GPU 0: allocated 3284 MB, 1114112 kangaroos. OldGpuMode: Yes
GPU 1: allocated 2322 MB, 786432 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2074 MKeys/s, Err: 0, DPs: 1418283K/109142K, Time: 0d:00h:00m/0d:00h:57m
MAIN: Speed: 2758 MKeys/s, Err: 0, DPs: 1418714K/109142K, Time: 0d:00h:00m/0d:00h:43m
MAIN: Speed: 2745 MKeys/s, Err: 0, DPs: 1419132K/109142K, Time: 0d:00h:00m/0d:00h:43m
***
MAIN: Speed: 2695 MKeys/s, Err: 0, DPs: 1424111K/109142K, Time: 0d:00h:02m/0d:00h:44m
Stopping work ...
Point solved, K: 0.066 (with DP and GPU overheads)

PRIVATE KEY: 0000000000000000000000000000000000000000000000612E8BA2E8BAC75640

real	4m35,010s
user	1m11,596s
sys	0m45,348s[s][/s]

All that effort for nothing (:  now he’ll show up with that brilliant brain and groundbreaking ideas and say:

“See? It gets found in 2 to 5 minutes, and during that time I can just pay a high fee and make a regular transfer.”

LMAO anyway, I had a lot of fun today.

Yeah, my man Spirik gotcha ya. Probably he’s gonna do that, he’s gonna rely on that time until bot crack it and steal the funds. But wait… he cracked it with a simple hardware, what about a powerful hardware which can do that faster and drop the time to a few seconds? Lmao certainly he’s gonna desapear and go back with a new account or just make up a new argument to not accept how things in our reality works. Just like the people who believes Karl Marx’s theories would actually work out.

[neoman602]

https://github.com/puzzleman22/Bitcoin-Puzzle-Base-Rotator

every thread makes a rotation like:

base 2 is - 101010

base 3 is - 012120
base4 is - 032132

etc... until base 2500


in inside each rotation a transformation is applied


and inside each transformation iteration a shuffle its applied


on top of that all a random is randomizing


like its full chaos on thousands of threads

its like a structured chaos

i dont think an app like this even exists anywhere on github for cuda kernel gpu

never seen

[nomachine]

How do you know the winner is transferring and broadcasting the fund? Do you get the public key immediately after the winner broadcast the transation? Does this take time?

Yes. In about 10-20 seconds you will be left with nothing.

It takes less than 2 seconds to break the private key of Puzzle 71 (once the initial TX is in the mempool), create the TX, and broadcast it, and to get it accepted by any miner.

The principle behind the puzzle bot can be explained more simply:

The bot checks a Bitcoin address for incoming transactions using a Python script.

If a transaction is found, it extracts the public key from the scriptsig field in the transaction input.

Example one-line Python command for puzzle 71:

Code:

python3 -c "import requests; import sys; address = sys.argv[1]; url = f'https://mempool.space/api/address/{address}/txs/chain'; r = requests.get(url); txs = r.json(); pubkey = next((vin['scriptsig'][-66:] for tx in txs for vin in tx['vin'] if 'scriptsig' in vin), None); print(f'Public key for address {address}: {pubkey}' if pubkey else 'Public key not found');" 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU

If the public key is found, it will appear like this:

Public key for address 197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ: 029fd3d2479a37f40d03975cb51ce0fa18cbb709cc46b47caeaa1722cfd3683583

If not, it will return:

Public key not found

You can manually press Enter repeatedly until the public key appears.

Alternatively, you can automate it with a Python script that checks every 5 seconds indefinitely.

The public key will appear as soon as someone broadcasts a transaction from that address.

Faster Execution with a Local Node

If you're running a local Bitcoin node (e.g., with Umbrel), you can query your own mempool instead of an external API:

Code:

url = f'http://mempool.localhost/api/address/{address}/txs/chain'

This reduces latency and speeds up detection.

Once the public key is obtained, Kangaroo is used to derive the private key, typically in 2-3 seconds.

The script then replaces the original transaction in the mempool before it gets confirmed.

Example:

bitcoin-cli createrawtransaction 'INPUTS' 'OUTPUTS'
bitcoin-cli signrawtransactionwithkey 'HEX' '["PRIVATE_KEY"]'
bitcoin-cli sendrawtransaction 'SIGNED_HEX'

No Rate Limits: Local mempool API is faster and unrestricted.

Real-Time Detection: Sees transactions as soon as they enter the mempool.

[Wanderingaran]

In about 10-20 seconds you will be left with nothing.

I just need someone to convince me that this is ethical. So far, no one has been able to prove to me that it’s legal. 

[kTimesG]

In about 10-20 seconds you will be left with nothing.

I just need someone to convince me that this is ethical. So far, no one has been able to prove to me that it’s legal.  

I think you're missing the principles of why Bitcoin exists: obtaining security inside an anonymous but totally insecure environment. There's absolutely nothing secure with using a private key that is known to be insecure. Ethical or legal issues are outside the point here. Also, the stupidity and naivity of using an insecure key in an insecure environment, full of unreliable participants, and yelling left and right "here's the private key, my dear ethical friends which I never met but I completely blindly trust" always has a cost.

Honestly, there is no one who can even prove that puzzles 66 and 69 were solved by them, simply because the TXs that were archived by sites such as mempool.space might have actually received an already replaced TX, from the very beginning. We'll never know.

[Cricktor]

Many paths lead to Rome, as the saying goes.

With an own node, works with a heavily pruned one just fine,  you can set it up to run a script once new transactions arrive or regularly poll also your node's mempool for a transaction which involves any of the puzzle's unsolved addresses. RPC getdescriptoractivity, properly used, might work. Or ZeroMQ stuff... I haven't tried, I'm not a coder, but it's not really rocket science.

Once a vulnerable public key is publicly exposed which can be solved fast enough, stealing bots can and will kick in and start a bidding war with increasing fees because that's how replacement of transactions with unconditional FullRBF works. Do your homework if you don't understand how FullRBF works (for those who phantasize about it's enough to broadcast a tx with just a high fee to succeed).

BTW, worse case shit happens: block 909211 took almost 95 minutes to be mined. If you're unlucky and stupid enough to publicly broadcast e.g. solution for puzzle #71 in such a scenario where the next block takes significantly longer to be mined than the average of about 10min, there's plenty of time for a lot of bots to compete.

Yes, you could be lucky that the next block is mined very few seconds after you broadcasted your transaction publicly and it reached the mining pool's mempools. You could also be very unlucky because mining is unpredictable and finding a valid block hash is a random process.

It's funny how little knowledge some seem to have about Bitcoin's current basic mechanics. Sadly, this thread is full of garbage and nonsense chit-chat.

[Akito S. M. Hosana]

Full RBF turns the mempool into the Hunger Games for puzzle solutions. And yeah, if you broadcast #71’s key during a 95-minute block delay, even my grandma’s toaster could jump in the bidding warassuming it’s running Bitcoin Core 29.0, that is.  

[mahmood1356]

Address: 1GjerJf1FeccCzvQUZVpeVmPpad3RH1ZT5
Public Key: 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc
Range(18hex): 400000000000000000 - 7FFFFFFFFFFFFFFFFF

I have a modest rtx 2060S + GTX1060ti — solution in about 2-5 minutes. For the sake of decency, you could at least put 1 dollar there. 

Code:

~/RCKangaroo$ time ./rckangaroo -dp 16 -range 85 -start 1 -pubkey 03af13c80e78581d870a96f112cf681db1cad6f9da26860f2c25dd9a9125b0bdfc -tames tames85.dat -max 13
********************************************************************************
*                    RCKangaroo v3.0  (c) 2024 RetiredCoder                    *
********************************************************************************

This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 2, CUDA driver/runtime: 12.4/12.0
GPU 0: NVIDIA GeForce RTX 2060 SUPER, 7.78 GB, 34 CUs, cap 7.5, PCI 3, L2 size: 4096 KB
GPU 1: NVIDIA GeForce GTX 1660 Ti, 5.79 GB, 24 CUs, cap 7.5, PCI 8, L2 size: 1536 KB
Total GPUs for work: 2

MAIN MODE

Solving public key
X: AF13C80E78581D870A96F112CF681DB1CAD6F9DA26860F2C25DD9A9125B0BDFC
Y: C9EDCFE647622731DBE2E9E7291E8498BA0AFD44D3356C59B96F630218BDD3FB
Offset: 0000000000000000000000000000000000000000000000000000000000000001

Solving point: Range 85 bits, DP 16, start...
SOTA method, estimated ops: 2^42.702, RAM for DPs: 4.253 GB. DP and GPU overheads not included!
Max allowed number of ops: 2^46.402, max RAM for DPs: 53.044 GB
Estimated DPs per kangaroo: 57.427.
load tames...
tames loaded
GPU 0: allocated 3284 MB, 1114112 kangaroos. OldGpuMode: Yes
GPU 1: allocated 2322 MB, 786432 kangaroos. OldGpuMode: Yes
GPUs started...
MAIN: Speed: 2074 MKeys/s, Err: 0, DPs: 1418283K/109142K, Time: 0d:00h:00m/0d:00h:57m
MAIN: Speed: 2758 MKeys/s, Err: 0, DPs: 1418714K/109142K, Time: 0d:00h:00m/0d:00h:43m
MAIN: Speed: 2745 MKeys/s, Err: 0, DPs: 1419132K/109142K, Time: 0d:00h:00m/0d:00h:43m
***
MAIN: Speed: 2695 MKeys/s, Err: 0, DPs: 1424111K/109142K, Time: 0d:00h:02m/0d:00h:44m
Stopping work ...
Point solved, K: 0.066 (with DP and GPU overheads)

PRIVATE KEY: 0000000000000000000000000000000000000000000000612E8BA2E8BAC75640

real	4m35,010s
user	1m11,596s
sys	0m45,348s[s][/s]

All that effort for nothing (:  now he’ll show up with that brilliant brain and groundbreaking ideas and say:

“See? It gets found in 2 to 5 minutes, and during that time I can just pay a high fee and make a regular transfer.”

LMAO anyway, I had a lot of fun today.

Yeah, my man Spirik gotcha ya. Probably he’s gonna do that, he’s gonna rely on that time until bot crack it and steal the funds. But wait… he cracked it with a simple hardware, what about a powerful hardware which can do that faster and drop the time to a few seconds? Lmao certainly he’s gonna desapear and go back with a new account or just make up a new argument to not accept how things in our reality works. Just like the people who believes Karl Marx’s theories would actually work out.

Hello and thank you for doing this and clarifying the matter. I used to contradict this, but now I fully understand it and I apologize to my friends with whom I disagreed on this issue.