CLUE Prediction Markets Documentation
Updated: June 30, 2026
CLUE documentation is the canonical research and integration hub for a decentralized prediction markets protocol. It explains how on-chain prediction markets, event market mechanics, DAO governance, tokenomics, moderation and arbitration, and risk controls fit into one verifiable protocol architecture.
Use these materials for protocol research, technical review, operator planning, and infrastructure due diligence. The docs are written for builders, analysts, interface operators, governance participants, and teams evaluating prediction market platform mechanics without relying on hidden platform discretion.
Materials are informational only and do not provide legal, tax, trading, portfolio, or professional advice; they do not provide trading signals, participation recommendations, assured outcomes, or universal jurisdictional availability.
Documentation Snapshot
| Area | What it explains | Primary page |
|---|---|---|
| Prediction market protocol | Protocol positioning, market forecast use cases, decentralization model | Protocol overview |
| Market mechanics | Market creation, AMM pricing, outcomes, appeals, fee flow | Market mechanics |
| Token and incentives | Utility, distribution, burn, vesting, anti-concentration controls | Tokenomics |
| Governance | DAO voting, treasury control, proposal execution, activity weighting | Governance |
| Risk and compliance | Non-custodial boundaries, operator responsibilities, protocol risks | Risk model |
Main Sections
- Protocol: CLUE prediction markets protocol
- Market mechanics: AMM, LMSR, event market lifecycle, and resolution
- Economic model: fee split, market creator rewards, referral branch, burn lane
- Tokenomics: CLUE utility, distribution, vesting, DAO Treasury, deflation
- Legal: compliance perimeter and risk disclosure
Documentation FAQ
What is this documentation for? -> Protocol research and integration review
It describes CLUE as prediction markets infrastructure: market mechanics, token utility, governance, moderation, arbitration, risk controls, and operator boundaries.
Is CLUE documented as a centralized betting service? -> No, it is protocol infrastructure
The docs separate protocol execution from interface and operator responsibilities. Legal and compliance pages explain this boundary in detail.
Where should developers start? -> Market mechanics and governance
Start with Market Mechanics for lifecycle and AMM details, then review Governance and Risk Model.