跳至正文
MZGrid

此页面仅提供英文版本。 以英文版本为准。

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 shareShare of charged amount
Liquid, paid to your wallet80%74.4%
Locked in ProviderRegistry20%18.6%

Worked example

A customer runs a job on your H100 SXM at 750 MZG/h for 10 hours.

ItemMZG
Charged7,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 × locked

A 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 MZGJob cap (MZG)Longest H100 SXM job at 750 MZG/hCharged volume needed to reach this lock
0252 min—
1,0004,0255.4 h≈ 5,376.3 MZG
2,50010,02513.4 h≈ 13,440.9 MZG
5,00020,02526.7 h≈ 26,881.7 MZG
10,00040,02553.4 h≈ 53,763.4 MZG
25,000100,025133.4 h≈ 134,408.6 MZG
50,000200,025266.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:

  1. Request exit. Run mzgrid-provider exit, which calls requestExit(). Your status changes from Active to Exiting, exitRequestedAt is recorded and an ExitRequested event is emitted with the unlock time. You stop receiving new jobs.
  2. Finish active jobs. Jobs that are already running continue to completion and are settled normally.
  3. Wait 10 days. EXIT_DELAY is 10 days from exitRequestedAt.
  4. Withdraw. Run mzgrid-provider withdraw, which calls withdrawLocked(). It succeeds only if the 10 days have passed and your activeJobs count is 0. Your full locked balance is transferred to your wallet and your status becomes Exited.

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.