> 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/developers/technical-overview.md).

# Technical Overview

Limelight is deployed on **Movement** (M1 Mainnet) with smart contracts written as **Move modules** (Aptos-dialect Move). Movement is a sovereign Move **Layer-1**, so Limelight uses Aptos-compatible REST APIs, SDKs, and tooling.

> **Note on code in this section.** The module names, function signatures, and snippets below are **illustrative** — they show the shape of the system, not a frozen, authoritative ABI. Request the current module addresses, entry-function signatures, and a Movement fullnode endpoint from the Limelight team before integrating.

## Architecture

* **Execution:** MoveVM with **BlockSTM** parallel execution.
* **Consensus & finality:** validator-based consensus with **sub-second finality**. No centralized sequencer; no dependency on an external chain for security.
* **Language:** Move (resource-oriented; **Move 2** features available). The resource model prevents whole classes of bugs (double-spends, reentrancy-style issues) by construction.
* **Collateral:** **USDCx**, the native USDC-backed stablecoin on Movement, represented as a fungible asset.
* **Gas:** **MOVE**.
* **Oracle layer:** **Pyth** price feeds, read on-chain via Move (pull-oracle pattern). See [Resolution Sources](/limelight-docs/for-creators/resolution-sources.md).
* **Deposits:** users fund in-app through an embedded deposit widget that accepts payments from almost any chain and delivers **USDCx** to their Limelight balance (typically in 10–20 seconds).

## Fee Routing Pipeline

On every trade, the 1% protocol fee is split on-chain:

```
protocolFee     = V × 0.01
toEcosystemFund = V × 0.005
toTreasury      = V × 0.0025
toPointsPool    = V × 0.00125   (accumulated per epoch)
toReferralPool  = V × 0.00125   (distributed per trade to uplines)
```

`V` is the trade value. The creator fee (0–2%) is applied separately and routed to the creator.

## Oracle and Data Layer

**Price markets** resolve against **Pyth** feeds. Pyth on Movement is a **pull oracle**: the resolver submits a fresh price update (paying a small update fee) and reads the price in the **same transaction**, so resolution binds to a verifiable on-chain value. Feed IDs come from Pyth's price-feed-ID list (no `0x` prefix on Aptos/Movement).

**Event markets** use the external sources named in each market's rules, with cryptographic attestation where available and dispute-based resolution as the backstop.

The resolver enforces each market's **observation window** — only data points timestamped between the market's start and end are considered. Pre-creation data is rejected by default, preventing historical prices from triggering false resolutions on threshold markets.


---

# 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/developers/technical-overview.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.