Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Arkd]

hello everyone, newbie here

is there an option on the Cyclone(Nomachine or Dookoo) to run sequentially with 2 workers in this example where

Worker A Scans Key 0
Worker B Scans Key 0 + 1
Worker A Scans Key 0 + 2
Worker B Scans Key 0 + 3
and so on

instead of dividing all the range in N parts as thread inputs
to keep a better track of the progress
i think bitcrack does that with gpu
thanks

[nomachine]

The best option is to compile each application yourself, including the entire (Linux) system from scratch. 

Then, are you 100% safe from hacker attacks and surveillance by the deep state?   

Actually, no. If you have an Intel motherboard and processor, it’s necessary to clean the BIOS of the Intel ME engine using me_cleaner.

https://legends2k.github.io/note/clean_me/

And you should live in a Faraday cage—offline—preferably in a cave.  

[Akito S. M. Hosana]

The best option is to compile each application yourself, including the entire (Linux) system from scratch. 

Then, are you 100% safe from hacker attacks and surveillance by the deep state?   

Actually, no. If you have an Intel motherboard and processor, it’s necessary to clean the BIOS of the Intel ME engine using me_cleaner.

https://legends2k.github.io/note/clean_me/

And you should live in a Faraday cage—offline—preferably in a cave.  

Holy... I didn’t even know this existed. What do you do if the BIOS is encrypted and can’t be changed?

[Bram24732]

After so much debate, I have concluded that @Bram and @Ktimesg were right; prefix search does not offer a statistically significant improvement.

https://bitcointalk.org/index.php?topic=5539190

Thanks for editing the original post with the conclusion.
Also, it takes a lot to change one’s mind, so kudos to you for doing so.

[nomachine]

Holy... I didn’t even know this existed. What do you do if the BIOS is encrypted and can’t be changed?

To use the USB programmer and program the BIOS chip, first unsolder it with a hot air soldering gun. 

[Akito S. M. Hosana]

Holy... I didn’t even know this existed. What do you do if the BIOS is encrypted and can’t be changed?

To use the USB programmer and program the BIOS chip, first unsolder it with a hot air soldering gun. 

Are you Joe, aka the Kingpin?   

[nomachine]

Holy... I didn’t even know this existed. What do you do if the BIOS is encrypted and can’t be changed?

To use the USB programmer and program the BIOS chip, first unsolder it with a hot air soldering gun. 

Are you Joe, aka the Kingpin?   

No, he lives in another state, but I know him. 

[kTimesG]

hello everyone, newbie here

is there an option on the Cyclone(Nomachine or Dookoo) to run sequentially with 2 workers in this example where

Worker A Scans Key 0
Worker B Scans Key 0 + 1
Worker A Scans Key 0 + 2
Worker B Scans Key 0 + 3
and so on

instead of dividing all the range in N parts as thread inputs
to keep a better track of the progress
i think bitcrack does that with gpu
thanks

You have the same exact track of the progress no matter where the scanned keys were located. Your example is hard to implement because the worker keys don't advance by one, they advance by numWorkers. However, it doesn't make it impossible, just more complicated, with no real benefits. At a large scale, it doesn't even matter in what way the workers scanned, as long as the entire subrange completes, and you can then move to the next subrange (or some other unscanned one - totally personal preference with no impact on anything).

You can stop and resume equally divided worker ranges just as well.

[2008TOKi]

After so much debate, I have concluded that @Bram and @Ktimesg were right; prefix search does not offer a statistically significant improvement.

https://bitcointalk.org/index.php?topic=5539190

Thanks for editing the original post with the conclusion.
Also, it takes a lot to change one’s mind, so kudos to you for doing so.

is the competition you mentioned still active?  
I’ve found a method that reduces the 2⁷⁰ search space of Puzzle 71 by approximately 7.22%, without using any prefixes or hash tricks. I've tested it in Python.  
I just hope the competition is still ongoing and the reward is valid. Once I wrap up some other work, I’ll share the method.
We use this mathematical method to determine how much new genetic mutations vary and which probability distribution they fall into.

[zahid888]

the key was found after 0.7206% of the range.

So someone solved puzzle 69 using a modified Cyclone in 20 days?  

Hi all! Modified version with jumps and partial match: https://github.com/Dookoo2/Cyclone
Try your luck:)

With a small tweak 😉. I'm still a bit confused about how the jump function works, so I avoided using it. Interestingly, it seems to take the same amount of time with or without it.

[POD5]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

[nomachine]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags. 

[fantom06]

the key was found after 0.7206% of the range.

So someone solved puzzle 69 using a modified Cyclone in 20 days?  

Hi all! Modified version with jumps and partial match: https://github.com/Dookoo2/Cyclone
Try your luck:)

With a small tweak 😉. I'm still a bit confused about how the jump function works, so I avoided using it. Interestingly, it seems to take the same amount of time with or without it.

Where did you Cyclone dig up this?

