Rules

How a case works.

Every rule below is enforced by the contract or the schema, not by policy. Where something is a governance decision rather than code, it says so.

What a case is

A case names one publicly observable event, one threshold, and one deadline. Participants take the GUILTY side if they think the event will happen before the deadline, or the INNOCENT side if they think it will not.

A GUILTY verdict means only that the stated event was observed in time. It is not a finding of misconduct. It says nothing about who controls an address, why they acted, or whether anything improper occurred. Cases target public addresses and contracts, never people.

A price case and a Hyperliquid account market read as a question, so their two sides are shown as YES and NO. YES is the same side on chain as GUILTY, and NO the same as INNOCENT: only the words differ, and only on those two kinds of case.

The rule cannot change

When a case is created, its rule is serialised into a canonical form and hashed. The pool contract is constructed with that hash and stores it immutably. Every parameter — target, threshold, deadline, fee split, challenge window — is fixed at that moment.

This means you can recompute the hash yourself from the published rule and prove the contract settled against the rule you were shown. The dossier does exactly that on every page load, and says so if they ever disagree.

What can settle a case

Only finalised on-chain data, or an official public record named in the rule itself.

Social posts, commentary, screenshots, wallet labels of uncertain provenance and news coverage of an event cannot settle a case. They may appear as evidence, which is context for readers, but evidence never decides an outcome on its own.

When the data needed is missing, stale, contradictory, or not yet final, no verdict is posted from it. The resolver waits and tries again; a case that cannot be measured at all is voided and every stake refunded, and so is a case that reaches its deadline with no verdict. Funds stay untouched throughout.

Pace: standard or lightning

Every case is opened at one of two paces. Standard is the wizard’s own choices: staking for 15 minutes to 7 days, counting after it for 15 minutes to 7 days, a challenge window of 1 to 72 hours, and a resolution deadline a day after counting stops.

Lightning fixes them for a fast question: staking for 15 minutes; counting for 15 minutes or 30 minutes after staking closes (30 minutes for a price case or a price threshold, whose move or average needs it); the shortest challenge window the case factory accepts, an hour at launch; and a resolution deadline 2 hours after counting stops. The verdict comes once the chain has finalized the last block counted, which on Robinhood Chain takes 14.5 to 21.5 minutes (measured 2026-09-29); the verifier confirms it about a minute later, and claims open when the window after it closes: at launch, about an hour and a half after staking closes. A crypto price case is settled on chain instead: YES the moment a Chainlink round reaches the target, claims an hour later; otherwise NO 10 minutes after counting stops, claims an hour after that.

The rule, the pool and the settlement are the ones every case uses. Nobody labels a case lightning: it is one when its pool’s own times say so, read back from the chain when it is published — staking and counting each at most 30 minutes, a challenge window of at most an hour, and the lightning deadline, which only a case that keeps to the switch’s settings may take.

It is offered on the questions the chain answers within minutes: Dev dump, Supply teleport, Liquidity heist, Liquidity rush, Bundler exodus, Pons graduation, Price threshold, Sniper dump, Stealth mint, Ownership renounced, Whale accumulation, Price move, Hyperliquid position. A liquidity case reads a Uniswap v2 pair or a Pons curve only, and a price case one of the crypto feeds (BTC, ETH, LINK, ENA, WBTC, cbBTC, LBTC). Stock Tokens, depegs, public records and the types with no evaluator stay at the standard pace.

If nobody takes the other side, everyone is refunded about a minute after staking closes, with no fee. The resolver posts every verdict itself, from day one, as soon as the last block counted is final, and the verifier re-runs the resolver’s evaluation through its own RPC: it confirms a verdict it reproduces exactly and disputes one it cannot. If no verdict lands by the deadline, or the verifier never confirms one, everyone is refunded. The backer vault never stakes on a lightning case.

A price case is measured from the feed’s last answer when staking closes, and a feed publishes only when the price moves half a percent from its last answer, so that starting answer can already be up to half a percent from the market. The stake panel of a lightning price case says how far, from Hyperliquid’s price, or says it cannot.

Price cases

A price case asks whether one price reaches a target after staking closes, judged by one Chainlink feed on Robinhood Chain and nothing else. Touch counts any answer the feed publishes in the window; close reads the last answer at or before the end. An answer exactly at the target counts. A percentage is measured from the last answer the feed published at or before the moment staking closed, so nothing public while staking was open is counted.

