Unverified???...
 

I have recently been assigned M23165671 as a DC.
Checking its status prior to start the run, I found the following:

23165671
No factors below2^67
P-1 B1=330000
Unverified LL82DD4F0E7EA7DD__ by "Travis Rayhons"
Unverified LL82DD4F0E7EA7DD__ by "S235444"

Although it is theoretically possible that only the last bytes differ, I don´t really think that was the case...
Anybody has an idea about what could have caused the server to consider the exponent as unverified?
Has this happen before?

A similar shift could be cause. (For instance the save files were copyed to a new computer and account which then finished and submitted the result.)

Jacob

Identical shift counts. This strongly suggests this is one test by the same user. This was not an uncommon occurrence.

[QUOTE=Prime95;244553]This was not an uncommon occurrence.[/QUOTE]

That statement suggests that attempted fraud is not an uncommon occurrence.

[QUOTE=Mr. P-1;244563]That statement suggests that attempted fraud is not an uncommon occurrence.[/QUOTE]

Perhaps it's not always intentional fraud, but sometimes "I'm switching over from my old numbered v4 account to a new v5 account with a name, and I want some of my old credit (though I'm ignorant of the v4 migration tool), so I'll just resubmit my results!", or some mistake due to copying a Prime95 installation from one computer/user to another, or yes it could be attempted fraud.

[QUOTE=Mini-Geek;244568]Perhaps it's not always intentional fraud, but sometimes "I'm switching over from my old numbered v4 account to a new v5 account with a name, and I want some of my old credit (though I'm ignorant of the v4 migration tool), so I'll just resubmit my results!",[/QUOTE]

That possibility had not occured to me.

[QUOTE]or some mistake due to copying a Prime95 installation from one computer/user to another, or yes it could be attempted fraud.[/QUOTE]

Yeah, I've done that. And manually submitted results that I wasn't sure had been submitted before. But only to the same account.

It was also common for users to change from the v4 assigned userid to a more meaningful one. There were also cases where prime95 forgot your userid and a new Sxxxxxx one was assigned.

Old prime95 versions also used to resend results.txt whenever Test/PrimeNet dialog was used.

In any event, there are lots of non-malicious ways this case could have happened. The good news is the shift count saved us from mistakenly calling the exponent successfully double-checked.

[QUOTE=Prime95;244601] The good news is the shift count saved us from mistakenly calling the exponent successfully double-checked.[/QUOTE]

Yes, definitely!
And I´ll endeavour to provide a valid one in the not-so-distant future :wink:

Done. And verified!... :smile: