Prediction Market Dispute Resolution: Oracles & Edge Cases

Any prediction market has to settle cleanly once the event is over. Transport event contracts have an easier job than most, because the outcome comes from an official record and the thresholds are set in advance. Nobody needs to interpret anything. Edge cases still happen, though. Diversions, late records, arrivals right at the threshold and partial cancellations all test how a market settles.

Below are the edge cases that cause disputes in transport event contracts, how each is handled from the terms set at the open to the rare manual review, and how this differs from dispute resolution in general-purpose prediction markets.

Why Settlement Disputes Arise in Prediction Markets

A defined-outcome contract looks simple. The event happened or it didn’t, and the threshold was crossed or it wasn’t. In practice, most disputes fall into three groups.

Late records and sources that disagree. Official records update at different speeds. A flight can show as on time in one system and 14 minutes late in another because the two record different events, such as gate arrival and on-blocks. A ship that enters port waters and then waits at anchor before berthing causes the same problem, depending on which timestamp starts the clock.

Definitional boundaries. If a flight is diverted to another airport, does it settle Delayed or Cancelled? If a train terminates two stops early because of a track failure, does the replacement bus count as the measured service and settle Delayed? The market’s terms have to answer these questions before it opens. Making up an answer once the edge case happens is too late.

Cascading events. An 8-minute departure delay can grow into a 47-minute arrival delay and cross a 15-minute threshold. Whether the market measures push-back or arrival decides the outcome. Rules that look clear on paper show gaps once they meet real schedules on a disrupted network.

When Records Disagree

The hardest dispute is a record that contradicts another one, which is worse than a missing record. Two official accounts of the same arrival create a real ambiguity, and no rule settles it automatically. If the settlement design hasn’t decided in advance what happens in that case, it has to improvise after positions are open and traders have money on the answer.

Deciding in advance changes the question. Instead of “what do we do now?”, it becomes “which rule applies here?” That’s much easier to answer, and much harder to argue with afterwards.

How Oracles Work Elsewhere, and What Settles a Transport Market Instead

“Oracle” means different things in different places, and mixing them up confuses traders trying to judge settlement risk.

In general-purpose blockchain prediction markets, an oracle is usually a cryptoeconomic mechanism. A network of permissionless reporters submits answers, and those answers are aggregated, bonded and open to challenge during a dispute window. Polymarket uses UMA’s optimistic oracle, which relies on a bond-and-dispute escalation model. Augur used REP-token holder voting. Kleros uses a decentralised juror panel drawn from token holders, who must bond value to take part. In each case, people are paid to argue about the answer.

A transport market doesn’t need any of this. The event has already been recorded by the operator whose job is to record it. A GADUIN flight market settles on the destination airport’s published arrival time against its published schedule. A train market settles on the destination station’s published arrival record against the published timetable. A ship market settles on the destination port’s published arrival record against the arrival estimate locked when the market opened. There’s no reporter network, no vote and nothing to bond, because nobody is being asked a question.

How GADUIN settles flight delay contracts explains this in detail. The rule is written into the market before the first trade. It isn’t chosen after the event.

Two Ways to Answer the Same Question

If you’re weighing settlement risk, these are the differences that matter:

Dimension	Crypto oracle (UMA, Kleros, Augur)	A GADUIN transport market
Where the answer comes from	A permissionless reporter network	The operator’s own published record of the service
How a dispute is handled	Token-weighted voting or optimistic escalation	The market’s fixed terms applied to that record
Resolution timeline	Hours to days, because a dispute window is required	Automatic once the record is in; review time depends on the evidence if the record is unclear
Room for interpretation	Reporters interpreting evidence	A recorded time against a threshold fixed before the open
What an attacker would have to do	Sybil attacks, economic vote-buying	Falsify an operator’s own published record

Neither model is better in every case. Crypto oracles exist for events with no official record at all, like an election dispute or a claim about who said what. Transport is the opposite. The record exists and the operator publishes it, so the useful thing a market can do is commit in advance to using it.

The Terms Are Fixed Before the First Trade

What matters most in a transport market is when the settlement rule was decided. A market’s terms are fixed the moment it opens and can’t change afterwards. That covers the delay threshold, the scheduled time it’s measured against and the window a count is taken over.

