- Joined
- Aug 7, 2021
This sounds like it would work well for creating a progress bar. IIUC, there are ways to prevent parallelization. One would be to provide the next challenge only after the previous one is solved, but that involves back-and-forth. Another would be that the solution is an input to the next challenge. E.g., if the challenges are to find a, b, then the browser is provided hash(a), hash(b) xor a. I don't think there's a way to beat that with multiple cores.That would involve tracking solve times over a large enough data set. If I'm going to do that I might as well reduce difficulty to 2^16 (factor of 16 times easier) and then have them solve it 16 times. it is effectively the same thing, though it would benefit multiple cores and potentially attackers.
Last edited:




