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

# Known Limitations

Current known limitations in the public testnet:

1. Testnet assets have no real-world value.
2. Market availability may change as testing continues.
3. Creator markets may be live in one lifecycle state while other trading modes are still pending readiness.
4. A graduated token may still be pending liquidity or oracle readiness before a perpetual market is available.
5. XP, badges, ranks, and achievement rules may change during testnet.
6. Perp analytics and historical market data may be expanded or corrected as indexing improves.
7. Contract addresses and parameters may change across testnet deployments.
8. Some creator, social, and profile flows may require refreshed wallet or social-login state.
9. Public documentation may lag fast-moving testnet changes.

If a UI state conflicts with a wallet prompt or transaction preview, review the wallet prompt carefully and do not sign transactions you do not understand.


---

# 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://perps.gitbook.io/perps./known-limitations.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.