Prediction Contract Agreement

0. Operator, notices, and implementation warning

This Prediction Contract Agreement is administered by PredictDuel, the current operator of PredictDuel.

Operational questions, settlement challenges, and ordinary contract-support requests should be raised through the platform support flow or by contacting legal@predictduel.com. Formal legal notices relating specifically to contract interpretation, enforcement, or dispute escalation may be sent to legal@predictduel.com.

The operator name and legal contact have been specified in this document. Before production publication, you should still replace the remaining jurisdictional placeholders, including governing law and forum details.

1. Scope and order of precedence

This agreement governs how PredictDuel creates, interprets, pauses, reviews, settles, corrects, voids, and cancels prediction contracts made available through markets, duels, bundles, community formats, APIs, and related product surfaces.

By creating, submitting, accepting, matching, holding, reviewing, or otherwise participating in a prediction contract, you agree to this agreement, the Terms of Service, and any applicable product-specific or market-specific rules incorporated by reference.

If there is a conflict, the following order of precedence applies unless mandatory law requires another result: explicit market-specific rules and structured market fields, then product-specific rules, then this Prediction Contract Agreement, and then the general Terms of Service.

• The market title, resolution criteria, close time, determination time, timezone, source hierarchy, and special clauses are part of the controlling contract record.
• Promotional copy, social posts, chat messages, informal moderator comments, AI summaries, and unlabeled examples do not override the controlling contract record.
• A shortened card preview or UI summary is informational only if it omits details that appear in the full market rules.

2. Core interpretive rules

Each prediction market is a defined proposition. YES means the written proposition resolves true under the contract rules. NO means the written proposition resolves false under the same contract rules.

Contracts are interpreted literally and objectively. Settlement is not based on what users hoped the market meant, what a creator later says they intended, or what a majority of traders expected.

If a contract cannot be resolved with confidence from the published wording and listed source hierarchy, the platform may pause review and cancel or void the market instead of forcing a speculative interpretation.

3. Minimum contract requirements

A market should not be launched unless the platform can state the core settlement mechanics with enough precision that a neutral third party could resolve the outcome from the written rules alone.

• The exact question or proposition being tested.
• The deadline, observation period, or event date that matters for resolution.
• The applicable timezone and any source-specific time convention that overrides ordinary clock time.
• The exact condition for a YES outcome.
• The exact condition for a NO outcome or the statement that all non-YES outcomes resolve NO.
• The primary resolution source and any fallback source or escalation path.
• Any special treatment for ties, pushes, non-occurrence, postponements, cancellations, partial completion, or revised official results.
• Whether early resolution is allowed and, if so, under what standard.

4. Contract formation and order handling

A prediction contract forms only when the platform accepts and records the relevant action under then-current product rules. Submission of an order, duel response, bundle action, or similar instruction does not by itself create a guaranteed contract, guaranteed fill, or guaranteed position size.

The platform may reject, delay, queue, rate-limit, partially execute, reverse, or cancel requested actions that are stale, technically invalid, duplicative, outside the permitted trading window, inconsistent with compliance controls, or unsafe for system integrity.

Displayed quotes, order-book data, implied probabilities, volumes, and settlement timers are operational data points, not promises that activity will remain available or executable on the same terms.

5. Time conventions and official clocks

Every contract should state the time standard that governs the market. If a market specifies a timezone, local standard-time convention, publication cutoff, certification event, or official-source clock, that convention controls over a user's device clock or local interpretation.

If the contract resolves based on what is true by a stated deadline, outcomes occurring after that deadline do not count unless the written rules expressly say otherwise.

If the listed source itself uses a specialized reporting convention, such as local standard time, official statistical dates, or publication batches released after midnight for a prior day, that source convention controls if the contract adopts that source.

6. Source hierarchy and evidence rules

Each market should identify the source or sources used for settlement. Sources are interpreted hierarchically. The first listed source controls unless it is unavailable, materially delayed, internally inconsistent, obviously erroneous, or otherwise unusable under the written rules.

If the primary source fails, the platform may use the next listed fallback source or a documented manual-review process consistent with the contract. Unlisted sources do not control simply because they are faster, more popular, or easier to access.

