İçeriğe geç
MZGrid

Bu sayfa yalnızca İngilizce olarak mevcuttur. Bağlayıcı olan İngilizce sürümdür.

Yasal

Risk Disclosure

Son güncelleme: 1 Ekim 2026

The material risks of using MZG and the MZGrid protocol — token price volatility, smart contract and coordinator risk, provider lock and slashing, third-party hardware, Base network risk, regulation, key loss and supply unlocks.

This Risk Disclosure describes material risks of holding or using MZG and of using the MZGrid protocol and the services operated by MZGrid Labs ("MZGrid Labs", "we"). It forms part of our Terms of Service. It is not exhaustive: other risks exist, including risks we cannot foresee.

Read it in full before you acquire MZG, deposit MZG into escrow or register as a provider. If you do not understand these risks, do not use MZGrid. Nothing on the MZGrid website, in our documentation, blog or social channels is financial, investment, legal or tax advice.

Uyarı

You can lose some or all of the MZG you use with MZGrid. MZGrid Labs does not guarantee the value, liquidity or availability of MZG, the availability of compute, or any level of provider income.

1. MZG price volatility changes the real cost of compute and provider income

Every price on MZGrid is denominated in MZG: offers, deposits, settlements, the 7% protocol fee, provider payouts, the 20% lock, the job cap and slashing amounts. There is no price feed and no conversion to any other asset or currency inside the protocol.

This has direct consequences:

  • For customers, the real cost of a GPU-hour depends on the market value of MZG at the time you acquire it. If MZG's market value rises, the same offer costs you more in real terms; if you buy MZG in advance and its value falls, you may have paid more than necessary.
  • For providers, your costs — hardware, electricity, hosting, bandwidth — are not denominated in MZG. If MZG's market value falls, the same number of MZG earned covers less of those costs, and running a node may stop being economical. Provider prices adjust only when providers change them, and reference prices are reviewed only periodically.
  • Locked MZG is held for at least 10 days after you request an exit. Its market value may change substantially during that time and while it is locked.

The market value of MZG may be highly volatile and may fall to zero. It can be affected by demand for compute, the number of providers, market sentiment, liquidity, actions of large holders, regulatory developments, security incidents and factors unrelated to MZGrid.

2. No guarantees of price, liquidity, listing, yield or returns

  • MZGrid Labs does not publish, target, support or stabilise any market price for MZG.
  • There is no guarantee that MZG can be bought or sold on any venue, at any price, in any quantity. Liquidity may be thin or unavailable.
  • We make no representation that MZG is or will be listed on any exchange or trading venue.
  • MZG does not pay interest, dividends, yield or rewards. Locked MZG earns nothing. There is no staking program.
  • Any figures we publish about network activity, utilisation or illustrative provider earnings describe the past or explain the protocol's arithmetic. They are not forecasts and not promises.

3. MZG is a utility token, not an investment

MZG exists to pay for compute on the MZGrid network, to settle provider payouts and to serve as provider collateral. It is not designed or offered as an investment.

Holding MZG does not give you:

  • ownership of, or equity in, MZGrid Labs or any other entity;
  • any right to profits, revenue, the treasury or protocol fees;
  • any right to vote or participate in governance — there is no governance and no token voting; admin roles are held by a multisig; or
  • any claim against MZGrid Labs for redemption, repurchase or a minimum value.

You should not acquire MZG with the expectation of profit from the efforts of MZGrid Labs or anyone else.

4. Smart contract risk

The MZGrid contracts (MZGToken, ProviderRegistry, MZGridEscrow) are deployed on Base and are not upgradeable. They have been tested with unit, fuzz and invariant tests and reviewed internally. They have not completed an independent third-party audit, and we do not claim that they have.

Despite testing, the contracts may contain bugs or design flaws. Because they cannot be upgraded, a defect cannot be patched in place: it may require migrating to new contracts, during which funds held in escrow or locked balances could be delayed, inaccessible or lost. Smart contracts may also interact unexpectedly with wallets, tokens, other contracts or future changes to the Base network. The Security page describes the current security posture.

5. Coordinator centralisation and admin roles

Important parts of MZGrid are operated by MZGrid Labs today:

  • the scheduler, which selects providers for jobs;
  • the verifier, which runs benchmarks, checks usage reports and canary jobs, and decides when slashing rules have been triggered (it holds the SLASHER_ROLE);
  • the settlement oracle, which reports how long each job ran and calls completeJob or failJob (it holds the ORACLE_ROLE); and
  • the website, API and indexer that most users rely on.

The contracts bound what these components can do: a customer can never be charged more than their deposit, refunds always return to the client, slashing is capped at a provider's locked balance and split 50/50 between the affected client and the treasury, and clients can call reclaimTimeout if a job is never settled. Within those bounds, however, the coordinator is trusted. A bug, outage, compromise or error in the coordinator could cause incorrect settlement, wrongful or missed slashing, failed jobs or service interruptions.

The DEFAULT_ADMIN_ROLE in the contracts is held by a multisig controlled by MZGrid Labs. It can grant and revoke the oracle and slasher roles. A compromise of the multisig or the oracle key, or a mistaken role change, could harm users within the limits described above. The treasury is also a multisig address; its use is at the discretion of its signers.

6. Provider risks: lock, exit delay and slashing

