# GRU M1 Listing Validation **Last Updated:** 2026-01-31 **Document Version:** 1.0 **Status:** Active Documentation --- ## Purpose This document defines **acceptance gates and validation criteria** for GRU M1 compliant settlement instruments (cUSDC, cUSDT, cEURC, etc.) prior to and after listing on CoinMarketCap (CMC) and CoinGecko (CG). --- ## Hard Gates (Acceptance Criteria) | Metric | Threshold | Rationale | | ------ | --------- | --------- | | **Peg Deviation** | ≤ ±0.50% | Target price = 1.0000; variance band for operational tolerance | | **Recovery Time** | ≤ 24 hours | Time to return to peg band after stress event | | **Supply Reconciliation Error** | 0 | On-chain supply must match attested supply exactly | | **Unexplained Variance** | None | No unexplained supply changes; full audit trail | **Failure of any gate:** Corrective action required before listing or scaling. No exceptions. --- ## Pre-Listing Validation ### Dry-Run Requirements 1. **Dominance Simulation** — Complete S0–S5 scenarios; archive results 2. **Peg Stress-Test** — All P1–P6 tests pass per instrument 3. **Supply Check** — On-chain supply reconciled with attestation ### Documentation Requirements - Symbol registry table (frozen) - External classification matrix - Mint/burn policy - Reserve attestation summary - Peg maintenance memo **See:** [GRU M1 Master Implementation Plan](../gru-m1/GRU_M1_MASTER_IMPLEMENTATION_PLAN.md) --- ## Post-Listing Validation ### T+1 / T+7 / T+30 Checks | Checkpoint | Price | Supply | Category | Market Cap | | ---------- | ----- | ------ | -------- | ---------- | | T+1 | Correct | Correct | Stablecoin/Fiat-Pegged | Correct | | T+7 | Correct | Correct | Correct | Correct | | T+30 | Correct | Correct | Correct | Correct | ### Incident Triggers | Trigger | Action | | ------- | ------ | | Peg deviation > ±0.50% | Immediate disclosure; indexer communication | | Supply mismatch | Corrective data submission; pause if critical | | Misclassification | Corrective data submission to CMC/CG | **See:** [GRU M1 Listing Dry-Run Runbook](../runbooks/GRU_M1_LISTING_DRY_RUN_RUNBOOK.md) --- ## Compliance Cross-Reference This validation framework supports: - **Regulatory Compliance** — Auditable evidence for institutional, banking, and sovereign review - **Operational Compliance** — Runbooks, incident response, recovery procedures - **Financial Compliance** — Transaction logging, balance tracking, attestation **See:** [Compliance Tracking](COMPLIANCE_TRACKING.md) --- ## Related Documentation | Document | Path | | -------- | ---- | | GRU M1 Master Implementation Plan | [docs/gru-m1/GRU_M1_MASTER_IMPLEMENTATION_PLAN.md](../gru-m1/GRU_M1_MASTER_IMPLEMENTATION_PLAN.md) | | GRU M1 Listing Dry-Run Runbook | [docs/runbooks/GRU_M1_LISTING_DRY_RUN_RUNBOOK.md](../runbooks/GRU_M1_LISTING_DRY_RUN_RUNBOOK.md) | | Peg Stress-Test Worksheet | [docs/gru-m1/PEG_STRESS_TEST_WORKSHEET.md](../gru-m1/PEG_STRESS_TEST_WORKSHEET.md) | | GRU M1 Real-Data Dominance Addendum | [docs/gru-m1/GRU_M1_REAL_DATA_DOMINANCE_ADDENDUM.md](../gru-m1/GRU_M1_REAL_DATA_DOMINANCE_ADDENDUM.md) |