This is why settlement can’t be argued with, and it’s also why it’s fast. Nobody can widen a threshold after a bad arrival, reinterpret a rule after the fact, or find a more convenient way to measure the same flight. The sentence you read before trading is the sentence that decides your position.

Edge Cases: What Happens When the Outcome Is Unclear

Most markets settle without any problem. The record shows a 47-minute arrival against a 15-minute threshold, the outcome is Delayed, and positions settle. Edge cases are rare, but people remember them, so they shape how much traders trust a venue.

The 15-Minute Threshold and Flight Diversions

The 15-minute threshold on flight markets comes from the industry. Airlines and airports use the same line when they report punctuality, so the recorded times behind operational reporting also decide the market. A flight market counts as delayed at more than 15 minutes late. A train market counts as delayed at 5 minutes or more. The two draw the line in different places, and each market’s question states which one it uses.

Two scenarios test the threshold:

Near-threshold arrival. Under a 15-minute rule, a flight that arrives 14 minutes late settles On time, and one that arrives 16 minutes late settles Delayed. That one-minute gap comes from the definition, so there’s nothing to interpret. Traders accepted that definition when they opened the position, and it was in the market’s title. Knowing it in advance lets you size your position around it.

Diversion. When a flight is diverted, the terms have to say what “arrival” means for a flight that didn’t reach its published destination. The deciding question is always the same: was the destination served in the end, and when? A flight that eventually reaches its published destination after the threshold is delayed. A flight that’s abandoned, with nothing operated onward, is cancelled.

Train and Vessel Ambiguities

Rail has its own edge cases, because of how networks are laid out:

Short-turn termination. A regional train stops two stations before its published destination because of a blockage, and a replacement bus gets passengers there 55 minutes after the timetabled arrival. The terms have to say whether the bus counts as the measured service, and within what window, before anyone can trade the market.

Partial route cancellation. A train is cancelled east of a junction but runs normally west of it. If a market covers arrival at a destination past the junction, its terms have to say whether the cancelled section makes the service cancelled for settlement, or whether only markets on that side are affected.

Ship markets use a different clock. The arrival estimate is locked when the market opens, and the outcome is measured against the destination port’s published arrival record. Two cases come up often:

Anchorage holding. A ship reaches port waters but waits at anchor because the port is congested. Whether the clock stops at the waypoint, at pilot boarding or at the berth has to be in the terms, so nobody argues about it afterwards.

Port closure. A port closes because of a storm or an official order. If no outcome can be established under the market’s terms, the market is voided and every position is refunded in full. It isn’t settled on a guess about what would have happened.

Cancelled vs Delayed: How the Line Is Drawn

Cancellations usually settle more cleanly than delays, but they have awkward cases too:

A flight listed as cancelled but re-operated under a different number with most of the original passengers aboard
A voyage cancelled after cargo was loaded, with the cargo transshipped to another service

Both are handled the same way: apply the market’s terms to the record. A cancellation is its own outcome. It’s never treated as a very long delay, and a service that never operated is cancelled whatever the operator arranged afterwards. No new rule is made up at settlement time. Preventing that is what the fixed terms are for.

GADUIN’s Resolution Path: From Record to Settlement

Settlement runs in two modes. Knowing both tells you what to expect and when.

How GADUIN settles contracts in USDT covers how money reaches your balance. This section covers the step before that: how the outcome is decided.

Automatic Settlement: The Default Path

By default, no person is involved at any point:

Trading closes, and the market waits for the record named in its terms
The recorded time, or the confirmed cancellation, is measured against the threshold fixed before the open
If the record is clear, the outcome is recorded and settlement runs
Each share of the outcome that happened pays $1.00, and every other share pays $0. The money goes to your balance with no claim, form or reviewer

That’s how almost every market settles. For more on how a GADUIN market is built, see GADUIN’s market structure explained.

When Settlement Pauses for Review

Settlement pauses in a few situations: the record is missing, the record is late, or two sources disagree about the same arrival.

