> For the complete documentation index, see [llms.txt](https://lumagg.gitbook.io/lumagg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumagg.gitbook.io/lumagg/on-chain-products/limit-dca-keeper.md).

# Limit/DCA Keeper

`lumagg-limit-keeper` is a permissionless operator for the `order-escrow` contract. It watches limit and DCA events, asks LumAgg for quotes, and submits fills when the on-chain order conditions are satisfied.

It is currently supported on **testnet only**. Do not use the testnet escrow, aggregator, or token IDs on mainnet.

## Configuration

The preferred startup mode uses TOML. The signing secret is kept in a separate file and is never committed with the configuration:

```bash
cp lumagg-limit-keeper.toml keeper.toml
chmod 600 keeper.toml
printf '%s\n' 'S...' > keeper.secret
chmod 600 keeper.secret
```

Set `network = "testnet"`, the deployed contract IDs, `quote_api_url`, and:

```toml
secret_file = "./keeper.secret"
dry_run = true
```

Run a dry-run first:

```bash
./lumagg-limit-keeper --config ./keeper.toml
# Validate only, without connecting to the network:
./lumagg-limit-keeper --config ./keeper.toml --check-config
```

For live testnet fills, set `dry_run = false`. The keeper requires an XLM-funded signer for transaction fees. `reclaim = true` enables permissionless reclaim transactions after expiry: Limit orders use `reclaim_expired`, while DCA orders use `reclaim_expired_dca`.

The old `KEEPER_*` environment-variable interface remains available for the existing testnet deployment scripts.

## systemd example

```bash
sudo install -m 0755 lumagg-limit-keeper /usr/local/bin/lumagg-limit-keeper
sudo install -d -m 0750 /etc/lumagg
sudo install -m 0640 keeper.toml /etc/lumagg/limit-keeper.toml
sudo install -m 0600 keeper.secret /etc/lumagg/limit-keeper.secret
sudo install -m 0644 lumagg-limit-keeper.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now lumagg-limit-keeper
```

The service is only a process-manager example. The binary can also run under a container, supervisor, or another service manager.

## Safety boundary

* Keep the keeper signer separate from user wallets and escrow funds.
* Start with `dry_run = true` after every contract or API change.
* Use a private or capacity-controlled Soroban RPC for live operation.
* Monitor submitted fills and verify the escrow balance and order status.
* Run a contract audit before any mainnet deployment.


---

# 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://lumagg.gitbook.io/lumagg/on-chain-products/limit-dca-keeper.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.