What we can say with respect to these two posts:
Between 20 and 250 there were 50 - 0 = 50 bounties found.
We call them trophies. There were these
https://lbc.cryptoguru.org/trophies found.
Somewhere between 250 and 251 there is at least one bounty.
Somewhere between 251 and 252 there is at least one bounty.
Etc.
Where the probability of having more than one bounty doubles with each of these spaces.
If every single private key between 20 and 250 was not tried then there is a (small) possibility that you might have missed another bounty.
We will try every single key. Every single key between 0 and 2
49.35 was tried. We will now try every single key from 2
50 on and after #51 is found, then finish the work 2
49.35 to 2
50. If it's there, we will miss nothing.
So, once you find one bounty in a search space (250 ... 251 for example) you really should search the entire remaining space to see if there is a second (aliased) larger bounty!
Sure. That's the normal mode of operation. That's how we found e.g. f6cc30532dba44efe592733887f4f74c589c9602
In general, we seem to find uncompressed addresses with funds that pre-date the pool inception.
However if you happen to find the expected bounty and then skip to the next range there is a chance you will miss a larger bounty in the remainder of the range.
We know. We perform an exhaustive search. It's just for this specific #51 we skipped around 370 tn keys, because it has funds and it would be nice if the LBC finds it before someone else does. Then we return to our normal mode of operation.
Rico
