View Single Post
Old 2020-04-28, 10:52   #34
kriesel's Avatar
Mar 2017
US midwest

23×577 Posts

Originally Posted by R.D. Silverman View Post
So if two different machines trial divide with two different sets of trial factors how do you know whether a true factor was actually tested??? You might be missing some.
It's my understanding that the leading gpu TF applications use not too few but too many candidate factors. Incomplete sieving of trial factoring candidates is accepted because it is higher performance, without excluding any candidate prime factors. It's faster in practice to sieve the Mersenne number with an occasional composite factor candidate also included, than to perfectly sieve the factor candidates. All the primes of the proper form in 2b to 2b+1 are in the set of trial factors when doing TF from b to b+1, plus a varied set of composites. Assuming the hardware and software are operating to spec, that is, or sufficiently near it.

That's covered in points 8 and 9 of (my attempt to document all the concepts of mfaktc trial factoring I could identify, which had been reviewed by the author of mfaktc)

But suppose one in 106 primes were omitted somehow from the TF candidate factors. We would still get nearly all the benefits of a perfect TF process, with all or nearly all the run time of a perfect TF process, over the same bit size interval.
A usable proof of work algorithm needs to be tolerant of both some level of expected software imperfection and speed optimizations.

Last fiddled with by kriesel on 2020-04-28 at 11:01
kriesel is offline   Reply With Quote