Roadmap
How the court grows.
Scuttlebutt is a product, not a one-off demo. This is the sequence we will actually ship against — honest about what is live versus sketched.
Now — rumor court v1
Shipped- Post a natural-language claim with a deadline and an opening stake
- Stake TRUE or FALSE while the claim is open; timestamps are amount-weighted
- Anyone triggers resolve after the deadline
- Leader fetches the live web (DuckDuckGo + Wikipedia), LLM verdict via prompt_comparative
- TRUE / FALSE / UNVERIFIABLE with stored justification
- Time-decay payout; UNVERIFIABLE refunds; replay-safe withdraw
- Public flag counter that never reverses finality
- Full GenLayer transaction lifecycle in the UI (sign → consensus → finalized)
Next — denser court
Designed, not built- Claim categories and tags (markets, civic, sports, local) as a first-class index
- Richer resolution UI once receipts expose leader research snippets and validator votes
- Optional second Equivalence Principle check: a source-grounded summary stored beside the verdict
- Flag reason string + public log (still no reversal)
- Deadline watch list in the activity page
Later — keep it used
Horizon- Lightweight notifications when a watched claim hits its deadline
- Appeal UX that records a challenge without pretending to reverse GenLayer finality
- Read-only indexer for faster pagination if claim volume outgrows on-chain list_claims
- Public testnet deployment beyond Studio, once Bradbury/Asimov wallets are common
Non-negotiables
- No admin, no owner, no force-resolve.
- Native GEN only — no custom token.
- Flags are transparency, not an override.
- Integer math on-chain is the settlement source of truth.
- New categories or EP checks should not require a rewrite of storage or payout.