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

# 6. Cadence strategy

Build or exit a position in many small, randomized trades without moving the price against yourself.

{% embed url="<https://drive.google.com/file/d/1CjfppXhTy9bSnK6iDlPDmfXd0lOkFP2y/preview>" %}

Buy 5,000 ADA of a small-cap token in one order, and you pay for it in price impact. Cadence breaks a large buy or sell into many small trades at randomized sizes and times, rotated across several wallets and spread over hours.

### What you'll learn

* When to use Cadence
* Setting buy and sell totals, trade sizes and duration
* Rotating trades across multiple wallets
* Reading the preview, schedule and safety guards

### When to use it

| Goal                      | How to set it                           |
| ------------------------- | --------------------------------------- |
| Accumulate a token        | Set ADA → Token higher than Token → ADA |
| Exit a position           | Set Token → ADA higher than ADA → Token |
| Keep your position steady | Set both totals about equal             |

### Create a Cadence strategy

1. Click **New Strategy** and choose **Cadence**.
2. Pick your trading pair and DEX.
3. Set **ADA → Token** (total to buy) and **Token → ADA** (total to sell).
4. Set the trade size range. The hint above it shows the size where fees stop eating into each trade.
5. Choose the duration: 12, 24, 48 or 72 hours.
6. Add up to five hot wallets. Trades rotate between them.
7. Check the **Performance Preview** and the required balance, then click **Deploy Strategy**.

### Performance preview

| Metric         | Meaning                                        |
| -------------- | ---------------------------------------------- |
| Total volume   | Everything bought and sold over the plan       |
| Est. fees      | Batcher, network, pool and Surge fees combined |
| Net ADA        | ADA you'll end up with or spend, after fees    |
| Est. trades    | How many trades the schedule will place        |
| Avg trade size | Average size per trade                         |
| Avg time/trade | Average gap between trades                     |

### While it runs

* **Schedule:** Surge splits the plan into trade windows with randomized orders
* **Live status:** a countdown to the next trade and your progress through the plan
* **Safety guards:** daily volume cap, buy and sell caps per day, and the trade size range
* **Trade log:** every fill, with its transaction link
* **Controls:** pause, edit the config, or reschedule any time

### Good to know

* **Keep the Surge tab open.** Cadence trades are signed in your browser. Turn on Keep display awake in Settings.
* **Fund with a buffer.** The required balance covers the whole plan, plus fees.
* **Smaller trades, lower impact.** Your trade size range matters more than the total.

### Next

[7. DCA strategy](/tutorials/7.-dca-strategy.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.surgecardano.com/tutorials/6.-cadence-strategy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.