> For the complete documentation index, see [llms.txt](https://docs.world.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.world.inc/venue/known-problems.md). # Known Problems Find the full list here: World Markets is a brand new protocol, built entirely from scratch. It is launching in Beta given the inherent risks of this endeavor. Here are some known problems which are are improving in the immediate future: 1. The front end may be buggy for some users. We recommend using it with Chrome and Brave. 2. Historical data, such as trade and order history may not show up on the UI. The chart can sometimes be inaccurate. The reason is because the protocol operates fully onchain, historical data is hard to access. Solving this is a priority. 3. It's hard to use with Python. We are working on a docker container which can be run locally and expose Binance-like APIs making it easy to use World Markets with any language. This is a priority. 4. Portfolio and Points program pages, including historical PnL for the account. Coming soon. 5. My ETH bags keep going to 0. This has nothing to do with World Markets, it appears to be a universal phenomenon across all ETH holders. --- # 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://docs.world.inc/venue/known-problems.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.