As many have pointed out, the anonymous platform mechanism is not safe. Also, increasing the min quorum to 2 or more would require a new validator, so that is not optimal.

Since the goal here is to test the new app version, I am leaning towards deploying Alperen's new binaries using the new test app that I created earlier. I can dump 1000 or more tasks from an older data set whose results can be used as truth.

But I will wait for feedback before I go down this path.

It would be the best option IMHO- the least amount of work required on your part, but will still result in a valid check of the new application's accuracy without having any impact on the science database.


You'll need to determine how to differentiate the results provided by the current stock applications and the new application being used to process the test Tasks, as they will be handled by the present Validator and Assimilators, but you don't want them to be assimilated into the science database (1 we still don't know how accurate they are and 2 you've already got those results there anyway).


So all returned Tasks processed by the Test application that pass initial Validation will get credit, but won't be assimilated into the Science database; they'll get shunted off to where you can then compare them to the results produced by the stock application.

I guess the number to be released will be determined by how much time and effort it will take to do that cross checking- the larger the number (and the spread as some of the present CPU Tasks can take from 1.5hrs to just under 6hrs to complete) the better. But there's no point doing 100,000 if it's going to take you months to check them all out.
You want the largest possible number over the largest possible range, that you can deal with.



And if it all checks out and you do release the new version as the stock version, i'd suggest changing the Time out after Scheduler contact back to 30sec or so, so high-end GPUs don't end up sitting idle waiting for enough work to keep them busy.
And if there are any limits on the number of Tasks per compute device per machine they may need to be revised also- people really don't need to keep more than a couple of day's worth of work these days IMHO. But if the new application works as well as initial results are indicating, any present hard limits will likely need to be raised so they can have even just 24hrs of work cached.