> For the complete documentation index, see [llms.txt](https://polypoll.gitbook.io/polypoll-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polypoll.gitbook.io/polypoll-docs/protocol/g-lmsr.md).

# Paper LS-LSMR System

This docs page replaces the old pre-market graduation model.

## Current architecture

The paper backend mirrors the 2.5.2 prediction-market math while settling in points instead of money.

### The important parts

* **Wallets:** paper wallets tracked in Postgres
* **Markets:** offchain market records with binary or multi options
* **State:** price vectors, outstanding shares, fee pools, and liquidity settings
* **History:** price history captured after each trade
* **Claims:** winners claim POLL points after resolution

## Why this matters

Paper mode keeps the forecasting and trading experience:

* real price movement
* slippage
* positions
* settlement logic

without requiring:

* USDC
* gas
* onchain claim flows

## AI and paper markets

The paper creator assist endpoint can:

* research context
* generate options
* generate resolution criteria and background
* suggest topic tags
* return a relevant image URL

That means the create flow is much closer to a polished consumer prediction market workflow than the old contract-first docs describe.


---

# 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://polypoll.gitbook.io/polypoll-docs/protocol/g-lmsr.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.