> 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/why-movement.md).

# Why Movement?

Limelight is built natively on **Movement** — a sovereign **Layer-1** blockchain (M1 Mainnet) in the Move ecosystem. Movement isn't just where Limelight is deployed; several of its properties are a genuinely good fit for a prediction market that handles real money. Here's why.

## Native USDCx Collateral

Limelight markets are collateralized in **USDCx**, the USDC-backed stablecoin issued **natively on Movement**, with reserves held transparently on-chain. Because the core collateral is a native, on-chain-backed stablecoin — not a third-party bridged wrapper — there's no external bridge risk sitting under every position. That's a concrete trust story for a platform where your stake is the product.

## On-Chain Price Resolution with Pyth

Price markets ("Will BTC be above $X at time T?") resolve against **Pyth** price feeds read **on-chain in the resolution transaction** — minimal manual adjudication, a verifiable value, and a clean settlement path. Pyth is a decentralized, first-party-sourced oracle **integrated on Movement** (not a built-in chain oracle), covering crypto, equities, FX, and commodities. See [Resolution Sources](/limelight-docs/for-creators/resolution-sources.md).

## Sub-Second Finality and Very Low Fees

Movement delivers **sub-second finality** through validator-based consensus, with gas costs of a fraction of a cent. Trades confirm almost instantly and cost almost nothing — exactly the snappy UX a fast-moving market needs.

## Move Language Safety

Movement runs the **Move** language (originated in Meta's Diem/Libra project, now in the Move ecosystem alongside Aptos and Sui). Move's resource-oriented model treats assets as resources that can't be accidentally copied or destroyed, which eliminates whole classes of smart-contract bugs common in older languages. **Move 2** language features are live from day one. For an app that holds and settles user funds, that safety model is a real advantage.

## A Sovereign Layer-1

Movement is a **sovereign L1**, not a rollup: it has **no centralized sequencer** and **no dependency on an external chain for security**. Consensus is validator-based, and — by design — only unlocked tokens earn staking rewards, so the community controls network security rather than insiders.

## Easy Funding

You don't have to already hold funds on Movement. The in-app deposit widget lets you **pay from almost any chain** and delivers USDCx to your Limelight balance in seconds. See [Wallets & Networks](/limelight-docs/knowledge-base/wallets-and-networks.md).

## What We Don't Claim

We try to be precise about Movement's capabilities:

* Pyth is an **integrated** oracle, not a native chain-level one.
* Movement has **no native randomness or native automation service** — any such features are explicit design choices, not chain primitives.
* Throughput figures we cite are real-world targets; theoretical ceilings are labeled as theoretical.

Limelight sells its technology and product — not any token or its price.


---

# 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/why-movement.md?ask=<question>&goal=<endgoal>
```

`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.