Three kinds. Crypto (BTC, ETH, LINK, ENA, WBTC, cbBTC, LBTC): up or down, a percentage or a fixed level, at least 1% away, because the feed publishes only on a 0.5% move or once a day. Depegs (USDC and USDT): down only, a whole-cent level from $0.50 to $0.99. USDG, the dollar every stake and payout is in, is never a price case. Stock Tokens (all 35 of Robinhood’s on Robinhood Chain): as crypto, priced as the share price times the token’s multiplier, which reinvests dividends and absorbs splits.

A feed must be the one preCrime’s registry lists, at its exact address, with its decimals and, for a Stock Token, Robinhood’s own token for that ticker. A case on any other address is refused before it exists.

A price case is void, and every stake refunded, if the feed leaves the registry, Chainlink changes its aggregator or its decimals inside the window, it answers zero, or a NO or a close would rest on a silence of more than 25 hours. A fixed-level touch whose level was already reached when staking closed is void too. A YES from an answer the feed published stands whatever came after it.

Stock Tokens publish on a 24-hour schedule: every weekday is one continuous session, from Sunday 20:00 to Friday 20:00 New York time, closed only at weekends and on full-day US market holidays from 20:00 the evening before. Silence is counted only while the market is open, under a calendar each case names in its own rule (today US_EQUITIES_24_5_V1), and keeps even if a later calendar replaces it. A new calendar, the 24/7 one included, is data released with the code, never an edit of one a case already uses.

A Stock Token case is also void if Robinhood pauses the token’s price or changes its multiplier by more than 1% inside the window, as it does for a split; if a change like that was staged before staking closed to take effect inside the window; if two consecutive answers are one and a half times apart; or if the feed publishes well inside a closure the calendar excused. These are read from the token contract and the feed on chain, never from an announcement.

Hyperliquid’s price is shown beside a crypto case, with a link, as context. It never settles anything: the feed and Hyperliquid can differ, and only the feed judges.

Hyperliquid account markets

An account market asks whether a public Hyperliquid account’s position on one side of one coin is liquidated (in whole or in part), liquidated to zero, or fully closed, after staking closes and by a stated time. A fill Hyperliquid marks as a liquidation of that account decides a liquidation; a fill that takes the position to zero or turns it around decides a close.

This is the one kind of case that does not settle from the chain or an official record. Hyperliquid’s API keeps no history anyone could re-read later, so preCrime records the account while it happens, with two recorders on separate hosts and transports, each storing every fill under Hyperliquid’s own identifiers. A verdict is posted only when both recordings agree; otherwise the case is void and everyone is refunded. The recording is published with the case, and its fingerprint is inside the report the verdict commits.

The account’s owner decides the outcome, and every account market says so above its stake panel. The owner may open one: the case is then marked “opened by the account's owner” everywhere it is shown, permanently. preCrime never prepares a stake from the account or any address Hyperliquid links to it, and lists any stake from them that reaches the pool anyway. An account that holds no position on the case’s side when staking closes voids the case, with no penalty to anyone.

How payouts work

The fee is 2.00% of the gross pool — both sides combined — and the contract caps it at 2%. The winning side receives the remainder, distributed pro rata by stake. A case is staked in USDG or in PRECRIME, and every share below is paid in the asset the case was staked in.

Because it is parimutuel, a winner’s principal is not returned separately; it is already inside their share. A participant on the winning side can still receive less than they staked if their side held almost the entire pool. The stake screen shows the implied payout before you sign.

Winning side: 98.00%
Treasury: 0.95%
Case creator: 0.35%
Burned, or the jar: 0.30%
Evidence reserve: 0.20%
Referral: 0.20%

When a case pays nothing

A case settles only when both sides were staked. If nobody staked on the side that turned out to be correct, or nobody staked against it, the case is void. Every participant is refunded their exact stake and no fee, burn, reserve or referral is taken — so if everyone agreed and was right, nobody is charged for it.

There was no genuine two-sided market, so the protocol performed no settlement worth charging for. The same applies to a case that reaches its deadline with no verdict.

Two machines, and one human lever

No single key moves money to a side, and no person picks a side no machine reached. A posted verdict is provisional until a second machine has it: the verifier, run on its own host with its own data provider, re-runs the resolver’s evaluation and confirms the verdict only if it reproduces the same side and the same report digest. Claims open at the later of the window chosen when the case was created (1 to 72 hours) and that confirmation. If the verifier has not confirmed 1 day after claims would have opened, the case voids and every stake is refunded in full with no fee. An “unresolvable” verdict is a proposal the verifier confirms too.

A crypto or dollar price case needs no verifier: its pool names a price settler, a contract with no owner and no keys, which accepts the Chainlink round that proves the outcome from anyone — the provers, the watchdog, or any staker from the case page. A TOUCH case is YES the moment a round reaches the target; with none proven by 10 minutes after the window ends, it is NO by the contract’s rule.

