Bitcoin puzzle transaction ~32 BTC prize to who solves it

[puzzle-dev]

An update of my "solve66" tool for puzzle #66 is available!

Code:

- improved search options
- bugfixes

WARNING:
- NEVER DOWNLOAD THIS TOOL FROM ANY OTHER SOURCE THAN THE LINK IN MY PROFILE!
- READ README.TXT FIRST BEFORE USING THIS TOOL!

[sssergy2705]

An update of my "solve66" tool for puzzle #66 is available!

Code:

- improved search options
- bugfixes

WARNING:
- NEVER DOWNLOAD THIS TOOL FROM ANY OTHER SOURCE THAN THE LINK IN MY PROFILE!
- READ README.TXT FIRST BEFORE USING THIS TOOL!

Without source code, there is no trust in your application. It is not known what kind of application you are distributing.

[james5000]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

[digaran]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

Cool project, keeping an eye on this one!
Btw what project? 🤣 first show us what you got, then we'll talk about support, in case you haven't noticed, people are here to find money not give it away.😉

[james5000]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

Cool project, keeping an eye on this one!
Btw what project? 🤣 first show us what you got, then we'll talk about support, in case you haven't noticed, people are here to find money not give it away.😉

unfortunately by posting the code people with more knowledge will gain an advantage, so first I'll break down the 66, 67 and 68 puzzle before explaining how it works.

[Ovixx]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

Cool project, keeping an eye on this one!
Btw what project? 🤣 first show us what you got, then we'll talk about support, in case you haven't noticed, people are here to find money not give it away.😉

unfortunately by posting the code people with more knowledge will gain an advantage, so first I'll break down the 66, 67 and 68 puzzle before explaining how it works.

If you manage to solve puzzles 66, 67 and 68, what guarantees would we have that someone would see your code? If you already have the code, why do you want sponsorship? Personally, if I invest in a project, I do it on my own. If I have positive results, I will take my profit from there. So, I just wish you luck and that's it. I can't trust you and I think that most of the members on this forum would have no reason to trust you.

[james5000]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

Cool project, keeping an eye on this one!
Btw what project?  first show us what you got, then we'll talk about support, in case you haven't noticed, people are here to find money not give it away.

unfortunately by posting the code people with more knowledge will gain an advantage, so first I'll break down the 66, 67 and 68 puzzle before explaining how it works.

If you manage to solve puzzles 66, 67 and 68, what guarantees would we have that someone would see your code? If you already have the code, why do you want sponsorship? Personally, if I invest in a project, I do it on my own. If I have positive results, I will take my profit from there. So, I just wish you luck and that's it. I can't trust you and I think that most of the members on this forum would have no reason to trust you.

My code currently runs on the CPU, but we all know that for the next puzzles it needs to be made to run on the GPU, if anyone with CUDA knowledge is interested in splitting 50/50 we can work together.
I guarantee that with a rate of 300 Mk/s we break the 66, 67 and 68 in one week

[james5000]

Just for comparison purposes, I tested it with puzzle 30:

we know the range is 20000000:3fffffff
total of 536,870,911 possible keys

I reduced it to approximately 77,000,000 or -85.66%

based on the same calculations I suppose the 66 is reduced to about 27 trillion keys

[frozenen]

#66 I mean I am interested in your "software" but I don't see how these numbers are possible with just 300Mk/s even if you reduced 86% of #66
Are you able to test on #65 as I think #30 is a bit small?
The range I am searching which I have confidence in but have not shared is less than that at 1342426695300956160 out of 36893488147419107000 keys but even this is like 20 years with 3x RTX3080s so I don't understand how #66, #67 and #68 can be found in 1 week without pub key, could you share more info?

[james5000]

#66 I mean I am interested in your "software" but I don't see how these numbers are possible with just 300Mk/s even if you reduced 86% of #66
Are you able to test on #65 as I think #30 is a bit small?
The range I am searching which I have confidence in but have not shared is less than that at 1342426695300956160 out of 36893488147419107000 keys but even this is like 20 years with 3x RTX3080s so I don't understand how #66, #67 and #68 can be found in 1 week without pub key, could you share more info?

I haven't tested it on 65 because my code is still for the CPU, 65 would take a long time to confirm it works, but on a GPU up to 68 will be possible. 

Well, let's go, in the next post I will explain all the logic, if anyone wants to give support please feel free if it makes sense. 

[brainless]

#66 I mean I am interested in your "software" but I don't see how these numbers are possible with just 300Mk/s even if you reduced 86% of #66
Are you able to test on #65 as I think #30 is a bit small?
The range I am searching which I have confidence in but have not shared is less than that at 1342426695300956160 out of 36893488147419107000 keys but even this is like 20 years with 3x RTX3080s so I don't understand how #66, #67 and #68 can be found in 1 week without pub key, could you share more info?

I haven't tested it on 65 because my code is still for the CPU, 65 would take a long time to confirm it works, but on a GPU up to 68 will be possible. 

Well, let's go, in the next post I will explain all the logic, if anyone wants to give support please feel free if it makes sense. 

Dear friend,  based on developer community, we experience, what in developer mind, only they create for that for gpu, rest just see 1 or 2 pages back lot of basic coder still working on python at CPU level, just see their ideas, script in python back in 1 or 2 pages, albertobsd max created ecctools in c,  even he is good coder for gpu too, but not him or other gpu coder able to create basic ecc tools for gpu, don't take much aspectation for gpu coder community, let world run at python and CPU ,

