Yes... and it's not tracked by timestamp or something along these lines. Look for posts by knreed or nelsoc for the old answer where we also wanted to have tick marks or color codes to see which results validated today.

That, will not happen! You get what you're offered, where there is already a system to tie fast devices together, but if there is no fast device the wingman result will go to the regular queue else the hopper will bog down quickly **. Those points wont go away at any rate, your patience will not either... this the ideal place to train it 24/7 :D

** Exception is presently DDDT-2 A-Type and Repair jobs. They always go to fast returners/low error rate devices.

Thats another way to answer the tongue in cheek question.

How would you propose with very high confidence to proof a device is able to do the job alone on a consistent basis when new to WCG? This waste is the price of doing business so to speak reduced to the lowest acceptable for the scientists.

For ZR projects there is a periodic re-proofing... think the total that runs eventually in quorum 2 is about 20%, still 80% better than the full quorum 2 projects, who need it for each and every result.

Disconnects forever... well what's your point? Even reliable devices that are paired with starters need periodic re-verification, so thank you for contributing 10 results.

When a reliable device is reverified through pairing with an unproven device [it works bi-redirectional], is that any different to 2 unproven devices checking each other, but then not needing 5 or 10, but 15 before that can be determined with very high confidence?

And yes, your reliable device will be used too for verification and to be re-verified, so at times you'll have results waiting in pending validation, but maybe you like a field on the device profile to be opted out and only be paired with fast reliable devices, with a lower preferential verification frequency.

--//--