We were previously discussing the fact that users could just return a 'unsuccessful password range' without performing the computation when distributed HOB work, but perhaps sub-task spot-checking could eliminate this behaviour? If returned results do not contain valid spot-checkpoint results then we could disregard the result and administer a punishment to the user for manipulating the result.
We were previously discussing the fact that users could just return a 'unsuccessful password range' without performing the computation when distributed HOB work, but perhaps sub-task spot-checking could eliminate this behaviour? If returned results do not contain valid spot-checkpoint results then we could disregard the result and administer a punishment to the user for manipulating the result.