Bitcoin puzzle transaction ~32 BTC prize to who solves it

[kTimesG]

Relax, buddy. It's OK if you don't understand how a tool you've downloaded from GitHub works.

Also, probably by this summer I'll publish my DLP solver, written from scratch in C and CUDA, and some huge improvements, both algorithmical and technical optimizations (e.g. much higher speeds, AND a lower overall complexity then RCKang SOTA), so I'm not really bothered that you're using some basic proof of concept stripped off from an optimized cracking tool, which you fail to grasp how it works, to attempt solving a 134-bits DLP.

I'm also sure I have more 32-bit DPs gathered so far then your entire idiots pool "checkpoints", times 100.

RetiredCoder also introduced many innovations, added a second type of wild herds, and therefore adapted the private key computation for the case of a collision between two wild herds. He also adapted the detection approach, the exit from cycles, and many other aspects.

I posted the 3-type collision formulas 4 months before RCKang was ever a thing.

Also the 3-types algorithm already existed in literature.

Since then, I decided to keep the other several things which I'm using as optimizations to myself, though I posted a SHA256 hash of some important things no one has ever noticed or used in practice, so history will make justice in the future...

[Torin Keepler]

Relax, buddy. It's OK if you don't understand how a tool you've downloaded from GitHub works.

Also, probably by this summer I'll publish my DLP solver, written from scratch in C and CUDA, and some huge improvements, both algorithmical and technical optimizations (e.g. much higher speeds, AND a lower overall complexity then RCKang SOTA), so I'm not really bothered that you're using some basic proof of concept stripped off from an optimized cracking tool, which you fail to grasp how it works, to attempt solving a 134-bits DLP.

I'm also sure I have more 32-bit DPs gathered so far then your entire idiots pool "checkpoints", times 100.

RetiredCoder also introduced many innovations, added a second type of wild herds, and therefore adapted the private key computation for the case of a collision between two wild herds. He also adapted the detection approach, the exit from cycles, and many other aspects.

I posted the 3-type collision formulas 4 months before RCKang was ever a thing.

Also the 3-types algorithm already existed in literature.

Since then, I decided to keep the other several things which I'm using as optimizations to myself, though I posted a SHA256 hash of some important things no one has ever noticed or used in practice, so history will make justice in the future...

When I pointed you directly to the link where the program developer clearly states that he uses the kangaroo algorithmic method, instead of simply admitting that you were wrong, you jumped to another topic, talking about how great you are and how you are supposedly about to write a program better than the one written by RC.
First write it, release it, or better yet, solve the puzzle, and only after that praise yourself for how great you are.

In my eyes, you are a foolish loudmouth who cannot admit being wrong because your inflated ego has been hurt. And you have no choice but to start praising yourself.

You are completely clear to me, and I have lost interest in continuing this conversation.

[kTimesG]

When I pointed you directly to the link where the program developer clearly states that he uses the kangaroo algorithmic method, instead of simply admitting that you were wrong

1. Take your anxiety pills.
2. I'm not wrong, RCKang doesn't use the kangaroo method. In what language do you need translation, so this information actually dissolves into your brain?

You're spreading around non-sense, that is my only concern. If you can't handle the actual theory behind some GitHub repo, at least STFU and go back to your Python file scanner. RetiredCoder simply used an inappropriate name for his PoC, deal with it, instead of fighting an useless false argument. Read the dozens of papers, maybe.

I'm done with this topic.

[Bram24732]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

[Torin Keepler]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

[Bram24732]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

[Torin Keepler]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

[analyticnomad]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I look forward to the day people don't double down on being wrong and just say "fuck, I might be wrong this time, and thats okay".

You have the most two reputable on here telling you whats what. Man the fuck up.

[Torin Keepler]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I look forward to the day people don't double down on being wrong and just say "fuck, I might be wrong this time, and thats okay".

You have the most two reputable on here telling you whats what. Man the fuck up.