[POD5]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags. 

It is nice to see, how many good minded people are creating interesting code.
I've been using Cyclone with range file. Perhaps one day.

[Akito S. M. Hosana]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags. 

================= WORK IN PROGRESS =================
Puzzle/Bits   : 71
Target Hash160: f6f5431d25bbf7b...5e3475c44a0a5b8
Prefix length : 8 bytes
Mode          : Random
CPU Threads   : 12
Mkeys/s       : 42.91
Total Checked : 1661029376
Elapsed Time  : 00:00:45
Start Range   : 400000000000000000
End Range     : 7fffffffffffffffff
Progress      : N/A
Progress Save : 0
Stride        : 1

Previously, it was 34–35 Mkeys/s.

[fantom06]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags. 

================= WORK IN PROGRESS =================
Puzzle/Bits   : 71
Target Hash160: f6f5431d25bbf7b...5e3475c44a0a5b8
Prefix length : 8 bytes
Mode          : Random
CPU Threads   : 12
Mkeys/s       : 42.91
Total Checked : 1661029376
Elapsed Time  : 00:00:45
Start Range   : 400000000000000000
End Range     : 7fffffffffffffffff
Progress      : N/A
Progress Save : 0
Stride        : 1

Previously, it was 34–35 Mkeys/s.

Dookoo2/Cyclone.exe DON'T WORK random!!!
Progress Save #14 at 4200.02 sec: TotalChecked=165648870912, ElapsedTime=01:09:56, Mkeys/s=39.47
Thread Key 0: 00000000000000000000000000000000000000000000004000000000ED06BF4C
Thread Key 1: 000000000000000000000000000000000000000000000041C71C71C84FB74D1D
Thread Key 2: 0000000000000000000000000000000000000000000000438E38E38F4C82E82C
Thread Key 3: 000000000000000000000000000000000000000000000045555555566746FCAB
Thread Key 4: 0000000000000000000000000000000000000000000000471C71C71D83FF9AAA
Thread Key 5: 000000000000000000000000000000000000000000000048E38E38E4A19A7F7F
Thread Key 6: 00000000000000000000000000000000000000000000004AAAAAAAABC571EB8A
Thread Key 7: 00000000000000000000000000000000000000000000004C71C71C72E1BEE19D
Thread Key 8: 00000000000000000000000000000000000000000000004E38E38E39FCD2CDF4
Thread Key 9: 00000000000000000000000000000000000000000000005000000001180AFBE5
Thread Key 10: 000000000000000000000000000000000000000000000051C71C71C831899D1E
Thread Key 11: 0000000000000000000000000000000000000000000000538E38E38F4C811407
Thread Key 12: 000000000000000000000000000000000000000000000055555555566AB7C870
Thread Key 13: 0000000000000000000000000000000000000000000000571C71C71D87F356FB
Thread Key 14: 000000000000000000000000000000000000000000000058E38E38E49C52A4AC
Thread Key 15: 00000000000000000000000000000000000000000000005AAAAAAAABB81BE4F9
Thread Key 16: 00000000000000000000000000000000000000000000005C71C71C72B2F23946
Thread Key 17: 00000000000000000000000000000000000000000000005E38E38E39D115A50A
Thread Key 18: 0000000000000000000000000000000000000000000000600000000134385842
Thread Key 19: 000000000000000000000000000000000000000000000061C71C71C84EE355F0
Thread Key 20: 0000000000000000000000000000000000000000000000638E38E38F4C38D490
Thread Key 21: 0000000000000000000000000000000000000000000000655555555667E224EC
Thread Key 22: 0000000000000000000000000000000000000000000000671C71C71D823EFD0E
Thread Key 23: 000000000000000000000000000000000000000000000068E38E38E4A1425FFA
Thread Key 24: 00000000000000000000000000000000000000000000006AAAAAAAABC5224582
Thread Key 25: 00000000000000000000000000000000000000000000006C71C71C72E20053EA
Thread Key 26: 00000000000000000000000000000000000000000000006E38E38E39FB295D10
Thread Key 27: 00000000000000000000000000000000000000000000007000000001197A72FC
Thread Key 28: 000000000000000000000000000000000000000000000071C71C71C8328DD3E0
Thread Key 29: 0000000000000000000000000000000000000000000000738E38E38F4E4C8CBE
Thread Key 30: 0000000000000000000000000000000000000000000000755555555669FBD51C
Thread Key 31: 0000000000000000000000000000000000000000000000771C71C71D886EF6DA
Thread Key 32: 000000000000000000000000000000000000000000000078E38E38E49B721E0E
Thread Key 33: 00000000000000000000000000000000000000000000007AAAAAAAABB6BD38FE
Thread Key 34: 00000000000000000000000000000000000000000000007C71C71C72B10BA1BE
Thread Key 35: 00000000000000000000000000000000000000000000007E38E38E39C9A0A182

[hoanghuy2912]