The platform may use unlisted materials only to confirm authenticity of a listed source, locate the relevant entry in a listed source, or investigate fraud, tampering, or source corruption. Those auxiliary materials do not by themselves change the answer if the contract names a controlling source.

• If official and unofficial reports conflict, the listed official source controls unless the contract explicitly says otherwise.
• If a source later publishes a correction or revision, the platform may wait for the final official publication or reopen review if the written rules, source structure, or integrity review make that necessary.
• If no listed source can answer the question cleanly and no lawful fallback exists, the market may be canceled or voided.

7. Clarifications, edits, and launch defects

The platform may correct obvious typographical, formatting, or link errors before trading or before any user is materially exposed to the market, provided the correction does not change the market's economic meaning.

After meaningful participation begins, material edits are strongly disfavored. If a drafting flaw, omitted rule, incorrect source, or other substantive problem would change how a reasonable trader understood the contract, the platform may halt the market and either cancel it or relist a corrected replacement rather than silently rewriting the original market.

A post-launch clarification may be published for genuine ambiguity only when the clarification is consistent with the most reasonable reading of the original written contract and does not unfairly disadvantage one side. If that standard is not met, cancellation or voiding may be used instead.

8. Market lifecycle states and trading restrictions

Markets may move through states such as draft, scheduled, open, restricted, halted, locked, pending resolution, under review, settled, canceled, voided, adjusted, and archived. The platform may also apply product-specific sub-states for compliance review, quality review, or incident handling.

The platform may restrict new activity before the close time, during data uncertainty, while investigating suspected abuse, when a duplicate or conflicting market exists, or when infrastructure, source, or compliance issues require intervention.

A market remaining visible or temporarily open does not itself signal that a particular outcome is likely to resolve. Operational state should not be treated as settlement guidance.

9. Resolution methodology

At settlement, the platform evaluates the written contract against the listed source hierarchy and applies the outcome mechanically. The contract question must be answered as written, not as users may have generalized it.

If the contract depends on a number, threshold, ranking, score, certification, or announcement, the platform will use the measurement, unit, ordering rule, or publication state called for by the contract. If the contract says 'official,' 'certified,' 'final,' or an equivalent term, the platform may wait for that level of publication even if preliminary data is available earlier.

The platform may keep an internal or external audit trail identifying the market, source consulted, relevant timestamp, supporting evidence location, operational events, and any reviewer notes that justify the final outcome or cancellation.

10. Early resolution, delayed resolution, and manual review

A market may resolve before the ordinary deadline only if the written contract expressly permits early resolution or if the relevant outcome becomes irreversible under the contract's stated standard.

Settlement may be delayed even after the underlying event appears complete if the contract requires official publication, final certification, source reconciliation, anti-abuse review, or another integrity step before a reliable outcome can be recorded.

Markets may be moved to manual review whenever automation cannot determine a clean result, source data is inconsistent, fraud or tampering is suspected, the market overlaps another contract in a contradictory way, or a system incident affects record confidence.

11. Cancellation, void, push, and neutral-outcome rules

Cancellation or voiding is an integrity tool, not a trading result. The platform may cancel or void a market when the written rules are materially ambiguous, the referenced event becomes unmeasurable, the source becomes permanently unusable, the contract duplicates or conflicts with another contract, the market contains a material launch error, or continued operation would create inconsistent treatment across users.

A push, neutral, or split outcome applies only if the market explicitly provides for that treatment or if mandatory operational correction rules require neutral treatment after a platform incident.

If a market is canceled, voided, pushed, or neutralized, the platform may reverse, refund, nullify, or otherwise restate affected records according to the product's ledger model and the outcome treatment announced for that market type. In practical terms, this means affected stakes, contract entries, or reserved balances may be returned or unwound rather than awarded to either side.

11A. No death-resolution and no violence-incentive rule

PredictDuel does not permit markets to resolve affirmatively on the death of a named person, a private individual, a public figure, or any identifiable victim. Markets must not be structured so that a death, killing, assassination, suicide, fatal injury, or other lethal event is the event that determines the winning side.

If an existing market would otherwise resolve based on the death of a person, or if the underlying event becomes death-dependent because of later real-world developments, the market may be halted and will resolve as a push or equivalent neutral outcome rather than YES or NO unless mandatory law requires a different treatment.

