本文へスキップ
MZGrid

このページは英語版のみご利用いただけます。 英語版が正式な内容となります。

Overview & addresses

The three MZGrid contracts on Base, their deployed addresses, roles, the admin multisig and the trust model.

MZGrid's money flows are enforced by three Solidity contracts on Base, built with OpenZeppelin Contracts 5.x and Solidity 0.8.28.

ContractPurpose
MZGTokenThe MZG ERC-20 token with EIP-2612 permit. Fixed supply, no owner.
MZGridEscrowHolds customer deposits, settles jobs, takes the 7% fee and routes the 20% provider lock.
ProviderRegistryProvider registration, locked balances, job caps, the 10-day exit delay and slashing.

Vesting wallets for the token allocation are OpenZeppelin VestingWallet / VestingWalletCliff instances, described on the token page.

Networks

NetworkChain idExplorer
Base mainnet8453basescan.org
Base Sepolia (testnet)84532sepolia.basescan.org

Addresses

BasechainId 8453
  • MZGToken (MZG)0x0018b7E238DBfB210645B88072F32a77bd00C66e
  • MZGridEscrow0xD41600dA905E8327f7D8a9572cC10C6930Fa2bb9
  • ProviderRegistry0x12b555e28C1756CEEDCa9c0e2b920aCf60D8e477
  • トレジャリーのマルチシグ0xae5796Ddd59A177EfC5BD009f3A2D4736F28A809

Always verify an address against this page or the @mzgrid/sdk addresses export before approving tokens or sending transactions. Source code is verified on BaseScan and published at github.com/mzgrid.

Roles

Both MZGridEscrow and ProviderRegistry use OpenZeppelin AccessControl.

ContractRoleHolderCan do
MZGridEscrowDEFAULT_ADMIN_ROLEAdmin multisigGrant and revoke roles.
MZGridEscrowORACLE_ROLECoordinator settlement signercompleteJob, failJob.
ProviderRegistryDEFAULT_ADMIN_ROLEAdmin multisigGrant and revoke roles.
ProviderRegistryESCROW_ROLEMZGridEscrow contractaddLock, jobStarted, jobEnded.
ProviderRegistrySLASHER_ROLECoordinator verifierslash.

MZGToken has no roles and no owner.

Admin and governance

  • No token governance. MZG carries no voting rights and there is no on-chain governance module.
  • Admin multisig. The DEFAULT_ADMIN_ROLE on the escrow and registry is held by a multisig. Its only power is managing roles — for example rotating the coordinator's oracle or slasher key. It cannot change fees, the lock percentage, the exit delay, the job cap formula or the accept and timeout windows: these are constants compiled into the bytecode.
  • Immutable deployments. The contracts are not deployed behind proxies and cannot be upgraded. The treasury address is an immutable constructor argument of the escrow. A change to any rule would require deploying new contracts and users choosing to move to them.

Trust model

The contracts enforce the money rules; the coordinator supplies facts the chain cannot observe.

Enforced on-chainSupplied by the coordinator
Deposits can only leave escrow via settlement, cancel, fail or timeout reclaim.usedSeconds reported in completeJob.
charged is capped at the deposit; the 7% / 80% / 20% split is fixed.The decision to failJob a job.
Settlement only pays the client, the job's provider, the registry and the treasury.The slashing reason and amount (capped on-chain at the provider's lock).
Customers can cancel after 10 minutes and reclaim after deadline + 1 h without the coordinator.
Job cap and active-provider checks at funding time.
Locked MZG can only be withdrawn by the provider after a 10-day exit delay with no active jobs.

See the Security model for the full discussion.