Esta página está disponível apenas em inglês. A versão em inglês é a que prevalece.
Jurídico
Terms of Service
Última atualização: 5 de novembro de 2026
The terms that apply when you use the MZGrid website, coordinator API, SDK and provider agent, and how they relate to the MZGrid smart contracts on Base.
These Terms of Service ("Terms") govern your access to and use of the MZGrid website, dashboards, coordinator API, SDK, provider agent and related services (together, the "Services") operated by MZGrid Labs ("MZGrid Labs", "we", "us" or "our"). By accessing or using the Services, you agree to these Terms. If you do not agree, do not use the Services. When you sign in with your wallet, you accept these Terms by ticking the acceptance checkbox before signing; your acceptance is recorded with the version of these Terms (currently 2026-11-05) and a timestamp against your wallet address.
Please also read our Privacy Policy and our Risk Disclosure, which form part of these Terms.
Importante
MZGrid involves self-custodied crypto-assets, immutable smart contracts and computation on third-party hardware. You can lose MZG through your own mistakes, through provider or customer misbehaviour, through slashing, or through software defects. Read the Risk Disclosure before using the Services.
1. Definitions
- "Protocol" means the MZGrid smart contracts deployed on the Base network, including
MZGToken,ProviderRegistryandMZGridEscrow, as listed on the contracts page. - "MZG" means the MZG token, an ERC-20 token on Base used to pay for compute on the Protocol.
- "Coordinator" means the off-chain service operated by MZGrid Labs that provides the scheduler, verification, settlement oracle, API and related functions.
- "Customer" means a person who uses the Services to rent compute.
- "Provider" means a person who makes GPU hardware available through the Services.
- "Job" means a workload submitted by a Customer and executed by a Provider, together with its associated on-chain escrow record.
2. Eligibility and sanctions
You may use the Services only if:
- you are at least 18 years old and able to form a binding contract;
- you are not located in, organised in, or ordinarily resident in a country or territory subject to comprehensive sanctions, and you are not a person named on, or owned or controlled by a person named on, any sanctions list applicable to MZGrid Labs or to you;
- you are not prohibited by any law applicable to you from using crypto-assets, renting compute, or providing compute; and
- if you use the Services on behalf of an organisation, you have authority to bind that organisation to these Terms, in which case "you" includes that organisation.
We may restrict access to the Services from certain locations, block wallet addresses that we reasonably believe are associated with sanctioned persons or unlawful activity, and request information to confirm your eligibility. Use of tools to circumvent such restrictions is a breach of these Terms.
3. Wallets and keys
The Services are non-custodial. You interact with the Protocol using a wallet you control. MZGrid Labs never has access to your private keys, seed phrases or keystore passwords, and cannot recover them.
You are solely responsible for:
- keeping your private keys, seed phrases, keystore files and passwords secure;
- all transactions signed with your keys, including permit signatures;
- confirming the details of every transaction and signature before you approve it in your wallet; and
- holding enough ETH on Base to pay network fees.
Transactions on Base are generally irreversible. If you lose access to your keys, or someone else obtains them, we cannot reverse transactions, recover funds or restore access. API keys issued by the Coordinator are credentials for the Services; you must keep them confidential and revoke them promptly if compromised.
4. The Protocol and the Services are different things
The Protocol consists of immutable smart contracts running on the Base network. Once deployed, their code cannot be changed by anyone, including MZGrid Labs. The admin role in the contracts is held by a multisig and is limited to managing roles (such as which addresses may act as the settlement oracle or slasher), as documented on the contracts page.
The Services are software and infrastructure operated by MZGrid Labs that help you use the Protocol. In particular, the Coordinator:
- matches Jobs to Providers and dispatches them;
- receives usage reports, runs benchmarks and verification checks;
- acts as the settlement oracle, calling
completeJobandfailJobon the escrow contract; and - acts as slasher, calling
slashon the provider registry when the slashing rules are triggered.
The Coordinator is a centralised component operated by us. The contracts limit what it can do — for example, it cannot charge a Customer more than the Job deposit, and slashing is capped at a Provider's locked balance — but it is not trustless. You may interact with the contracts directly without using our website, subject to the same rules the contracts enforce. Certain functions, such as cancelJob and reclaimTimeout, are designed so that Customers can recover deposits without relying on the Coordinator.
We may modify, suspend or discontinue any part of the Services at any time, including for maintenance, security or legal reasons. Doing so does not change the Protocol.
5. Customer obligations and acceptable use
As a Customer, you are responsible for the workloads, container images, models, data and configuration you submit, and for complying with the licences of any models or software you run. You must not use the Services to:
- process, store, generate or distribute content that is illegal, including child sexual abuse material, content that infringes intellectual property rights, or content that violates privacy or data protection law;
- attack, probe, scan or disrupt any system or network, including the Provider's host, other Jobs, the Coordinator, the Protocol or any third party (including denial-of-service attacks, credential stuffing, and exploit development against systems you are not authorised to test);
- attempt to escape container isolation, access the Provider's host, network or other tenants, or tamper with the provider agent or usage reporting;
- mine crypto-assets or run proof-of-work workloads, or otherwise use the Services in a way designed to extract value from Providers other than by paying the agreed price for compute;
- send spam, operate malware or botnet infrastructure, or facilitate fraud;
- train or run models for purposes that are unlawful in your jurisdiction or the Provider's jurisdiction; or
- evade sanctions, launder proceeds of crime or otherwise violate applicable law.
Providers may stop a Job that they reasonably believe violates this section and must report it to us. We may fail Jobs, revoke API keys and refuse service to Customers who breach this section, and we may report unlawful activity to the relevant authorities.
6. Provider obligations
As a Provider, you represent and agree that:
- Hardware honesty. The GPUs, CPU, memory, storage and bandwidth you register are accurately described, under your control, and lawfully available for you to use for this purpose. You will not manipulate benchmarks, usage reports or verification outputs.
- Isolation. You will run Jobs using the official provider agent or a compatible build that preserves its isolation settings (no host network, no privileged mode, resource limits, per-job temporary storage). You will not inspect, copy, retain, modify or disclose Customer data, models or outputs except as strictly necessary to run the Job.
- Availability. When you accept a Job, you will keep the machine powered, connected and running until the Job completes or is stopped by the Customer. Failure to do so may result in slashing under Section 9.
- Law and permissions. You have all permissions required to operate the hardware and network connection for commercial compute (including from landlords, employers, hosting providers and network operators), and you are responsible for your own electricity, equipment, taxes and regulatory obligations.
- Security. You will keep the host operating system, drivers and agent reasonably up to date and will notify [email protected] promptly if you become aware of a compromise affecting Jobs.
Provider status, prices and offers are displayed on the Services based on information you supply and verification we perform. We may mark a machine as unverified, exclude it from scheduling, or remove offers that we reasonably believe are inaccurate or harmful.
7. Fees and payment in MZG
All prices on the Services and the Protocol are denominated and paid in MZG. Providers set their own prices per GPU-hour; reference prices published by us are informational only.
The Protocol charges a protocol fee of 7% of the amount actually charged for each Job, which is transferred to the treasury address set in the escrow contract. The fee is included in the price shown for an offer and is not added on top. Network fees on Base are paid in ETH by the party sending the transaction and are not received by MZGrid Labs.
We do not quote, guarantee or support any value of MZG in any other asset or currency, and the cost of compute and the value of Provider earnings may change significantly as the market value of MZG changes. See the Risk Disclosure.
8. Escrow, settlement and refunds
Jobs are funded and settled by the escrow contract according to its code. In summary:
- Deposit. Before a Job runs, the Customer deposits
pricePerHour × maxDurationMZG into escrow. The deposit may not exceed the Provider's job cap of25 MZG + 4 × locked balance. - Acceptance. The Provider must accept the Job on-chain within 10 minutes of funding. If it does not, the Customer may cancel and receive the full deposit back.
- Settlement. When the Job ends, the Coordinator settles it. The amount charged is
min(deposit, pricePerHour × usedSeconds / 3600), billed per second of use. Of the amount charged, 7% goes to the treasury and 93% is the Provider's share, of which 80% is paid to the Provider and 20% is locked in the provider registry. The unused part of the deposit is refunded to the Customer in the same transaction. - Failure. If a Job is failed by the Coordinator (for example, because the Provider went offline or failed verification), the Customer receives the full deposit back.
- Timeout. If a running Job has not been settled by its deadline plus a one-hour grace period, the Customer may call
reclaimTimeoutand receive the full deposit back.
Except as provided by the contract mechanisms above, charges for completed compute are final. We do not issue refunds outside the Protocol, and we cannot reverse on-chain settlements. If you believe a Job was settled incorrectly, contact [email protected] with the Job ID; we will review it in good faith, but any remedy is at our discretion and limited to what is technically possible.
9. Provider lock and slashing
20% of each Provider's share of every settled Job is locked in the provider registry as collateral. Locked MZG does not earn any return. It is released only after the Provider calls requestExit, waits 10 days, has no active Jobs, and calls withdrawLocked.
A Provider's locked balance may be slashed, including during the 10-day exit period, under the following rules, as applied by the Coordinator's verifier:
| Event | Slash |
|---|---|
| Accepted Job not completed by its deadline (abandoned) | min(locked, 2 × Job deposit) |
| No usage report for more than 10 minutes while a Job is running | min(locked, 1 × Job deposit) |
| Failed verification or fraud | 100% of locked |
Slashed MZG is distributed 50% to the affected Customer and 50% to the treasury. Detailed rules are in the slashing documentation. By registering as a Provider, you accept that slashing decisions are made by the Coordinator's verifier and executed on-chain, and that slashed amounts cannot be returned by the Protocol. If you believe a slash was applied in error, contact [email protected] within 30 days; any remedy is at our discretion.
10. No governance, staking or profit rights
MZG does not confer voting rights, governance rights, ownership of MZGrid Labs, a share of profits or revenue, or any claim against MZGrid Labs. There is no staking program and no yield. The treasury is controlled by a multisig and its use is at the discretion of its signers. Nothing in the Services is an offer or solicitation to buy or sell any asset or investment.
11. Third-party hardware and data
Jobs run on hardware owned and operated by independent Providers, not by MZGrid Labs. Container isolation reduces risk but does not provide confidential computing. A Provider with physical or administrative access to a machine may be able to observe data, models and outputs processed on it. You should not submit data to a Job unless you are comfortable with it being accessible to a third party, and you are responsible for having a lawful basis to process any personal data you submit. We do not warrant the performance, availability, security or conduct of any Provider.
12. Intellectual property
We and our licensors own the Services, including the website, documentation, branding, the MZGrid name and logo. Source code that we publish under an open-source licence (for example, on GitHub) is governed by that licence. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable licence to use the Services for their intended purpose.
You retain all rights to the workloads, models, data and outputs you submit or receive. You grant us only the rights necessary to operate the Services, such as storing Job metadata and logs as described in the Privacy Policy. If you send us feedback, we may use it without obligation to you.
13. Disclaimers
THE SERVICES AND THE PROTOCOL ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. We do not warrant that the Services will be uninterrupted, timely, secure or error-free; that any Job will be accepted, completed or produce correct output; that any Provider will be available; that the smart contracts are free of defects; or that MZG will have any particular value or liquidity. The contracts have not completed a third-party audit. Some jurisdictions do not allow the exclusion of certain warranties, so some of these exclusions may not apply to you.
14. Limitation of liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, MZGRID LABS AND ITS CONTRIBUTORS, OFFICERS, EMPLOYEES AND AGENTS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA, GOODWILL OR CRYPTO-ASSETS, ARISING OUT OF OR RELATING TO THE SERVICES OR THE PROTOCOL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR TOTAL LIABILITY FOR ALL CLAIMS RELATING TO THE SERVICES IS LIMITED TO THE GREATER OF (A) THE PROTOCOL FEES ATTRIBUTABLE TO YOUR JOBS IN THE THREE MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, MEASURED IN MZG, AND (B) 22,000 MZG.
Nothing in these Terms limits liability that cannot be limited under applicable law, such as liability for fraud or for death or personal injury caused by negligence.
15. Indemnity
You will indemnify and hold harmless MZGrid Labs and its contributors, officers, employees and agents from any claims, losses, liabilities and expenses (including reasonable legal fees) arising out of: your use of the Services; your workloads, data or hardware; your breach of these Terms; or your violation of any law or the rights of a third party.
16. Suspension and termination
You may stop using the Services at any time. Providers who wish to leave should follow the exit process in the lock and exit documentation.
We may suspend or terminate your access to the Services, revoke API keys, exclude your machines from scheduling, or fail your active Jobs if we reasonably believe you have breached these Terms, pose a security or legal risk, or if required by law. Because the Protocol is permissionless, termination of the Services does not prevent you from interacting with the contracts directly, and does not affect funds held in escrow or locked balances, which remain subject to the contract rules (including refunds, timeouts, exit and slashing). Sections 7 to 15, 17 and 18 survive termination.
17. Governing law and disputes
These Terms are governed by the laws of the jurisdiction in which MZGrid Labs is organised, without regard to conflict-of-law rules. Before starting any formal proceedings, you agree to contact [email protected] and try in good faith to resolve the dispute informally for at least 30 days.
Any dispute that is not resolved informally will be finally resolved by binding arbitration before a single arbitrator under internationally recognised arbitration rules, conducted in English, except that either party may seek urgent injunctive relief in a competent court. To the extent permitted by law, disputes will be resolved on an individual basis and not as a class or representative action. If any part of this section is unenforceable for you under mandatory consumer protection law, that part does not apply to you.
18. Changes to these Terms
We may update these Terms from time to time. We will post the updated version on this page with a new "last updated" date and, for material changes, give reasonable advance notice through the Services or our blog. Continued use of the Services after changes take effect constitutes acceptance. Changes to these Terms do not change the code of the Protocol.
19. General
These Terms, together with the Privacy Policy and the Risk Disclosure, are the entire agreement between you and MZGrid Labs about the Services. If any provision is held unenforceable, the remainder stays in effect. Our failure to enforce a provision is not a waiver. You may not assign these Terms without our consent; we may assign them in connection with a reorganisation or transfer of the Services.
20. Contact
- Legal questions: [email protected]
- Support, billing and slashing reviews: [email protected]
- Security reports: [email protected]
- Privacy requests: [email protected]