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.
| Contract | Purpose |
|---|---|
MZGToken | The MZG ERC-20 token with EIP-2612 permit. Fixed supply, no owner. |
MZGridEscrow | Holds customer deposits, settles jobs, takes the 7% fee and routes the 20% provider lock. |
ProviderRegistry | Provider 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
| Network | Chain id | Explorer |
|---|---|---|
| Base mainnet | 8453 | basescan.org |
| Base Sepolia (testnet) | 84532 | sepolia.basescan.org |
Addresses
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.
| Contract | Role | Holder | Can do |
|---|---|---|---|
MZGridEscrow | DEFAULT_ADMIN_ROLE | Admin multisig | Grant and revoke roles. |
MZGridEscrow | ORACLE_ROLE | Coordinator settlement signer | completeJob, failJob. |
ProviderRegistry | DEFAULT_ADMIN_ROLE | Admin multisig | Grant and revoke roles. |
ProviderRegistry | ESCROW_ROLE | MZGridEscrow contract | addLock, jobStarted, jobEnded. |
ProviderRegistry | SLASHER_ROLE | Coordinator verifier | slash. |
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_ROLEon 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 areconstants 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-chain | Supplied 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.