M1 · ibm_fez T2 — published 2026-05-10, frozen at market creation
Resolution spec: ibm_fez T2 > 130µs in next IBM Heron calibration cycle
Market parameters
| Field | Value |
|---|---|
| marketId | 0x5d43d39c988d91176e7b5d94f063d96f48fdc9e19e9820b91c681608957c722f |
| contract | 0x5586b67C77E22eFB1574db0234bacbd249395Aea (V2, Base 8453) |
| oracle | 0x6b477738f7f73471A54bD390e5741FbD79730069 (founder) |
| closesAt | 2026-05-18T02:37:30Z |
| resolvesAt | 2026-05-18T03:37:30Z |
| seed | 1 USDC (recoverable post-resolution via lpWithdraw) |
Resolution rule
Outcome resolves to YES if, at the IBM Quantum calibration tick on or before resolvesAt, the average T2 coherence time across the qubit subset listed below exceeds 130µs. Otherwise resolves to NO.
Data source (authoritative)
- Endpoint:
GET https://api.quantum.ibm.com/runtime/backends/ibm_fez/configuration+/properties(authenticated, IBM Quantum Network) - Field path:
properties.qubits[i].T2.valuein seconds (converted to µs by ×1e6) - Qubit subset (fixed at market creation, NOT changeable):
[Q12, Q34, Q67, Q89, Q103] - Aggregation: arithmetic mean across the 5 qubits
- Threshold: 130 (µs) strictly greater than
- Resolution timestamp: the closest IBM calibration tick at or before
resolvesAt; if none falls in window, the most recent calibration prior toresolvesAt
Edge cases (frozen)
- If
ibm_fezis decommissioned or unreachable beforeresolvesAt, outcome = Invalid (half-payout to both sides per V2 contract logic) - If IBM Quantum API returns calibration data missing one or more of the listed qubits, the remaining qubits are averaged (minimum 3 must be present)
- If fewer than 3 listed qubits have valid T2 readings, outcome = Invalid
- If oracle (founder) fails to broadcast resolve within 24h of
resolvesAt, traders MAY dispute via on-chain `Invalid` flag — see governance below
QED receipt contents
On resolve, a QED receipt PDF will be sealed to evidence/v21-v2-deploy/resolution-M1-<ts>.pdf and linked from this page. It will include:
- The exact IBM Quantum API response (full JSON payload)
- The calibration tick timestamp
- The per-qubit T2 readings used in the average
- The computed average
- D-KaP hybrid signature (Ed25519 + ML-DSA-65) over the payload, signed by
EPOCHCORE™_DKAP_CEO_28ED271DEE6D5C45 - The Base mainnet resolution tx hash
Trader recourse
This spec is the binding rule. The oracle (EpochCore) commits to publishing the resolution data at least 12 hours before the resolve tx is broadcast, with a dispute window for any trader to challenge the data interpretation. If the dispute is correct, resolution is reverted to Invalid.