For a push or equivalent neutral outcome under this rule, PredictDuel may return stakes, unwind matched exposure, restate balances, or otherwise restore users to the applicable pre-settlement economic position under the product's ledger model.

• This rule applies even if death would appear to satisfy the literal wording of the market.
• Markets that incentivize violence, targeted physical harm, or celebratory speculation on human death may be refused, removed, canceled, or pushed at any stage.
• Nothing in this rule obligates PredictDuel to keep a market open merely because a non-lethal version of the question might have been permissible if written differently.

12. Postponements, reschedules, and non-occurrence

Postponement does not automatically resolve a market. The written contract controls whether a postponed event remains live, extends through a grace period, resolves NO, or is canceled if it does not occur within the required window.

If an event is moved outside the market's stated observation period and the contract does not supply a coherent default rule, the platform may cancel or void the market rather than infer a rule that was never written.

If the event never occurs, never becomes measurable, or is abandoned before a reliable official result exists, the market may resolve according to any express non-occurrence clause or may be canceled or voided.

13. Thresholds, ties, and measurement boundaries

The contract should specify whether threshold comparisons are inclusive or exclusive, how ties are treated, what level of precision applies, and whether rounding is allowed. Those written rules control settlement.

If a contract is silent on a measurement detail and the omission could materially change the result, the platform may determine that the market is defective and cancel or void it instead of adopting an arbitrary convention after trading.

Examples, illustrations, and hypothetical scenarios are not substitutes for an explicit boundary rule in the controlling contract text.

14. Administrative corrections and manifest error authority

The platform may correct clerical mistakes, display mistakes, duplicate processing, ledger mismatches, accidental duplicate markets, fraud-driven activity, or other manifest errors that affect contract administration or settlement integrity.

Corrections may include reversing an erroneous state transition, updating a wrong source reference, restoring an omitted audit record, reopening review, or correcting a settled outcome when clear error or legal obligation requires it.

The authoritative platform record, including the settlement state stored in the official ledger or database, controls over cached UI displays, stale notifications, screenshots, or third-party mirrors.

15. Disputes, challenge window, and settlement finality

If you believe a market was resolved incorrectly, you must raise the issue through support promptly with the market ID, account details, relevant timestamps, the specific rule you believe was misapplied, and any evidence that can be reconciled against the listed source hierarchy.

Unless a longer period is required by applicable law or a product-specific rule says otherwise, users should submit settlement challenges within seven calendar days after the result is published on the platform. Delayed complaints may limit the platform's ability to reconstruct context, preserve evidence, or provide relief.

Settlement is generally treated as final once recorded, but the platform retains the right to reopen or correct a market where there is clear error, source revision, fraud, abuse, operational incident, contradictory duplicate settlement, or legal obligation requiring intervention.

• A dispute should identify the exact contract term or source rule you believe was applied incorrectly.
• General dissatisfaction with the outcome, price movement, or strategic trading result is not by itself a valid basis to overturn settlement.

16. Integrity and prohibited conduct

Prediction markets depend on credible contract wording and credible settlement. You may not trade or otherwise participate in a way that undermines either.

• No wash trading, spoofing, collusion, market rigging, sham participation, or abusive automation.
• No falsifying, fabricating, suppressing, or selectively misrepresenting evidence used in settlement review.
• No creating or promoting deceptive market wording designed to exploit ambiguity or trap other users.
• No attempts to manipulate the referenced event, source publication, review process, or contract outcome.
• No circumvention of regional, sanctions, account, or product restrictions tied to contract participation.

16A. Restricted market subjects and safety-based refusals

PredictDuel may refuse, remove, suspend, cancel, or push markets that create disproportionate safety, ethics, privacy, manipulation, or legal risk even if a user believes the question could theoretically be written with objective resolution criteria.

Restricted or disfavored market subjects may include death, self-harm, criminal victimization, explicit threats, doxxing triggers, non-consensual sexual conduct, instructions for wrongdoing, or questions that could encourage targeted harassment or real-world harm.

The platform may also reject markets involving private-person conduct, intimate relationships, medical crises, or other highly sensitive facts where verifiability, privacy, consent, or abuse risk make the market unsuitable.

17. Product variants and current non-monetary status

