> For the complete documentation index, see [llms.txt](https://docs.swaproyale.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swaproyale.com/contests/trading-rules.md).

# Trading Rules

How portfolio building works.

You start with $100,000 in virtual capital. You are limited to a set number of trades per contest to emphasize skill over speed. Once you hit the limit of trades, you cannot make further actions in said contest. You can buy or sell assets within the contests to gain or reduce exposure to your virtual portfolio. 

Depeneding on the theme of the contests, permitted assets allowed for trading in said contests are subject to change. Pay attention to what is permitted into each contest while signing up. 

You can also stay in cash if you choose to. Your virtual portfolio will remain as is if you do so. 

<figure><img src="/files/tKE59CRNiks2g9hBmpmo" alt=""><figcaption></figcaption></figure>


---

# 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.swaproyale.com/contests/trading-rules.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.