About
A public record of who called it.
Crypto is full of people who say they saw something coming. Almost none of it is checkable. preCrime exists to make that claim falsifiable.
The idea
Someone opens a case: one publicly observable event, one threshold, one deadline. Other people take a side. When the deadline passes the chain settles it, and the record of who took which side — and what the odds were when they did — is permanent and public.
The interesting part is not the payout. It is that being early and against the consensus is worth more than being late and obvious, and that everyone can see which one you were.
What it refuses to be
A product like this could easily become an accusation engine. The design says no in several specific places, and those places are enforced in code rather than in a policy document:
- A case can only name an address, contract or pool. Never a person, and never a guess about who controls something.
- There is no free-text condition. Every case resolves from a number and a named source, because a rule someone has to interpret is a rule that gets argued about.
- A verdict is a measurement. GUILTY means an event was observed, and the product says so next to every verdict rather than in fine print.
- Social posts cannot settle anything. They may be evidence for readers; they never decide an outcome.
Where the money goes
2% of a settled pool, the most the contract allows. The winning side takes the rest. A case nobody took the other side of is void, and a void case is charged nothing at all — there was no market, so there is nothing to charge for.
Referrals are paid out of that fee, never out of anyone’s stake. There is one level and no reward for a signup on its own.
preCrime never holds funds. Every stake, claim and refund is a transaction you sign to a contract you can read.
State of the build
This is under construction, and the product says so rather than implying otherwise. Contracts are written and tested but not deployed or audited. Providers are configurable but may not be configured in the deployment you are looking at.
Wherever something is not connected, the page names the missing piece instead of showing an empty result that reads as calm. That distinction matters more than it sounds: an empty feed and a broken feed look identical unless someone says which it is.