The puzzles were solved faster and faster and consistently for 1 to 2 months, making me doubt the transparency.

[Denevron]

Hey guys, there is a new Cyclone on the block

Still working hard, hu?  
Some new interesting features?

Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags. 

================= WORK IN PROGRESS =================
Puzzle/Bits   : 71
Target Hash160: f6f5431d25bbf7b...5e3475c44a0a5b8
Prefix length : 8 bytes
Mode          : Random
CPU Threads   : 12
Mkeys/s       : 42.91
Total Checked : 1661029376
Elapsed Time  : 00:00:45
Start Range   : 400000000000000000
End Range     : 7fffffffffffffffff
Progress      : N/A
Progress Save : 0
Stride        : 1

Previously, it was 34–35 Mkeys/s.

Dookoo2/Cyclone.exe DON'T WORK random!!!
Progress Save #14 at 4200.02 sec: TotalChecked=165648870912, ElapsedTime=01:09:56, Mkeys/s=39.47
Thread Key 0: 00000000000000000000000000000000000000000000004000000000ED06BF4C
Thread Key 1: 000000000000000000000000000000000000000000000041C71C71C84FB74D1D
Thread Key 2: 0000000000000000000000000000000000000000000000438E38E38F4C82E82C
Thread Key 3: 000000000000000000000000000000000000000000000045555555566746FCAB
Thread Key 4: 0000000000000000000000000000000000000000000000471C71C71D83FF9AAA
Thread Key 5: 000000000000000000000000000000000000000000000048E38E38E4A19A7F7F
Thread Key 6: 00000000000000000000000000000000000000000000004AAAAAAAABC571EB8A
Thread Key 7: 00000000000000000000000000000000000000000000004C71C71C72E1BEE19D
Thread Key 8: 00000000000000000000000000000000000000000000004E38E38E39FCD2CDF4
Thread Key 9: 00000000000000000000000000000000000000000000005000000001180AFBE5
Thread Key 10: 000000000000000000000000000000000000000000000051C71C71C831899D1E
Thread Key 11: 0000000000000000000000000000000000000000000000538E38E38F4C811407
Thread Key 12: 000000000000000000000000000000000000000000000055555555566AB7C870
Thread Key 13: 0000000000000000000000000000000000000000000000571C71C71D87F356FB
Thread Key 14: 000000000000000000000000000000000000000000000058E38E38E49C52A4AC
Thread Key 15: 00000000000000000000000000000000000000000000005AAAAAAAABB81BE4F9
Thread Key 16: 00000000000000000000000000000000000000000000005C71C71C72B2F23946
Thread Key 17: 00000000000000000000000000000000000000000000005E38E38E39D115A50A
Thread Key 18: 0000000000000000000000000000000000000000000000600000000134385842
Thread Key 19: 000000000000000000000000000000000000000000000061C71C71C84EE355F0
Thread Key 20: 0000000000000000000000000000000000000000000000638E38E38F4C38D490
Thread Key 21: 0000000000000000000000000000000000000000000000655555555667E224EC
Thread Key 22: 0000000000000000000000000000000000000000000000671C71C71D823EFD0E
Thread Key 23: 000000000000000000000000000000000000000000000068E38E38E4A1425FFA
Thread Key 24: 00000000000000000000000000000000000000000000006AAAAAAAABC5224582
Thread Key 25: 00000000000000000000000000000000000000000000006C71C71C72E20053EA
Thread Key 26: 00000000000000000000000000000000000000000000006E38E38E39FB295D10
Thread Key 27: 00000000000000000000000000000000000000000000007000000001197A72FC
Thread Key 28: 000000000000000000000000000000000000000000000071C71C71C8328DD3E0
Thread Key 29: 0000000000000000000000000000000000000000000000738E38E38F4E4C8CBE
Thread Key 30: 0000000000000000000000000000000000000000000000755555555669FBD51C
Thread Key 31: 0000000000000000000000000000000000000000000000771C71C71D886EF6DA
Thread Key 32: 000000000000000000000000000000000000000000000078E38E38E49B721E0E
Thread Key 33: 00000000000000000000000000000000000000000000007AAAAAAAABB6BD38FE
Thread Key 34: 00000000000000000000000000000000000000000000007C71C71C72B10BA1BE
Thread Key 35: 00000000000000000000000000000000000000000000007E38E38E39C9A0A182

You can fix the random mode yourself as you need, and then just compile the program into .exe) but it is better to use at least wsl 

[nxtime]

I have some great ideas, but my only problem is converting the private key to hash160 using CUDA. I have various algorithms in mind. Can someone explain to me how to convert a private key to hash160 using CUDA?

[nochkin]

I have some great ideas, but my only problem is converting the private key to hash160 using CUDA. I have various algorithms in mind. Can someone explain to me how to convert a private key to hash160 using CUDA?

All brute-forcing programs do it already. Hash160 is the same as the address, just a different representation of it.