Esta página solo está disponible en inglés. La versión en inglés es la que prevalece.
Slashing
The three slashing reasons, the exact amounts, how slashed MZG is split between the client and the treasury, and worked examples.
Slashing removes MZG from a provider's lock when the provider fails a customer. It is executed by the coordinator's verifier, which holds the SLASHER_ROLE on the ProviderRegistry, after the affected job has been failed and the customer fully refunded.
Reasons and amounts
| Code | Reason | Trigger | Amount slashed |
|---|---|---|---|
1 | Abandoned | You accepted a job and did not finish it by its deadline. | min(locked, 2 × job deposit) |
2 | OfflineDuringJob | No usage samples for more than 10 minutes while a job was running. | min(locked, 1 × job deposit) |
3 | VerificationFailed | A spot check returned the wrong result, or other evidence of fraud. | 100% of locked |
The amount is always capped at what you actually have locked; a slash never takes your liquid earnings or anything in your wallet.
Where slashed MZG goes
- 50% to the affected customer, in addition to the full refund of their deposit.
- 50% to the treasury.
If there is no affected customer address, the whole amount goes to the treasury. Every slash emits:
event Slashed(address indexed provider, bytes32 indexed jobId, uint8 reason, uint256 amount, uint256 toClient, uint256 toTreasury);Examples
All examples assume a provider with 8,800 MZG locked and a job deposit of 3,000 MZG (an H100 SXM at 750 MZG/h for 4 hours).
Offline during a job
The machine loses power two hours into the job and does not report for more than 10 minutes.
| Item | MZG |
|---|---|
| Slashed: min(8,800, 1 × 3,000) | 3,000.00 |
| To the customer (50%) | 1,500.00 |
| To the treasury (50%) | 1,500.00 |
| Provider lock after | 5,800.00 |
The customer also receives their full 3,000 MZG deposit back.
Abandoned job
The provider accepts the job and never completes it by the deadline.
| Item | MZG |
|---|---|
| Slashed: min(8,800, 2 × 3,000) | 6,000.00 |
| To the customer | 3,000.00 |
| To the treasury | 3,000.00 |
| Provider lock after | 2,800.00 |
Verification failed
A canary job returns a result hash that does not match the expected output.
| Item | MZG |
|---|---|
| Slashed: 100% of 8,800 | 8,800.00 |
| To the customer | 4,400.00 |
| To the treasury | 4,400.00 |
| Provider lock after | 0.00 |
A new provider with a small lock
A provider with 950 MZG locked goes offline during a 3,720 MZG job. The slash is min(950, 3,720) = 950 MZG: 475 MZG to the customer, 475 MZG to the treasury. The customer still gets the full 3,720 MZG refund from escrow. This is why the job cap keeps a new provider's jobs in proportion to its lock: 25 + 4 × 950 = 3,825 MZG.
Avoiding slashes
- Run the agent as a service with automatic restart (see the systemd example).
- Use a UPS and a reliable connection; schedule maintenance only when no jobs are running.
- Do not overcommit: a GPU serves one job at a time.
- Never alter, short-circuit or cache customer workloads. Spot checks are indistinguishable from real jobs.
Slashes also lower your reputation through the completion-rate component.