M2 · Quantum Glue v38 backtest — published 2026-05-10, frozen at market creation
Resolution spec: Quantum Glue v38 backtest ≥ 1500 / 1502 receipts
Market parameters
| Field | Value |
|---|---|
| marketId | 0xf829abee25adbd6b60e29d0aae4745efd89cec7d117e7cf0078f89d62b66eba4 |
| contract | 0x5586b67C77E22eFB1574db0234bacbd249395Aea (V2, Base 8453) |
| oracle | 0x6b477738f7f73471A54bD390e5741FbD79730069 (founder) |
| closesAt | 2026-05-25T02:37:30Z |
| resolvesAt | 2026-05-25T03:37:30Z |
| seed | 1 USDC (recoverable post-resolution via lpWithdraw) |
Resolution rule
Outcome resolves to YES if the Quantum Glue v38 backtest, executed exactly once during the 14-day window between market creation and resolvesAt, passes ≥ 1500 / 1502 receipts. Otherwise resolves to NO.
Backtest specification (frozen)
- Codebase: EpochCore Quantum Glue at commit
HEAD as of v37 backtest run (1495/1502) - Hardware: NVIDIA RTX 5090 (24GB, sm_120, Blackwell) + CUDA-Q 0.13.0 GPU primary, IBM Heron fallback for receipts requiring ≥28q
- Software: PyTorch 2.10.0+cu128, Qiskit 2.3.0, Aer 0.17.2, EpochCore
quantum_execution_service.pypinned at v37 state - Pipeline invocation:
python -m epochcore.quantum_glue.backtest --version v38 --receipts 1502 --seal-evidence - Pass criteria per receipt: published in
QuantumSwarms/epochcore-canonical/docs/quantum-glue-receipt-spec.mdat market creation - Receipts seal chain: predecessor seal v37 apex
1f27ef1cb8d9…must appear in the v38 manifest
Edge cases (frozen)
- If the backtest cannot complete within the window (hardware failure, dependency rot), outcome = Invalid
- If a receipt is partially passed (e.g. timeout-cancelled), it counts as failed
- If the backtest is run multiple times in the window, only the run sealed to the canonical repo first is authoritative
- If oracle (founder) fails to broadcast resolve within 24h of
resolvesAt, traders MAY dispute via on-chain Invalid flag
QED receipt contents
On resolve, a QED receipt PDF will be sealed to evidence/v21-v2-deploy/resolution-M2-<ts>.pdf with:
- The full backtest manifest (commit hash, hardware fingerprint, timestamps)
- Per-receipt pass/fail summary table
- Total: passed / failed / total
- D-KaP hybrid signature over the payload
- The Base mainnet resolution tx hash
Trader recourse
Same as M1: oracle commits to publishing the backtest manifest at least 12h before resolve broadcast, with a dispute window.