It is a logical error to rely on authority rather than conduct your own analysis.
Moreover, someone who may appear to be an authority to one person may not be considered one by others.

[analyticnomad]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I look forward to the day people don't double down on being wrong and just say "fuck, I might be wrong this time, and thats okay".

You have the most two reputable on here telling you whats what. Man the fuck up.

It is a logical error to rely on authority rather than conduct your own analysis.
Moreover, someone who may appear to be an authority to one person may not be considered one by others.

The irony of this comment isn't lost on me.

[snaz3d]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

Are you sure / certain that that's what he used to reach the key(s)? That software was released way after the latest key (130) was found and even now it has its flaws not even to mention how would it have worked on 400 GPUs he claims to have used to get it.

[Torin Keepler]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

Are you sure / certain that that's what he used to reach the key(s)? That software was released way after the latest key (130) was found and even now it has its flaws not even to mention how would it have worked on 400 GPUs he claims to have used to get it.

In one of his posts, he wrote that he used his own version of the program to solve the puzzle.
He also stated that he is currently using a more efficient version of the program. Therefore,
which specific version of the program was used to find the 130th puzzle is known only to him.
However, one thing can be stated with certainty: his program is indeed very fast.
I tested it on various ranges. In particular, in the latest test, a test private key was found within a 115-bit range.

Whether to believe this developer or not is something everyone must decide for themselves.

[snaz3d]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

Are you sure / certain that that's what he used to reach the key(s)? That software was released way after the latest key (130) was found and even now it has its flaws not even to mention how would it have worked on 400 GPUs he claims to have used to get it.

In one of his posts, he wrote that he used his own version of the program to solve the puzzle.
He also stated that he is currently using a more efficient version of the program. Therefore,
which specific version of the program was used to find the 130th puzzle is known only to him.
However, one thing can be stated with certainty: his program is indeed very fast.
I tested it on various ranges. In particular, in the latest test, a test private key was found within a 115-bit range.

Whether to believe this developer or not is something everyone must decide for themselves.

What GPU did you use for a 115bit range? And how long did it take?

[Torin Keepler]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

Are you sure / certain that that's what he used to reach the key(s)? That software was released way after the latest key (130) was found and even now it has its flaws not even to mention how would it have worked on 400 GPUs he claims to have used to get it.

In one of his posts, he wrote that he used his own version of the program to solve the puzzle.
He also stated that he is currently using a more efficient version of the program. Therefore,
which specific version of the program was used to find the 130th puzzle is known only to him.
However, one thing can be stated with certainty: his program is indeed very fast.
I tested it on various ranges. In particular, in the latest test, a test private key was found within a 115-bit range.

Whether to believe this developer or not is something everyone must decide for themselves.

What GPU did you use for a 115bit range? And how long did it take?

The 115-bit range was solved as part of a challenge. The address was funded with $200, and some participants redirected their computing power from the 135th puzzle to this challenge. In the end, it took us about 30 days to find the key.

The idea is that everyone searches locally on their own computer, while the work done is not lost, since all discovered checkpoints are saved to a file. Because the kangaroo algorithm does not store all points but only checkpoints, the size of such a file is relatively small. Once a day, all participants shared their files in a public location. At some point, while analyzing this database, we were able to compute the private key.

Another important feature is that if you find the private key locally, there is no need to share any files, since you already have the private key in your possession.
Roughly speaking, saving data to a file and exchanging these files between participants is an optional feature of the program.

This approach provides very good scalability.

https://t.me/puzzle135

[snaz3d]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I don’t care about semantics. They could be Koalas for all I care.
What matters is that your project is scammy, whatever the name of the algorithm.

RetiredCoder wrote the program, proved its effectiveness in practice, earned more than one million dollars, released one of its versions to the public, and clearly described how it works and which algorithms were used. And your argument is that you do not care. Keep going in the same spirit, do not deny yourself anything.

