Standards • MEVS

How projects earn verification

Deterministic criteria — no “lack of information.”

To pass MEVS, a project must provide verifiable proof. If a requirement is missing, the verification report will specify what to fix and how to fix it.

Pass / Conditional / Reject

Status	Meaning	What to do
VERIFIED	All required checks passed.	Embed the badge + publish your /.well-known/mevs.json
CONDITIONAL	Core checks passed; warnings remain (fixable).	Fix warnings to earn VERIFIED
REJECTED	One or more required checks failed.	Follow the “What to fix” list and resubmit

Required checklist

Public website reachable over HTTPS.
Contact email (domain-matching email recommended).
Token logo direct URL (SVG preferred).
Verification metadata JSON at /.well-known/mevs.json (or equivalent direct URL).
ERC‑20 basics readable: name(), symbol(), decimals(), totalSupply().
Ownership model disclosed: renounced, multisig, timelock, or explicit admin controls.

Optional but strongly recommended: on-chain liquidity lock proof link; audit or risk report; transparent tokenomics.

Metadata JSON template

Host this JSON on your website at /.well-known/mevs.json and update it when anything changes.

{
  "system": "MEVS",
  "project": "YourProjectName",
  "contract": "0xYourContract",
  "status": "VERIFIED|CONDITIONAL|REJECTED",
  "updated": "2026-01-22T00:00:00Z",
  "website": "https://yourdomain.com",
  "email": "support@yourdomain.com",
  "logo": "https://yourdomain.com/logo.svg",
  "proofs": {
    "liquidityLock": "https://link-to-proof",
    "audit": "https://link-to-audit-or-risk-report"
  },
  "notes": "Short, factual description of controls / risks / purpose."
}

MEVS • Standards

Deterministic criteria — no “lack of information.”