The Adaptive Declaration Layer — ten markdown files. Language-agnostic. No runtime dependency. The formal bridge between your system and the MEV standard.
The MEV Lite SDK is not a library you install. It is not a dependency you import at runtime. It is a set of standardised markdown files you include in your codebase to formally declare how your system implements the MEV standard.
Think of it as the MEV standard's equivalent of a LICENSE file — but instead of declaring copyright, it declares your economic framework. It tells the world exactly how your system generates MEVU, what your milestone formula is, what Diapause phase you are in, and how you connect to the global registry.
Each file declares one aspect of your MEV implementation. Together they constitute your full MEV compliance declaration.
The entry point for any reader. Explains what MEV is and how this specific project implements it. This is the first file anyone reads.
This project implements MEV Standard v1 (officialMEV.org).
MEVU = verified commerce transactions × V.
Milestones: k × 10ⁿ formula.
Declares the project under the MEV Open Standard License v1. Records the license version and certificate ID.
License: MEV Open Standard License v1
Certificate: MEV-001-MEZE
Issued by: MEV Foundation, 2026
Proof of certification. Contains your unique Registry ID, certification date, and link to your registry entry on officialMEV.org.
Registry ID: MEV-001
Status: MEV-Certified
Issued: 2026
Registry: officialMEV.org/registry/meze
Declares the form MEVU takes in this system — token, credit, index, credential, or score — along with the supply model and issuance mechanism.
MEVU Form: MEZE native token
Supply: Adaptive (Revenue-Backed)
Issuance: Per verified commerce event
Declares the milestone formula chosen, the milestone scale, Epoch types, Te values per phase, and the on-chain or off-chain Epoch response mechanism.
Formula: M = k × 10ⁿ, k ∈ {"{"}1,5{"}"}
Scale: 1, 5, 10, 50, 100...
Epoch Response: NFT minting
Declares the system's current Diapause phase (S=0 or S=1), the published H trigger thresholds, D parameter values, and the activation function configuration. Required for all MEV implementations.
Phase: I (S=0)
Activation: All MEVU activates immediately
Future: Full Diapause planned Phase II+
The MEV Rule Set Specification. Formally defines what constitutes Activity (A), how V is calculated, the milestone thresholds, and any adopter-specific rules governing MEVU issuance.
A: Settled commerce transaction
V: EIP-712 OCEO payload × verifier
M: k × 10ⁿ threshold crossing
Declares the MEV Oracle operating mode — Off-Chain Only, On-Chain Only, or Bridge. For Bridge mode, documents the off-chain bridge architecture, signing mechanism, and data freshness policy.
Mode: Bridge
Oracle: OCEO (EIP-712 signed)
Freshness: 5-minute window
Formally defines what constitutes a valid Activity event in this system. Specifies the data sources, event types, and any exclusion criteria for activity that cannot generate MEVU.
RBT: Settled food commerce payment
RBA: Settled platform revenue event
Exclusions: Test transactions, refunds
The innovation declaration. Documents everything the adopter built on top of the MEV foundation — their unique architecture, mechanisms, and contributions. This is what makes each implementation distinct.
Innovations: RBM, RBT, RBA, OCEO,
NativeTrigger, AllocationVault,
MEVTracker, Epoch NFT System
Self-assessment against all MEV standard requirements. Declares which components are implemented, which are in progress, and which are planned. This is the file the MEV Foundation reviews during certification.
MEV Standard: v1 compliant
A × V implemented: ✓
Milestones (k×10ⁿ): ✓
Epoch NFT: ✓
OCEO Bridge: ✓
Diapause Phase I (S=0): ✓
Validators: Not in scope
Required: AboutMEV, MEVU,
MEVEpoch, MEVDiapause,
MEVMRSS, MEVCompliance
Recommended: All 10 files
Four steps from zero to MEV-compliant.
Clone or download the MEV Lite SDK from our public GitHub repository. Add the files to a /mev-sdk/ folder in your project root.
Complete each file with your system's specific implementation details — your MEVU form, milestone formula, Diapause phase (S=0 for Phase I), Oracle mode, and activity definitions.
Submit your completed MEVCompliance.md and Implementation Paper to the MEV Foundation for review. We will assess your compliance and issue your Registry ID if approved.
Receive your unique Registry ID, populate your MEVCertificate.md with it, and be listed on the MEV Global Registry at officialMEV.org.
View RegistryGet the MEV Lite SDK from GitHub, complete your files, and join the registry.