Next scheduled rescrape ... never
Version 1
Last scraped
Edited on 27/09/2025, 16:07:47 UTC

An update to CUDACyclone that generates non-repeating, persistent random subranges.
Ideal for collaborative search.

./CUDACyclone \                                                                                                                                                  
              --range 400000000000000000:7fffffffffffffffff \
              --address 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU \
              --random-subranges --num-subranges 10000000 --grid 256,8

Would it not be faster if you target Hash 160 of the Address instead of the BTC Address. i.e. cut down on calculating Address from PK which is not needed.


Internally, the comparison is made against hash160().
The address is displayed in the interface for convenience only.




An update to CUDACyclone that generates non-repeating, persistent random subranges.
Ideal for collaborative search.

./CUDACyclone \                                                                                                                                                
              --range 400000000000000000:7fffffffffffffffff \
              --address 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU \
              --random-subranges --num-subranges 10000000 --grid 256,8
Hello man, update your software. Previous version of a Cyclone has a bug. I did a mistake with a first batch of the thread, not right computing center point of the first batch, and than the last batch finish not in the end of the range. Last half batch of points from the end of the each thread doesnt computing!


Specifically, which version are you referring to?
Original archived Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Scraped on 20/09/2025, 16:07:15 UTC

An update to CUDACyclone that generates non-repeating, persistent random subranges.
Ideal for collaborative search.

./CUDACyclone \                                                                                                                                                 
              --range 400000000000000000:7fffffffffffffffff \
              --address 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU \
              --random-subranges --num-subranges 10000000 --grid 256,8

Would it not be faster if you target Hash 160 of the Address instead of the BTC Address. i.e. cut down on calculating Address from PK which is not needed.


Internally, the comparison is made against hash160().
The address is displayed in the interface for convenience only.