How Are Markets Disputed

Disputes usually happen when:

• a data feed is unavailable or inconsistent at expiry

• an event becomes unclear (e.g., postponed/abandoned match)

• the market rules didn’t cover a rare scenario

In P2P oracle systems, disputes can involve bonding and onchain voting. Maiga uses a simpler bettor-protection approach: refund on data-quality disputes (for that market).

---

Maiga dispute policy (simple)

If there is a dispute due to data quality issues for a specific market, Maiga will:

✅ Refund all bettors for that specific market.

Refund means:

• your stake is returned

• no side is considered a winner

• market is marked Refunded / Invalid

---

What counts as a “data quality dispute”?

Examples:

• primary source was down at the exact timestamp

• primary and fallback sources disagree materially and rules don’t define tie-break

• upstream provider later confirms an error

• event outcome cannot be verified reliably under the written rules

This refund policy is designed to protect beginners. If the “data quality is broken,” nobody should lose money.

---

Ben’s dispute example (feed outage)

Ben trades a 15-min BTC close market.

At expiry:

• Binance feed is unavailable briefly due to API error

• Result: market is flagged for data-quality review → refund all bettors.