> For the complete documentation index, see [llms.txt](https://rico-token.gitbook.io/rico/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rico-token.gitbook.io/rico/page-6-rico-quantima-core-trading-strategies.md).

# 📈 Page 6: Rico Quantima Core Trading Strategies

## 📈 6. Rico Quantima Core Trading Strategies

The Rico Quantima trading software architecture accommodates five core mathematical trading models depending on changing volatility frameworks:

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

#### The 5 Core Trading Strategies

* 1\. Breakout Strategy (Chasing Momentum): \
  The system continuously watches key technical "ceilings" (resistance) and "floors" (support). The exact microsecond a coin breaks through a major price ceiling on high trading volume, the engine instantly enters the trade to ride the rapid upward surge.<br>
* 2\. Trend Following (Riding the Wave): \
  The engine uses math formulas—like dynamic Exponential Moving Averages (EMA) and Fibonacci levels—to spot long-term, sustained market trends. It safely buys into a rising trend and holds onto the position to maximize your returns, only selling when code mathematically confirms the trend has flipped.<br>
* 3\. Mean Reversion (The Rubber Band): \
  This strategy is built on a proven statistical fact: asset prices can only stretch so far before they snap back to their historical average price. The system automatically sells short when a coin's price peaks too high, and buys long when it drops into an oversold valley, profiting as the price corrects back to normal.<br>
* 4\. Scalping Engine (Micro-Profits): \
  Built for hyper-fast, sub-minute trading loops. Instead of waiting hours for a big price move, this engine buys and sells in a matter of seconds, capturing dozens of tiny price fluctuations throughout the day to safely stack up consistent, fractional gains.

#### 5. 🎯 Swing Trading (Capturing Bigger Moves)

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

Built for bigger-picture market tracking over longer multi-day or multi-week timeframes.

* Captures Major Shifts:\
  Instead of worrying about tiny minute-to-minute price movements, this strategy focuses on catching large, structural market swings and momentum shifts.
* Protects Your Capital: \
  The system utilizes smart trailing stops—an automated risk management tool that moves your exit point higher as the price climbs—to lock in your profits and protect your trading balance if the market suddenly turns around.

***

### 🪙 6.4 The Role of the $RICO Token on This Page

Across all 5 automated trading strategies, `$RICO` serves as the underlying **Execution Settlement Utility**:

* **Performance-Linked Demands:** Because different trading strategies generate varying transaction frequencies—ranging from high-speed loops in the Scalping Engine to macro metrics in Swing Trading—the computational resources required fluctuate dynamically.
* **Programmatic Utility:** The platform standardizes these operating metrics by pricing all execution logic, real-time cloud data streams, and script triggers strictly in `$RICO` micro-deductions directly from the user's Gas Tank.


---

# 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://rico-token.gitbook.io/rico/page-6-rico-quantima-core-trading-strategies.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.