If you are a provider:

  • 20% of your share of every job is locked in the provider registry. You cannot withdraw it while you are active.
  • Exit takes at least 10 days. You must call requestExit, wait 10 days and have no active jobs before calling withdrawLocked. During that time you receive no new jobs.
  • You can be slashed, including during the exit period. Abandoning an accepted job can cost up to twice the job deposit; going offline for more than 10 minutes during a job can cost up to the job deposit; failed verification or fraud costs 100% of your locked balance. Slashed MZG is not returned.
  • Slashing decisions are made by the coordinator's verifier. Ordinary failures — power cuts, internet outages, hardware faults, operating system updates, bugs in the agent — can trigger slashing even if you acted in good faith. Verification uses statistical checks that could, in rare cases, produce false positives.
  • Earnings are not guaranteed. Demand for your hardware may be low or zero. A new provider is limited to job deposits of 25 MZG + 4 × locked, which restricts which jobs you can take.
  • You bear your own costs for hardware, electricity, cooling, hosting and network, and any damage or wear to your equipment.
  • Workloads are supplied by third parties. Despite container isolation and acceptable use rules, a customer workload could be malicious, attempt to exploit your system, or involve unlawful content.

7. Third-party hardware and data confidentiality

Jobs run on machines owned and operated by independent providers. MZGrid is not confidential computing. Container isolation protects jobs from each other and providers from jobs, but it does not prevent a provider with physical or administrative access from observing the memory, storage, network traffic, models, inputs and outputs of a job running on their machine.

Do not send data to a job — including prompts, files, model weights, credentials or personal data — unless you accept the risk that a third party may access it. Providers may also deliver incorrect results, perform poorly, or disconnect; verification reduces but does not eliminate these risks. Providers may be located in any country, which may have implications for your legal obligations regarding the data you process.

8. Base network risks

MZGrid depends on the Base network, an Ethereum layer-2 network that we do not operate or control.

  • Congestion and fees. Transactions require gas paid in ETH, not MZG. Network fees can rise sharply during congestion, making small jobs uneconomical, and transactions may be delayed.
  • Sequencer downtime. Base currently relies on a sequencer. If it halts or censors transactions, you may be unable to fund, accept, settle, cancel or reclaim jobs, or to exit, for the duration. Time-based rules (the accept window, deadlines, timeouts and the exit delay) continue to run on block timestamps, which may disadvantage you if you cannot transact in time.
  • Reorganisations and finality. Blocks can be reorganised before they are final. The coordinator may act on events that are later reorganised away, leading to delays or inconsistencies.
  • Bridges and upgrades. Base and its underlying infrastructure may be upgraded, changed or suffer failures, including failures of bridges between Base and other networks.
  • RPC providers. Wallets and the coordinator rely on RPC node providers, which may be unavailable or return incorrect data.

See base.org for information about the Base network.

9. Regulatory and tax risk

The legal and regulatory treatment of crypto-assets, decentralised compute markets and smart contracts is uncertain and varies between jurisdictions. Laws or regulators may change in ways that restrict or prohibit holding or using MZG, operating the coordinator, providing compute, or accessing the website from certain locations. MZGrid Labs may be required to restrict, suspend or discontinue some or all of the Services in some or all jurisdictions, which could reduce demand for MZG or make it harder to use.

You are responsible for determining and paying any taxes that apply to you, including on acquiring, using, earning, locking or disposing of MZG, and for complying with any rules that apply to providing compute or processing data in your jurisdiction. Tax treatment may be complex and may differ for customers and providers. Seek independent advice.

10. Key loss and wallet risk

MZGrid is non-custodial. If you lose your private key, seed phrase or keystore password, or if someone else obtains them, you may permanently lose your MZG, your locked balance and control of your provider identity. We cannot recover keys or reverse transactions.

Be careful what you sign. A malicious website or application could ask you to sign an approval or EIP-2612 permit that allows a third party to transfer your MZG. Check that the spender is the MZGrid escrow contract listed on the contracts page, and that the amount matches the job deposit.

Provider agents store an encrypted keystore on the provider's machine; a compromise of that machine may expose the provider's key.

11. Supply and vesting unlocks

MZG has a fixed supply of 1,000,000,000 tokens and no mint function. A substantial part of the supply is subject to vesting schedules — for network incentives, ecosystem grants, treasury and operations, team and contributors, and investors and strategic partners — as published on the token page. As tokens vest over time, the circulating supply increases. Holders of vested tokens may sell them, which could affect the market value and liquidity of MZG. The vesting schedules are enforced by on-chain vesting contracts, but how vested tokens are used once released is at the discretion of their recipients.

12. Operational and business risk

MZGrid Labs may not succeed in maintaining or developing the network. Demand for decentralised compute may not grow, competition may increase, key contributors may leave and funding may run out. We may change, suspend or discontinue the Services. If the coordinator stops operating, the contracts continue to exist and clients can recover unsettled deposits through cancelJob and reclaimTimeout, and providers can exit through requestExit and withdrawLocked, but the network would no longer match or settle jobs unless another operator took over those roles.

13. Network figures, demo data and forward-looking statements

The website shows network statistics, maps, leaderboards and activity feeds. Some environments of the website, including previews and demonstration deployments, display simulated data that does not reflect real network activity. Do not rely on displayed figures for financial decisions.

Statements on the website, in documentation, blog posts or social media about future plans, features, network growth or work in progress are forward-looking. They reflect current intentions only, are not commitments, and may change or never happen.

14. Contact

Questions about this disclosure: [email protected]. Security issues: [email protected]. General support: [email protected].