Live web, not a resolution source
Validators fetch public pages at deadline. The claim is a proposition, not a script. Jailbreaks fail closed to Unverifiable.
Intelligent contract · GenLayer
The rumor court for the live web.
Write what just happened in plain language. Stake native GEN. Validator nodes fetch the page, reach consensus, and pay the early correct side.
Why a court, not a market
Prediction markets freeze the future. Scuttlebutt tries the present.
Earlier correct stakes earn more
Time-decay weighting: amount × (resolved − stake time + 1). The losing pool is split by that weight. Dust stays on-chain.
No owner. No force-resolve.
Anyone can trigger resolution after the deadline. Flags record dissent. GenLayer finality is never reversed.
| Classic market | Scuttlebutt |
|---|---|
| Rigid, pre-declared resolution source | Validators read the live web |
| Binary yes / no | TRUE, FALSE, or UNVERIFIABLE |
| Same payout regardless of timing | Earlier correct stakes weigh more |
| Admin or oracle backdoor | Trustless — Equivalence Principle only |
How the court works
Four moves, then the wire goes quiet.
01
Post a claim
Write something happening now in plain language. Set a deadline. Put GEN on TRUE or FALSE.
02
Stake a side
Anyone can back TRUE or FALSE while the claim is open. Earlier correct stakes weigh more.
03
Validators research
After the deadline, anyone can trigger resolution. Leader nodes fetch the live web and an LLM; others agree via the Equivalence Principle.
04
Time-decay payout
Winners recoup their stake plus a share of the losing pool. Unverifiable claims refund everyone. Flags record dissent without reversing finality.
Auditable payout
Time-decay, in integers.
remaining_i = resolved_at − stake_timestamp_i weight_i = amount_i × (remaining_i + 1) payout_i = amount_i + (weight_i × losing_pool) // total_winner_weight UNVERIFIABLE → every staker is refunded in full losing side → 0 dust → stays in the contract (no owner drain)
Weights are snapshotted at resolve. Withdraw is O(1) and replay-safe. Settlement always happens on-chain — the UI only previews.
Next
Built to keep going.
Categories, richer resolution receipts, and a public flag log are designed so they can land without rewriting the court.
RumorCourt · trustless Intelligent Contract · native GEN