When that happens, the market goes under review. No money moves and no position changes while the review is open. A person then resolves it using the same evidence and the same terms the market has had since it opened. They apply the rule and never override it. How long that takes depends on the evidence available, so there’s no fixed deadline. If no outcome can be established, the market is voided and every position is refunded in full.

That’s the only human involvement, and it’s deliberately limited. The reviewer doesn’t decide what seems fair or what the market “really meant”. They apply a sentence written before anyone traded to a record someone else produced. Everything else in settlement is arithmetic.

Who Decides an Outcome, and Who Cannot

In bilateral markets, one trader’s gain is another’s loss. Dispute mechanisms exist partly to handle challenges from the trader whose outcome didn’t happen. Transport markets settle differently.

Nobody Here Decides the Result

A GADUIN settlement has no referee, no adjuster and no discretion. The terms were fixed at the open, the record is the operator’s, and the outcome comes from putting the two together. A trader can’t appeal for a better interpretation because there’s nothing to interpret, and neither can GADUIN.

This has two effects. First, the losing side can’t hold up settlement with procedural objections, because the result applies the same way to every position on the same outcome. Second, everything depends on the terms being right before anyone trades. That’s why the terms are in the market’s title and never change.

Where GADUIN Operates, and What That Means for You

GADUIN is operated from Panama. It is not registered with, or licensed by, any securities or derivatives regulator, and it is not available to US persons or to residents of restricted jurisdictions. Access is blocked before account creation.

This matters for disputes. There’s no regulator-supervised exchange rulebook behind these outcomes and no formal arbitration panel to escalate to. What you get instead:

Terms published before the open. The threshold, the scheduled time it’s measured against and the window are all shown on the market.
A settlement that shows its working. A settled market shows the rule it was judged by and the times it was judged on.
A limited review. A person applies the same fixed terms. If no outcome can be established, the market is voided and everyone is refunded in full.

Weigh this before you choose where to trade, not after you’ve opened a position. It’s a different set of rights and a different timeline from a regulated venue.

What a Trader Can Check for Themselves

You should be able to rebuild any outcome yourself instead of taking it on trust. Here’s what lets you do that:

You can read the terms before you trade. Each market’s title states the service, the date and the rule that decides it. If you open a position without reading it, you’ve still accepted those terms.

A settled market shows how it was judged. It shows the rule it was decided by, the scheduled time and the recorded time. Those are the same three facts the settlement used.

The record comes from someone else. The arrival time that settles a flight market is the destination airport’s published time. GADUIN doesn’t generate it. It exists whether or not the market does, which is why it’s worth settling against.

The exception is limited. A review applies the market’s own terms and ends in either a settlement or a full refund. It isn’t an open-ended appeals process, and you can’t request one.

Edge cases still happen. These rules make them rarer, and what’s left is visible and can be checked, so nobody can rewrite it afterwards.

Precise Terms Are the Real Dispute Prevention

The best dispute resolution is terms precise enough that disputes rarely come up. That’s the part a venue controls most, so it’s a good thing to judge a venue on.

Name the measured moment. “Arrival time” isn’t a rule. “The destination airport’s published arrival time against its published schedule, delayed at more than 15 minutes late” is. Different systems record touchdown, on-blocks and gate-open as separate events, so the terms have to say which one counts.

Name the comparison. A threshold needs something to be measured against: a flight’s scheduled arrival, a train’s timetable, a ship’s arrival estimate locked at the open, or a count threshold fixed before the window began. Each has to be pinned down when the market opens.

Decide the edge cases in advance. Diversions, short-turn terminations, port closures and partial cancellations all need their handling written into the terms before the market opens. If the rule isn’t written down, someone has to make it up at settlement, which is the worst time to do it.

Tight terms mean reviews are rare. Loose terms mean reviews keep happening, and that hurts confidence more than any single bad outcome. For a venue that settles on real-world events, writing good terms is central to the job, and it’s a fair thing for you to judge one by.

Event contracts on transport delays are financial instruments, not compensation products. Trading involves risk of loss, including the full amount you put in. Past settlement outcomes do not predict future outcomes. This article is for informational purposes only and does not constitute financial advice. GADUIN is not available to US persons. See User Agreement and Terms.