A person reviews a verdict only when the two machines disagree, or when the operator escalates it before it is due, with the reason published on chain in full. A review freezes claims and can end only on a refund, the verifier’s side, or the posted side when a machine posted it — never a side no machine reached, and never a flip of a verdict both machines agreed on. It has a deadline: 3 days at launch, fixed in each pool when it is created (the timelock may set 1 day to 30 days for new cases). Unruled by then, anyone may void the case, and every stake is refunded in full with no fee.

There is no bond to challenge a verdict and nothing to buy: anyone who sees a wrong verdict reports it on the case page, publicly, and the operators are paged. Claims unlock automatically once a confirmed verdict’s window passes. Nobody has to be online for that to happen.

Who can resolve

A case creator can never resolve their own case. Enforced by the contract.
A resolver holding a stake on either side of a case cannot post its verdict. Also enforced by the contract, not merely by policy.
The verifier can never answer a verdict it posted, a case it created, or a pool it holds a stake in. Each judge’s key holds one seat, once; seating one waits 48 hours in public at the timelock, and the operator can unseat one at once, which only ever leads to refunds.

Opening a case

Anyone can open a case by posting a creator bond. There is no allowlist: an address nobody has heard of pays the default bond and creates cases exactly like anyone else. Reputation earns a smaller bond and more concurrent cases, never permission.

The bond comes back four days after the case’s outcome — voided or settled — to the wallet that opened it. It is slashed, half burned and half paid as a bounty, only on one of five grounds, and only with the evidence each one names:

Duplicate: The case's rule hashes to the same commitment as an earlier case that was still open for stakes when this one was created. The earlier case is the original; the later one is the duplicate.
Malformed: No rule that hashes to the pool's commitment was published by the stake cutoff, so nobody could have known what the pool settles on.
Fabricated: The case cites evidence or a source that does not exist or does not say what the case claims, shown by an upheld report that links the source and what it actually says.
Materially misleading: The title or description describes an event the rule does not measure, so that a reader relying on it would stake on something other than what settles the case — or it presents a named person as having done wrong. Shown by an upheld report quoting both.
Unresolvable by the creator's own rule: The resolver declared the case unresolvable, on chain, for a reason the rule's author controlled: a wallet, pool or supply that held nothing when the case opened, a pool that does not exist or was never initialised, decimals that do not match the token, a contract with no owner to renounce, a launch whose sniping window had not closed when the case opened, or a window that ends before staking closed.

Never a ground: one side was never staked; the resolution deadline passed without a verdict; a verdict somebody disagrees with. An indexer or provider outage blocks the verdict, or at worst voids the case and refunds it — a failure on our side is not the creator’s fault.

A slash is a timelock proposal, so it is public for 48 hours before it can run: the case’s history shows the ground and the evidence from the moment it is proposed. The four-day hold on the bond is what lets a proposal made when the case ends arrive before the bond leaves.

The 22 case types

Every case uses one of these. There is no free-text condition, because a rule a resolver has to interpret is a rule that will eventually be disputed.

Exchange escape: Will this wallet move funds to an exchange after staking closes?
Dev dump: Will this wallet sell a large share of what it holds when staking closes?
Supply teleport: Will this wallet move a large share of total supply somewhere new?
Liquidity heist: Will this pool lose a large share of its liquidity?
Liquidity rush: Will this pool gain a large share of liquidity?
Bundler exodus: Will this group of wallets collectively sell down?
Cluster rotation: Will this group of wallets rotate from one asset into another?
Cluster migration: Will this group of wallets send funds to one destination?
Stock Token accumulation: Will tracked wallets accumulate a Stock Token?
Stock Token move: Will this Stock Token move by a set percentage?
Paired rotation: Will this token outperform a Stock Token by a set margin?
Congressional disclosurepublic record: Will a congressional disclosure matching these filters be published?
Issuer filingpublic record: Will an issuer filing matching these filters be published?
Attention spike: Will activity here exceed its recent baseline by a set multiple?
Pons graduation: Will this Pons launch graduate from its bonding curve?
Price threshold: Will this token's time-weighted price cross a set level?
Sniper dump: Will the wallets that sniped this launch sell down?
Stealth mint: Will new supply of this token be minted?
Ownership renounced: Will this contract's owner renounce it?
Whale accumulation: Will this wallet buy a large share of the supply?
Price move: Will this price reach a target after staking closes?
Hyperliquid position: Will this Hyperliquid account's position be liquidated or closed after staking closes?

Open a case How data is sourced Safety and reporting