> For the complete documentation index, see [llms.txt](https://limelight-1.gitbook.io/limelight-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limelight-1.gitbook.io/limelight-docs/knowledge-base/glossary.md). # Glossary A reference for the terms that show up across Limelight docs. * **Boosted Market** — A market flagged for 2× LP on the same fee. Triggered automatically by large seed liquidity ($500+) or by the team. See [Boosted Markets & Campaigns](/limelight-docs/knowledge-base/boosted-markets-and-campaigns.md). * **Creator Fee** — The 0–2% fee a market creator sets when launching a market. Paid per trade, goes directly to the creator. * **Dispute Bond** — Collateral posted when submitting a dispute during the challenge period. Returned if the dispute is approved, forfeited if rejected as frivolous. * **Dispute Period** — The 24–48 hour window after a market resolves during which any user can challenge the outcome by posting a dispute bond. * **Epoch** — A monthly cycle during which LP accumulate. At epoch close, the Points Reward Pool is distributed proportionally and LP resets to zero. * **Featured Market** — A higher-profile, event-driven market around elections, championships, or major announcements. Curated by the Limelight team. * **Judge Team** — The admin team plus verified users who review dispute submissions and either approve (outcome updates) or reject (outcome stands). * **Limelight Catalyst** — The badge that unlocks market creation. Earned either by creating a market during the first-month open window, or by completing the four Catalyst tasks. See [Limelight Catalyst](/limelight-docs/for-creators/limelight-catalyst.md). * **LP (Limelight Points)** — Non-transferable, off-chain reward-accounting units that track your contribution to platform activity and determine your share of the monthly Points Reward Pool. Earned at 1 LP per $1 of traded volume. Not a token. * **LS-LMSR** — Liquidity-Sensitive Logarithmic Market Scoring Rule. Limelight's pricing engine: an adaptive bonding curve where all outcomes share a single pool, depth scales with volume (`b = α·Q`), and the market maker's loss is bounded by the creator's seed. See [How Limelight Works](/limelight-docs/the-basics/how-limelight-works.md). * **MOVE** — Movement's native token, used for gas on the network. * **Movement** — A sovereign Move **Layer-1** blockchain (M1 Mainnet) in the Move ecosystem. Limelight is built natively on Movement. See [Why Movement?](/limelight-docs/knowledge-base/why-movement.md). * **MoveVM / Move** — The execution engine and resource-oriented smart-contract language (originated in Diem/Libra) that Movement runs. Move's design eliminates whole classes of common smart-contract bugs. * **Observation Window** — The time range during which a market's resolving event is measured. Defaults to creation → expiry. Pre-window data doesn't count unless the rules explicitly say so. * **Privy** — The authentication and wallet provider Limelight uses. Lets users sign in with Google, email, X, or a connected wallet, and provisions a wallet automatically. * **Pyth** — A decentralized, first-party-sourced oracle integrated on Movement. Limelight resolves price markets against Pyth feeds read on-chain. Pyth is integrated, not a native chain oracle. * **Points Reward Pool** — A monthly pool funded by 0.125% of all trading volume, distributed proportionally to LP holders at epoch close. * **Protocol Fee** — The 1% fee on every trade, split into Ecosystem Fund (0.50%), Treasury (0.25%), Points Reward Pool (0.125%), and Referral Reward Pool (0.125%). See [Fees and Limits](/limelight-docs/the-basics/fees-and-limits.md). * **Rebalance** *(coming soon)* — A creator-only action that swaps the shares received from your initial seed liquidity, after the market goes live. Routed through the LS-LMSR curve, so it has price impact like any trade. See [Rebalancing Your Market](/limelight-docs/for-creators/rebalancing.md). * **Recurring Markets** *(coming soon)* — Time-boxed prediction markets on observable variables that reset on a fixed cadence (5m/15m/1h/4h/1d), resolved via Pyth. See [Recurring Markets](/limelight-docs/knowledge-base/recurring-markets.md). * **Referral Reward Pool** — A pool funded by 0.125% of all trading volume, distributed per trade to referral uplines (Tier 1: 10%, Tier 2: 1%, Tier 3: 0.1%). * **Resolution** — The process of determining a market's final outcome once its observation window ends. Price markets resolve via Pyth; event markets resolve from external sources. * **Share** — A tradable unit that pays out approximately $1.00 if its outcome wins, $0.00 if it doesn't. Prices reflect estimated probability. Actual payouts can vary slightly above or below $1.00 in deep or skewed markets. * **Sharpest Caller** — Limelight's skill-based prediction competition across the World Cup knockout stage. Scored on profit with stake capped at $50 per market, so rank is decided by the quality of your calls, not bankroll. See [Sharpest Caller](/limelight-docs/competitions/sharpest-caller-world-cup.md). * **USDCx** — The native USDC-backed stablecoin issued on Movement, with on-chain reserves. Limelight's primary collateral. * **Void** — A resolution state where a market's rules can't produce a definitive outcome (event cancelled, source offline, result doesn't fit). All stakes are returned. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://limelight-1.gitbook.io/limelight-docs/knowledge-base/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.