M332193019 has a factor: 245547253556010982337. Found with mfactor.

[QUOTE=gribozavr]M332193019 has a factor: 245547253556010982337. Found with mfactor.[/QUOTE]

Site updated.
Congratulations on your find gribozavr! :bow:

Thanks, Omboo! There are some more factors:
M332193149 has a factor: 377447611643870659897. Found with mfactor.
M332193149 has a factor: 1229637305950589655937. Found with mfactor.
:banana:

[QUOTE=gribozavr]M332193149 has a factor: 377447611643870659897.
M332193149 has a factor: 1229637305950589655937.[/QUOTE]
That's a juicy pair, Dmitri!

M332193233 from 64 to 71 bits with mfactor. No factors found.

M332193109 from 67 to 70 bits with mfactor. No factors found.

M332192969 from 70 to 71 bits with mfactor. No factors found. 1193 minutes.
M332193859 from 64 to 65 bits with mfactor. No factors found. 25 minutes.


I wonder, is there some "goal" bit depth? What maximum bit depth makes sense for 100MDPP?

M332193469 has a factor: 62406675324149338327. Found with mfactor.

One more factor:
M332193529 has a factor: 1002359989482492383441. Found with mfactor.
:banana:

[QUOTE=gribozavr]One more factor:
M332193529 has a factor: 1002359989482492383441. Found with mfactor.
:banana:[/QUOTE]

Gribozavr's on a row! I'll release my exponent on 64 bits, feel free to find a factor for it!

Wow...

[QUOTE=gribozavr]
I wonder, is there some "goal" bit depth? What maximum bit depth makes sense for 100MDPP?[/QUOTE]

I don't think I'm the one to ask... :unsure: . It was because the project seemed dead that I took it over. I have a bit of knowledge about what this project is regarding (remove as many candidates as possible) but I don't know where to stop.

We could keep going until we find a factor (or waste a bunch of CPU cycles on a prime)
Or we could do as OBD and say that we run 'X' candidates to 'Z' bits.

What do you people want? :whistle: