Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Should we now improve it to add EC multiply and SHA256 so that we're EXACTLY in the context you describe ?
Nah, you'd still be biased:
- it's not running in the 69 range; the immutable set is not the same....
- it's not searching for the correct prefix; I mean, birthday paradox......
- it's not finding the key as fast as it finds it once you have a million prefixes known in advance... wrong proximities calculated....
- wrong parameters; they need to be this or that so the results are better
etc...
You have too much free time
You have no idea. I can do this as long as I need to be
Now that we have an tangible base to work with, it's only a matter of time until we reach the empirical truth
Are you sure about that? You'd just read the results wrong, ultimately. At which point your code is so specific, that it needs to go back to the general case. And so on.