PredictDuel may offer prediction activity through standard markets, duels, bundles, community proposals, simulations, and other formats. Product-specific execution, scoring, cancellation, or settlement details may differ by format, and the more specific product rule controls if it conflicts with a generic example or educational explanation.

The current PDT environment is a non-monetary gameplay and information product. Unless PredictDuel launches a separate product under separate terms, PDT contract units, points, XP, ranks, rewards, or related balances do not create a right to fiat, crypto, interest, redemption, custody protection, or withdrawal value.

17A. Current market types and category-specific rules

PredictDuel currently supports or contemplates category-specific markets and ideas including sports, politics, weather, entertainment, community markets, and price-direction ideas for stocks, crypto assets, and foreign exchange pairs. Each category may include additional source, timing, and invalidation rules in the market-specific record.

The following category principles apply unless a more specific market-level rule states otherwise and remains consistent with this agreement.

• Sports: outcomes ordinarily resolve from the officially recognized league, tournament organizer, or governing body. Postponements, abandonments, suspensions, overtime, extra time, penalty shootouts, stat corrections, and voided contests resolve only as stated in the written market rules.
• Politics: outcomes ordinarily depend on the office, election, certification, appointment, resignation, or official action described in the market text. Preliminary reporting, media projections, unofficial concessions, and rumors do not control if the market requires official certification, inauguration, swearing-in, or another final governmental act.
• Weather: outcomes ordinarily depend on the listed official weather source, station, report type, and reporting convention. Third-party weather apps, social posts, and screenshots do not control settlement unless they are expressly named as sources.
• Entertainment: outcomes ordinarily depend on the specific release, chart, award, broadcast, premiere, or official announcement identified in the market text. Pirated copies, leaks, fan compilations, or unsourced rumor accounts do not control.
• Community markets: user-submitted or community-style markets may be subject to stricter approval, editing, rejection, or cancellation standards because wording quality and manipulation risk can vary more than platform-authored markets.
• Stock price markets: resolution should specify the relevant symbol, venue or reference listing, comparison point, and observation time. Halts, delistings, corporate actions, ticker changes, and exchange irregularities may trigger delay, fallback review, or cancellation if the written rules do not already address them coherently.
• Crypto price markets: resolution should specify the asset symbol, quote currency, exchange or index source, and exact observation time. Forks, chain disruptions, exchange outages, unstable oracle prints, symbol remappings, or market fragmentation may require delay, fallback review, or cancellation under the written rules.
• FX price markets: resolution should specify the currency pair, pricing convention, and reference source or feed. Bank-holiday conditions, stale prints, extraordinary interventions, or unavailable reference quotes may require delay, fallback review, or cancellation if no reliable listed source is available.

18. Contract design standards applied by the platform

PredictDuel aims to approve or launch markets that satisfy baseline contract-design standards intended to reduce ambiguity and manipulation risk.

• Observable: a neutral third party can verify the answer from the listed source.
• Singular: the market tests one proposition rather than multiple hidden sub-conditions.
• Time-bounded: the relevant deadline, period, or certification event is explicit.
• Exhaustive: YES and NO cover the valid result space unless a written void or push path is included.
• Deterministic: the written source hierarchy and fallback policy produce one answer or a documented cancellation path.
• Manipulation-aware: the contract is not readily susceptible to settlement abuse, contradictory overlap, or avoidable source gamesmanship.

19. Governing framework and updates

Unless mandatory law requires otherwise, this agreement and contract-interpretation disputes will be assessed under the laws of [Insert governing law jurisdiction] and in the forum located in [Insert exclusive courts / forum jurisdiction].

The platform may revise this agreement to improve contract clarity, dispute handling, compliance posture, market integrity, or operational safety. The latest version will be published on the site with an updated effective date.

Continued use of the relevant product after an update becomes effective constitutes acceptance of the revised agreement, subject to any rights you have under mandatory law.

20. What users agree to when they enter a contract

• You agree that the written market rules and listed source hierarchy control the outcome.
• You agree that close times, lock windows, and review holds may be binding even if you disagree with the market direction.
• You agree that a defective or ambiguous market may be canceled or voided rather than reinterpreted in your favor.
• You agree that settlement may be delayed whenever source quality, fraud review, or operational integrity requires additional review.
• You agree that PredictDuel may maintain authoritative records and correct manifest errors even after a result is first displayed.