Are you sure / certain that that's what he used to reach the key(s)? That software was released way after the latest key (130) was found and even now it has its flaws not even to mention how would it have worked on 400 GPUs he claims to have used to get it.

In one of his posts, he wrote that he used his own version of the program to solve the puzzle.
He also stated that he is currently using a more efficient version of the program. Therefore,
which specific version of the program was used to find the 130th puzzle is known only to him.
However, one thing can be stated with certainty: his program is indeed very fast.
I tested it on various ranges. In particular, in the latest test, a test private key was found within a 115-bit range.

Whether to believe this developer or not is something everyone must decide for themselves.

What GPU did you use for a 115bit range? And how long did it take?

The 115-bit range was solved as part of a challenge. The address was funded with $200, and some participants redirected their computing power from the 135th puzzle to this challenge. In the end, it took us about 30 days to find the key.

The idea is that everyone searches locally on their own computer, while the work done is not lost, since all discovered checkpoints are saved to a file. Because the kangaroo algorithm does not store all points but only checkpoints, the size of such a file is relatively small. Once a day, all participants shared their files in a public location. At some point, while analyzing this database, we were able to compute the private key.

Another important feature is that if you find the private key locally, there is no need to share any files, since you already have the private key in your possession.
Roughly speaking, saving data to a file and exchanging these files between participants is an optional feature of the program.

This approach provides very good scalability.

https://t.me/puzzle135

Aha... Ok, good luck!

[Bram24732]

In my eyes, you are a foolish loudmouth

kTimesG is one of the only ones who knows his shit around here.
He calls you out on your BS, just deal with it. But please do so silently.

I am sending you a link to the GitHub repository of the developer RetiredCoder, where in the very first paragraph of the description he explicitly states that this is an efficient implementation of a program using the Kangaroo algorithmic method.
https://github.com/RetiredC/RCKangaroo

Here is the quote itself:

"(c) 2024, RetiredCoder (RC)
RCKangaroo is free and open source GPLv3. This software demonstrates efficient GPU implementation of SOTA Kangaroo method for solving ECDLP. It is part 3 of my research, you can find more details here: https://github.com/RetiredC
"

I look forward to the day people don't double down on being wrong and just say "fuck, I might be wrong this time, and thats okay".

You have the most two reputable on here telling you whats what. Man the fuck up.

It is a logical error to rely on authority rather than conduct your own analysis.
Moreover, someone who may appear to be an authority to one person may not be considered one by others.

Haha this dude might almost make me start the work on 135 just to prove him wrong 🤣

[whistle307194]

Is there any tool that can precisely calculate/estimate how many addresses we can expect in a given hex priv key range while prefix search?

[WanderingPhilospher]

Relax, buddy. It's OK if you don't understand how a tool you've downloaded from GitHub works.

Also, probably by this summer I'll publish my DLP solver, written from scratch in C and CUDA, and some huge improvements, both algorithmical and technical optimizations (e.g. much higher speeds, AND a lower overall complexity then RCKang SOTA), so I'm not really bothered that you're using some basic proof of concept stripped off from an optimized cracking tool, which you fail to grasp how it works, to attempt solving a 134-bits DLP.

I'm also sure I have more 32-bit DPs gathered so far then your entire idiots pool "checkpoints", times 100.

RetiredCoder also introduced many innovations, added a second type of wild herds, and therefore adapted the private key computation for the case of a collision between two wild herds. He also adapted the detection approach, the exit from cycles, and many other aspects.

I posted the 3-type collision formulas 4 months before RCKang was ever a thing.

Also the 3-types algorithm already existed in literature.

Since then, I decided to keep the other several things which I'm using as optimizations to myself, though I posted a SHA256 hash of some important things no one has ever noticed or used in practice, so history will make justice in the future...

Where do your 32-bit DPs lie, leading, trailing or in the middle?

[GnSekhar]

can you suggest what to use for=

[fecell]

Private key of 71 is

6*****************

It's absurd.
PK is a binary 0/1 value.