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

# DCA

DCA schedules recurring buys of a token at fixed SOL amounts and intervals.

## Access

The DCA engine and UI handlers exist (`handlers/dca_ui.py`, callback `dca_menu`), but there is **no main-menu button** in `menus.py` today. The backend still executes due orders from `dca_engine.py` when rows exist in the database.

If you operate a private fork, wire `dca_menu` to a keyboard row to expose the dashboard.

## Create order (when UI is reachable)

1. Enter token mint address
2. Set SOL amount per buy
3. Set interval in hours

## Dashboard

Lists active DCA orders with:

* Token symbol/mint
* Amount per execution
* Interval
* Cancel button

## Execution

`dca_engine.py` checks due orders and executes buys through the standard swap path. Failed buys are logged; the schedule continues unless cancelled.

## PnL interaction

DCA buys add to the **current position cycle** — they do not start a new cycle unless the position was fully closed. See [Analytics and PnL](/features/analytics-pnl.md).

## Limits

* Requires sufficient SOL balance at each execution
* Uses user's slippage and fee settings
* Does not auto-enable Trading Shield unless configured globally

## Related

* [Buy and sell execution](/features/buy-sell.md)
* [Pro Settings](/features/pro-settings.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 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.hipersnipe.com/features/dca.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.