Rob, I'm not sure how far along you've gotten with the validation but I think the best way to do this is to have our own Rosetta manager. I know your aware that there are many task managers out there and they all call out the Rosetta client to do the computational work. From there, you can tie in a piece of code that tells Bible pay that the client is actually running and keep track of the tasks run. From our own manager, you can then also send out the performance data for validation use.
That is what I've come up with after thinking about it through out the day. Then, the only piece left that is not currently in our control is the Rosetta and Rosetta mini clients.
Possibly. I think I can actually scrape all that intercommunication between rosetta and boinc anyway (using the opensource boinc protocol), but I was thinking of that part of it, and whether we trust that log or trust our auditor - Im wondering if we start by assigning an auditor, thats you, we create some web reports (thinks like task turnaround speed per machine, ghz & cores per machine, with some metrics) and make the auditors record the "reference machine"for biblepay. You can read your row and "certify"it (thats our scale).
Then I base the integrity value on other rolled up users values vs. the auditors. Then we look at it and try to figure ways to improve it - and try to figure out how "weak"it actually is.