> For the complete documentation index, see [llms.txt](https://docs.origami.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origami.tech/v1.2.0.md).

# v1.2.0

* **Competition Hub — updated competitions experience:**\
  [The Competition Hub](https://app.origami.tech/competitions) has been updated to support the refreshed competitions flow. Upcoming competitions can now be displayed with a dedicated **Coming Soon** state, and the new **Competitive Index** has been introduced to provide users with a clearer view of competition performance and ranking context.
* **Competition Hub — improved filter behavior:**\
  Fixed an issue where selected filters could be reset after opening **My Competition**. This improves navigation across competition views and keeps the experience consistent for both logged-in and logged-out users.
* **Charts — improved trade history display:**\
  Fixed an issue where buy and sell history could be displayed incorrectly on TradingView charts. Trade markers should now appear more reliably when reviewing historical activity.
* **Competitions — price ticker support:**\
  Added support for assigning a price ticker to competitions, making competition setup more flexible and allowing competition data to be linked to the correct market symbol.


---

# 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.origami.tech/v1.2.0.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.