Skip to content
MZGrid

White paper

MZGrid White Paper

An open GPU compute marketplace on Base, where every GPU-hour is priced, escrowed, settled and collateralised in the MZG token.

v1.2 · November 2026 · MZGrid Labs

Download PDFEnglish · PDF · 1.0 MB

Available in 8 languages. The English version is authoritative.

Key parameters

Single payment and settlement currency
MZG only
Protocol fee, included in the price
7%
Of each provider payout locked as collateral
20%
Exit delay before the lock is released
10 days

What it covers

From escrow to roadmap

A summary of the topics in the white paper. The PDF is the complete, authoritative text.

Abstract

An open marketplace connecting providers of verified GPU machines with customers — developers, startups, researchers and autonomous AI agents — who rent them by the second. Workloads run off-chain; every payment goes through an immutable escrow contract on Base.

Escrow and settlement

The customer deposits price per hour × maximum duration in MZG before a job starts. At settlement the contract pays the provider for the seconds actually used, sends the 7% protocol fee to the treasury and refunds the rest. The operator never holds funds.

The 20% provider lock

Instead of an up-front stake, 20% of every provider payout is locked in the provider registry and released only after a 10-day exit delay. The lock sets the job cap (25 MZG + 4 × locked) and can be slashed for abandoned jobs, going offline or failed verification, with half going to the affected customer.

Verification and reputation

Registration benchmarks, usage samples at least every 90 seconds, canary jobs and deadlines feed a 0–100 reliability score used by the scheduler. These checks make cheating detectable and costly; they do not cryptographically prove every computation.

MZG token and vesting

MZG is the single currency of the network: a fixed supply of 1,000,000,000 tokens minted once, with no mint function, no governance and no staking rewards. Allocation and vesting over up to 48 months are enforced on-chain by vesting contracts.

Security and trust model

What the immutable contracts enforce, what the coordinator is trusted to do and the bounds it cannot exceed, how workloads are isolated, and the testing done so far. MZGrid does not claim confidential computing, and no independent external audit has been completed yet — it is a requirement for leaving beta.

Roadmap and current status

Milestone-driven phases, not dates: the mainnet beta on Base, network expansion, and an independent external audit as the next step before leaving beta. Includes a snapshot of network figures.

Risks

Smart-contract, operator, token price, supply unlock, market, hardware and verification, data, chain, regulatory and key risks — read them before interacting with the protocol.

Contents

Sections of the white paper, as in the PDF.

  1. 1. Abstract
  2. 2. The problem: compute is the bottleneck
  3. 3. MZGrid at a glance
  4. 4. Architecture
  5. 5. Job lifecycle, escrow and settlement
  6. 6. Provider collateral: the 20% lock
  7. 7. Verification, reputation and scheduling
  8. 8. The MZG token
  9. 9. Pricing
  10. 10. Security and trust model
  11. 11. Roadmap and current status
  12. 12. Risks
  13. Appendix A. Protocol parameters
  14. Appendix B. Contract interface
  15. Appendix C. Glossary