이 페이지는 영어로만 제공됩니다. 영어 버전이 정본으로서 효력을 가집니다.
Lock & exit
How 20% of every payout becomes your collateral, how it raises your job cap, and how to exit and withdraw it after 10 days.
MZGrid has no staking step and no up-front bond. Instead, 20% of your share of every job is locked in the ProviderRegistry contract. The lock is your collateral: it raises the size of jobs you can take, it can be slashed if you break the rules, and it is returned to you when you leave the network.
The 80/20 split
At settlement the escrow takes the 7% protocol fee and splits the remaining 93% provider share:
| Share of provider share | Share of charged amount | |
|---|---|---|
| Liquid, paid to your wallet | 80% | 74.4% |
Locked in ProviderRegistry | 20% | 18.6% |
Worked example
A customer runs a job on your H100 SXM at 750 MZG/h for 10 hours.
| Item | MZG |
|---|---|
| Charged | 7,500.00 |
| Protocol fee (7%) | 525.00 |
| Provider share (93%) | 6,975.00 |
| Liquid to you (80% of share) | 5,580.00 |
| Added to your lock (20% of share) | 1,395.00 |
Liquid MZG arrives in your wallet in the settlement transaction. Locked MZG is added to your registry balance and emits a LockAdded event.
Job cap
The registry enforces a maximum deposit per job:
jobCap = 25 MZG + 4 × lockedA new provider can take jobs up to 25 MZG. Every MZG you lock adds 4 MZG of capacity. The escrow refuses to fund a job for you whose deposit exceeds your cap, and the scheduler does not route such jobs to you.
| Locked MZG | Job cap (MZG) | Longest H100 SXM job at 750 MZG/h | Charged volume needed to reach this lock |
|---|---|---|---|
| 0 | 25 | 2 min | — |
| 1,000 | 4,025 | 5.4 h | ≈ 5,376.3 MZG |
| 2,500 | 10,025 | 13.4 h | ≈ 13,440.9 MZG |
| 5,000 | 20,025 | 26.7 h | ≈ 26,881.7 MZG |
| 10,000 | 40,025 | 53.4 h | ≈ 53,763.4 MZG |
| 25,000 | 100,025 | 133.4 h | ≈ 134,408.6 MZG |
| 50,000 | 200,025 | 266.7 h | ≈ 268,817.2 MZG |
A 24-hour RTX 4090 job at 155 MZG/h has a deposit of 3,720 MZG, which a provider can accept with about 925 MZG locked — roughly 5,000 MZG of settled work. Datacenter providers reach the caps needed for multi-day H100 jobs after their first few tens of thousands of MZG of settled work.
Exiting
Locked MZG can only be withdrawn when you leave the network:
- Request exit. Run
mzgrid-provider exit, which callsrequestExit(). Your status changes fromActivetoExiting,exitRequestedAtis recorded and anExitRequestedevent is emitted with the unlock time. You stop receiving new jobs. - Finish active jobs. Jobs that are already running continue to completion and are settled normally.
- Wait 10 days.
EXIT_DELAYis 10 days fromexitRequestedAt. - Withdraw. Run
mzgrid-provider withdraw, which callswithdrawLocked(). It succeeds only if the 10 days have passed and youractiveJobscount is 0. Your full locked balance is transferred to your wallet and your status becomesExited.
mzgrid-provider status, GET /v1/providers/me (exitUnlockAt) and the provider dashboard all show the unlock countdown.
경고
Slashing remains possible throughout the 10-day exit delay. The delay exists so that any misconduct discovered after your last job — a failed spot check, an abandoned job — can still be compensated from your lock.
Coming back
An Exited provider can call register again to become Active. The lock starts from zero, and so does the job cap above the 25 MZG base.