REACTORTürkçe

18 facts

Prediction markets

18 facts about prediction markets from 1 Rialo source. Each one is the explanation Reactor shows after a question, followed by the exact line it rests on.

Test yourself on this topic in Atlas

How Rialo Secures Prediction Markets

A smart contract cannot read a news site or watch a Fed meeting, so an oracle has to import the real world fact that settles the market.

“a smart contract cannot read the Associated Press's website to know election outcomes, watch a Fed meeting to get the latest interest rate decision, or scan social media for product announcements. To settle predictions, the prediction market needs an oracle to report these facts.”

Because the security model favors quorum agreement, a reporter who posts a fresh value nobody else has risks being slashed, so everyone settles on the stalest honest value.

“the quorum of reporters will logically converge on the stalest (honest) value in the quorum. For time sensitive values, reporting a fresh value that is unavailable to others risks slashing or penalization.”

A successfully challenged reporter loses the bond: the challenger receives part of it and the remainder is burned.

“if someone successfully challenges, the original reporter loses their bond (part of it goes to the challenger while the rest is burned)”

Optimistic oracles push the source of truth upstream, so they need some other trusted party, often governance, to settle disputes.

“Optimistic oracles function only when there is another trusted source of information to reconcile disputes.”

In the fictional Prophecy Markets example, submissions can be challenged for one day; if nobody objects, the result is finalized and payouts run.

“The system opens a one-day dispute window for other participants to challenge the submission; if no one objects, the result is finalized, and payouts are executed.”

Knowing the lie will tank the market's reputation, Alice shorts the governance token and profits again when its price crashes.

“she opens a short position on Prophecy's governance token. When public confidence collapses, the token price crashes–giving her another windfall.”

An attack pays when the false outcome payout plus the short profit exceeds the loss on tokens the attacker still holds when the price crashes.

“We can express this condition informally as: (payout from false outcomes + short profit) > (token loss from crash)”

The simulation assumes a $500 million governance token, ten markets of $10 million each, 10% extractable per market and a 30% crash after an attack.

“Assume Prophecy's governance token has a market capitalization of $500 million. The protocol hosts ten active markets, each averaging $10 million in trading volume.”

The simulation assumes a 30% drop in the governance token after an integrity failure, not 50%.

“Suppose an attacker can extract 10% of each market's volume if they falsify outcomes, and the governance token typically drops 30% following an integrity failure.”

Even with 20% turnout the attack pays, so the post says Prophecy would need over 75% participation or much larger bonds, both impractical.

“To restore security, Prophecy would need far higher governance participation (> 75%) or larger bonds, both of which are impractical in real-world contexts.”

On Rialo the resolution is code pointing to a primary source such as nfl.com or federalreserve.gov, with no token vote or reporter quorum in between.

“the market's resolution is a line of code that can point to a source on the web, and trustlessly report the results”

The post suggests nfl.com for a championship market, federalreserve.gov for rates and weather.com or ipcc.ch for climate.

“that might be nfl.com ; for rates, federalreserve.gov ; for climate, weather.com or ipcc.ch.”

Each market points to its own primary source, and it is far less likely that unrelated institutions coordinate to lie at the same time.

“it becomes even less likely to imagine they're coordinating with weather.com and NFL.com to all do so at the same time. Thus, even if the prediction market chooses the wrong resolution source, failure in one domain does not cascade across unrelated domains.”

Every oracle gets its data from somewhere; Rialo makes that source explicit so there is no chain of middlemen passing the message along.

“Eliminating the middleman game of "Telephone". Every oracle gets its information from somewhere.”

Rialo can return the whole feed from a named publisher, so apps can compute their own medians or transforms without losing the extreme values.

“On Rialo, it's possible to return the full underlying data stream (e.g., a feed from a named publisher), not a median that prunes outliers.”

Rialo does not duplicate a proof of stake model at the oracle level; resolution pointers and results are finalized by the chain itself with no extra bonded quorum.

“Resolution pointers and results are finalized by the chain itself; there's no extra bonded reporter quorum to maintain.”

To fake an outcome an attacker would need to corrupt or censor several visible institutions, and Rialo's MCP design mitigates censorship at the routing layer.

“On Rialo, an MCP design mitigates censorship at the routing layer, and protocol stake provides economies of scale”

Rialo reframes oracle security from a correlated governance risk into independent, verifiable ties to the public record, so the question is about the source itself.

“how likely is this primary source to misstate its own facts, and for how long? That reframes oracle security from a correlated governance risk into a set of independent, verifiable ties to the public record”

Other topics