[digaran]

Just for comparison purposes, I tested it with puzzle 30:

we know the range is 20000000:3fffffff
total of 536,870,911 possible keys

I reduced it to approximately 77,000,000 or -85.66%

based on the same calculations I suppose the 66 is reduced to about 27 trillion keys

Reduced what exactly, addresses? You don't have public key, so reducing whatever you think you reduced is not gonna work. But hey, I wish you are up to something and really hope to find the keys you are looking for.

[james5000]

Just for comparison purposes, I tested it with puzzle 30:

we know the range is 20000000:3fffffff
total of 536,870,911 possible keys

I reduced it to approximately 77,000,000 or -85.66%

based on the same calculations I suppose the 66 is reduced to about 27 trillion keys

Reduced what exactly, addresses? You don't have public key, so reducing whatever you think you reduced is not gonna work. But hey, I wish you are up to something and really hope to find the keys you are looking for.

Yes, I reduced the number of possible addresses.
Thanks, I'll find it.

[vhh]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon.  

support the project:  
1JamesJ2H2myei94NswaBATqEsBhATENSU

Sorry but when you put "brute force" and "coherent logic" in the same sentence , the result will be "incoherent". Brute force is the lack of a algorithm that has a logic; if there is one, then the logic part comes in. For #66 there is no other way of cracking it apart from brute force ! Any reduction technique that you think it will work, it won't,  because all we have is the output of RIPEMD160(SHA256(Public Key)). Unless you broke SHA256 and RIPEMD160 all together and somehow managed to recreate the 256 bits input from a 160 bits output, then this is pointless.  As you could see from other posts, people have tried already all sorts of techniques : statistical analysis regarding keys distribution in a certain range, "magic" relationships between wallet keys (with or without the knowledge of Pub Key), etc.

Try to read more about address generation process. One you've done, move on to the signature generation part where you can read about other interesting potential vulnerabilities like nonce reuse , nonce share , lattices and so on ! You will see how interesting the secp256k1 curve really is !

Start with this : https://www.oreilly.com/library/view/mastering-bitcoin/9781491902639/ch04.html

Cheers!

[ProjectSe7en]

I'm developing brute force software following a slightly more coherent logic, I'll post the code soon. 

support the project: 
1JamesJ2H2myei94NswaBATqEsBhATENSU

Cool project, keeping an eye on this one!
Btw what project?  first show us what you got, then we'll talk about support, in case you haven't noticed, people are here to find money not give it away.

unfortunately by posting the code people with more knowledge will gain an advantage, so first I'll break down the 66, 67 and 68 puzzle before explaining how it works.

If you manage to solve puzzles 66, 67 and 68, what guarantees would we have that someone would see your code? If you already have the code, why do you want sponsorship? Personally, if I invest in a project, I do it on my own. If I have positive results, I will take my profit from there. So, I just wish you luck and that's it. I can't trust you and I think that most of the members on this forum would have no reason to trust you.

My code currently runs on the CPU, but we all know that for the next puzzles it needs to be made to run on the GPU, if anyone with CUDA knowledge is interested in splitting 50/50 we can work together.
I guarantee that with a rate of 300 Mk/s we break the 66, 67 and 68 in one week

for CPU coded in which lang?

How many keys/s do you get with your computer?

[james5000]

for CPU coded in which lang?

How many keys/s do you get with your computer?

python for cpu.
now i have 50.000 key per second on cpu
i finished a first version for gpu and i get 250.000 keys per second for now

[7isce]

python for cpu.
now i have 50.000 key per second on cpu
i finished a first version for gpu and i get 250.000 keys per second for now

Don't waste your time, Keyhunt(CPU) can start with 1,000,000 key/s and you can get 27,000,000 on high end CPU.
BitCrack and KeyHuntCuda can get 1,000,000,000  key/s with mid range GPU.

Just pick up one of them, or you can change the code as you wash(its open source at the end)

[albert0bsd]

... and you can get 27,000,000 on high end CPU.

Actually some more than 100 Million keys/s    

By the way my fists test also start with some 50 Thousand keys/s

i finished a first version for gpu and i get 250.000 keys per second for now

Please don't start a code for GPU when you don't even reach the max limit for CPU, a shitty code in CPU will only lead a shitty code on GPU.

[james5000]

... and you can get 27,000,000 on high end CPU.

Actually some more than 100 Million keys/s    

By the way my fists test also start with some 50 Thousand keys/s

i finished a first version for gpu and i get 250.000 keys per second for now

Please don't start a code for GPU when you don't even reach the max limit for CPU, a shitty code in CPU will only lead a shitty code on GPU.

do you want work together?

[albert0bsd]

with 1Mk/s i have a key off 66 puzzle in max 10 days
with 300Mk/s i have a key in 10 hours
if albertobsd want work with me, we can make a call and divide 50/50 the 66, 67 and 68, maybe more

I think that your calculations are some wrong, what formula do you use?
According to my research with 1 Million keys/s the puzzle 66 can take up to 1 million 169 thousand years.

Code:

>>> 2**65/1000000/60/60/24/365
1169884.834710144

do you want work together?

Yes of course.

Eu falo um pouco de portugês.

I only develop in C and C++