Is there such a thing as an "un-disqualify"?

[Alexey]

I already said what I think about suspension instead of disqualification:

@Alexey

The suspension mode is a good suggestion from the SNO point of view, but a very bad from the satellites’ and customers’ points of view:

• your node doesn’t have requested files, but they can be requested by customers and they got an error “file not found”;
• it can trigger the repair job, because all pieces on your node will be marked as temporary unhealthy;
• if the repair job has been triggered, the payment for repairing would be taken from the satellite’s operator pocket, not from the held amount of the suspended node;
• the suspended node will lose the repaired pieces, because they will be stored on more reliable nodes;
• the satellite operator will pay for inaccessible data from its pocket until you fix the problem or until a week is gone.

The current implementation of suspension will be used only if your node would answer with unknown error. It’s not so great number of nodes as if were taken into account the “no such file” errors.

It should be extended to work as a slow disqualification:

• forbid not only PUT, but GET too (see storj/docs/blueprints/audit-suspend.md at 5786595d141ff8b8c8be21e5e8696dd73e04d08d · storj/storj · GitHub);
• take any costs from your held amount to recover missed pieces if repair trigger is fired;
• reduce reputation and levels of trust (i.e. - put 25% to held amount, then 50%, then 75% depending on level of loses);
• enable vetting again.

The recovered pieces will be removed from such node with a Garbage collector.