Trust and verification
Every machine has a trust from 0 to 100, which the Machines page and unitfabric machines show. Ours are at 100. A machine you enrol starts at 50, or lower if one of your organization’s machines has fallen lower: your organization’s trust is the lowest any of its confirmed machines reached, so a machine removed and enrolled again starts nothing afresh. From 80 a machine is verified: it runs jobs that ask for verified machines (pool: verified, see pools), and its earnings are credited at once instead of being held for 14 days (how earnings work).
How the work is checked
Section titled “How the work is checked”- Checks among its units. Now and then a unit your machine is given is a check whose right output we already know.
- Units run again. A share of the units your machine completes is run again on a machine of ours of its class, and your machine’s output is judged by ours.
- Compared as the work allows. Two cards of a class do not always make the same bytes, so outputs are compared with the tolerance the work needs, not byte for byte. An output that is missing, cannot be read, or changed after your machine reported it is wrong.
Work that needs a GPU is checked on a machine of ours of your machine’s GPU class, and work that needs none on a CPU machine of ours. Until we run a machine of its GPU class, a machine cannot be checked on GPU work: it takes your organization’s own jobs, and can take other organizations’ jobs that need no GPU.
What raises and lowers it
Section titled “What raises and lowers it”- A right output raises it a little.
- A wrong output lowers it a lot. When it was a unit run again, the buyer gets our machine’s output, and yours earns nothing for it.
- A check that takes far longer than the machine’s benchmark says it should, a check it fails or drops, and a lease it loses, or lets run past its deadline, each lower it a little. These alone never revoke a machine.
Revocation
Section titled “Revocation”A machine whose wrong outputs take its trust low enough is revoked: its token stops working at once, the lease it holds ends and its units go to other machines, and every earning of it that no payout covered is voided. A revoked machine does not come back. Your organization’s next machines start at the trust it fell to, and an organization whose machines fell that low enrols no more. We can also revoke a machine ourselves, for abuse or at your request: one we revoke for cheating or wrong outputs loses its unpaid earnings as above, and any other keeps them, payable.
Disputes
Section titled “Disputes”If you think a verdict, a fall in trust, a revocation, or earnings held or voided are wrong, write to the support address shown on your receipts for a review, with the machine’s id. An operator looks at what your machine returned and at what it was compared with. A verdict found wrong is overturned: the trust it took comes back, to the machine and to the trust your organization’s new machines start at, it no longer counts towards a revocation, and the earnings it held back are released once their hold has passed. A machine revoked wrongly stays revoked, and you enrol it again as a new one, at the trust put back; what its revocation voided comes back as the earnings they were, payable, held or credit only as before.