Acceptable Use Policy · v1.0

Acceptable Use Policy

Rules for everyone who requests jobs or provides GPU capacity on the OMC network. Last updated: October 4, 2026.

Language. This policy is published in English; the English version is the authoritative reference. Report violations to security@omc.network.

1 · Scope

This Acceptable Use Policy ("AUP") governs all use of the OMC network: submitting compute jobs, providing GPU capacity, operating nodes, and interacting with the protocol's smart contracts. It applies to every participant, including those acting through automated systems. It supplements — and does not replace — the network's technical documentation and any terms shown in the product interface.

2 · Prohibited content

You may not submit, store, process or distribute content that:

  • is illegal under the laws applicable to you or to the network's participants, including content that infringes intellectual property, privacy or data-protection rights;
  • depicts or sexualizes minors, or constitutes child sexual abuse material in any form;
  • promotes terrorism, violent extremism, targeted harassment, doxxing or credible threats of violence;
  • constitutes malware, phishing kits, credential theft, or the distribution of viruses, ransomware or botnets;
  • is designed to deceive: deepfakes of real people presented as authentic, forged documents, or fraud schemes.

3 · Prohibited workloads

You may not use OMC compute capacity to:

  • mine proof-of-work cryptocurrencies other than through the protocol's own verified-job rewards;
  • operate services whose purpose is denial-of-service, email or message spam, mass scanning, or password cracking against systems you do not own;
  • bypass export controls or sanctions, or provide compute to persons or entities prohibited by applicable law;
  • train or operate models for unlawful surveillance, unauthorized profiling of individuals, or weapons targeting;
  • circumvent the network's verification, staking or payment mechanisms, including fake heartbeats, self-dealing jobs, or colluding nodes.

4 · Network integrity

Attacks on the network itself are prohibited: exploiting smart-contract bugs outside a disclosed and authorized bug-bounty program, Sybil attacks on rewards or airdrops, manipulation of reputation scores, interference with scheduling or settlement, and any attempt to steal staked funds or job escrow. Security research is welcome only under responsible disclosure through security@omc.network.

5 · Provider obligations

Providers must run the official node client unmodified in its verification-relevant parts, declare hardware attributes honestly (VRAM, interconnect, region, confidential-computing capability), keep staking requirements met, complete accepted jobs within the agreed limits, and wipe job data as required by the job's data-protection level. Providers are responsible for the physical and legal security of their own hardware.

6 · Requester obligations

Requesters must submit jobs they are legally entitled to run, hold the rights to the data and model weights they upload, respect the data-protection level they select, and pay from escrow as settled by the protocol. Requesters should not submit job types that the network has labeled as unverifiable if they require strong correctness guarantees.

7 · Enforcement

Violations may result in: immediate job termination without payment; slashing of staked OMC under the protocol's published rules; loss of reputation or node eligibility; and, where warranted, blacklisting of the account or node. Illegal activity may be reported to the competent authorities. Severe violations — in particular those in Section 2 — may result in permanent exclusion and forfeiture under the slashing rules applicable at the time.

8 · Reporting and appeals

Report violations, suspicious jobs or compromised nodes to security@omc.network, including job identifiers, timestamps and any supporting evidence. If your node or job was penalized and you believe this was an error, contact the same address with the job identifiers; disputes follow the process described in the whitepaper (Section 5).

9 · Changes

This AUP may be updated as the network develops. Material changes are announced on the News page before taking effect, and the version date at the top of this page is updated accordingly. Continued use of the network after a change takes effect constitutes acceptance of the updated policy.