ReaperSniperBotREAPER SNIPER BOT
HomeFeaturesReferralDocsBlog
Docs›DCA

Automation

DCA — Stop Guessing the Bottom

A fixed amount of SOL, at a fixed interval, repeated. Instead of betting everything on one entry you get the average of many — which is the honest answer when nobody can know where the bottom is.

Last updated: August 2026

What It Does

You pick three things — how much, how often, how many times. Reaper buys on that schedule and each buy lands at whatever the price happens to be.

0.1 SOL every hour, ten times, is 1 SOL spread over ten hours. If the token dips in hour three, that buy is cheaper. If it runs in hour eight, that one costs more. What you end up holding is an average instead of a single guess about timing.

Setting One Up

Open any token and tap 📅 DCA. Three screens, presets on each one, typing optional.

1

Interval

1m, 5m, 15m, 30m, 1h, 6h or 24h from the presets. ✏️ Custom takes minutes — anything from 1 to 10 080, which is a full week.

2

Amount per buy

0.05, 0.1, 0.25, 0.5, 1.0 or 2.0 SOL, or your own figure between 0.01 and 100. This is spent on every buy, so the total is this number times the count.

3

How many buys

5, 10, 20, 50, or ∞ Unlimited. Type your own number if you want something in between — 0 also means unlimited.

The summary shows the total SOL and how long the plan will run before you confirm:

◎ 0.1 SOL every 1h  ·  Count: 10  ·  Total: 1.000 SOL over 10h

Picking an Interval

The interval decides what kind of price movement you are averaging over. There is no correct answer, but there is a wrong one — an interval so short that all ten buys land at the same price.

IntervalSuits
1m – 15mA fresh launch you want exposure to without one large entry. Aggressive, and the plan finishes fast.
30m – 1hThe common choice. Enough spacing that the price actually moves between buys.
6h – 24hA position you are building over days rather than hours.
Custom, up to 7dLong accumulation on a token you already believe in.

What the Bot Tells You

You do not have to watch a DCA plan. It reports on itself.

A buy failed

You get the reason and a counter — will retry next interval (1/3). The plan keeps going; one failure changes nothing.

Three failures in a row

The plan pauses and tells you. Something is consistently wrong, and burning network fees into it would not help.

Not enough SOL

Pauses immediately, before spending anything. A plan that cannot afford its next buy stops rather than failing over and over.

Plan finished

A summary with the totals — 10 buys × 0.1 SOL = 1.00 SOL total. Nothing left running in the background.

Keeping It Funded

💡Each buy needs its amount plus about 0.01 SOL for network fees. Reaper checks before every single buy, and pauses the plan the moment the balance would not cover the next one — so an underfunded plan stops cleanly instead of failing repeatedly.

A paused plan is not resumed on its own. Top up, then create a new one — that way you decide whether the schedule still makes sense at the price it has reached.

The 0.7% fee comes out of the buy amount rather than being added on top: 0.1 SOL per buy means roughly 0.0993 SOL of tokens each time.

Watching Progress

/dca

Every active plan with its schedule and how far along it is:

📅 HeeHaw  |  0.1 SOL / 60min  |  3/10
SettingValue
Active plansUp to 5 at a time
Interval1 minute to 7 days
Amount per buy0.01 to 100 SOL
Buys per planAny number, or unlimited
SlippageYour Buy setting — ⚡ Auto by default, read fresh before each buy
CancellingOne tap per plan, from the same list
💡DCA and limit orders solve opposite problems. A limit order waits for one specific level. DCA stops waiting and averages instead. Nothing stops you running both on the same token — a DCA to build the position and a limit sell to take profit on it.
⚠️Averaging down does not turn a bad token into a good one. A plan that keeps buying something going to zero simply buys more of it. Set a count you would be comfortable losing in full, and consider a stop loss on the position it builds.