Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I do not use the "--stride" function for several reasons:
1) it is possible to not find the right key (already using '2' as a value)
2) is meaningless without any premises as to whether the key is even or not
Any (no) benefit I could achieve - a comparable example I could run half of the whole range without using this function anyway) not knowing if I'm scanning the right half :-)
I use the "--share" function for this, thanks to which I have scripts that start divided into X parts (read internal ranges).
For each space I determine X individually (based on my own whim) and based only on my mood or the weather. My whim of X's arrangements for space 63 resulted in the fact that the last set scanned the space from the value of 'Y', which was lower than the proper key, respectively, so that I needed three days to reach the key. I can not say the same about the '62' range, which did not show the right key despite the fact that all readings are already at the level BELOW of the month until the end of the full scan.
Prejuding the questions:
1. I will NOT betray 'X' I have set.
2. Yes ... I am also scanning the range 64
So looks like you've got a key for #64 just by luck... or may be it was a good weather at that time. 1) it is possible to not find the right key (already using '2' as a value)
2) is meaningless without any premises as to whether the key is even or not
Any (no) benefit I could achieve - a comparable example I could run half of the whole range without using this function anyway) not knowing if I'm scanning the right half :-)
I use the "--share" function for this, thanks to which I have scripts that start divided into X parts (read internal ranges).
For each space I determine X individually (based on my own whim) and based only on my mood or the weather. My whim of X's arrangements for space 63 resulted in the fact that the last set scanned the space from the value of 'Y', which was lower than the proper key, respectively, so that I needed three days to reach the key. I can not say the same about the '62' range, which did not show the right key despite the fact that all readings are already at the level BELOW of the month until the end of the full scan.
Prejuding the questions:
1. I will NOT betray 'X' I have set.
2. Yes ... I am also scanning the range 64
