Two different mechanisms are sold under the same three letters. One buys a fixed amount on a fixed schedule. The other adds to a losing position to pull its average price down. Knowing which one you are looking at is the whole decision.
Dollar cost averaging is buying a fixed amount of an asset at a fixed interval, regardless of the price. $100 every Friday. When the price is low that $100 buys more units, when it is high it buys fewer, and the average price you paid ends up somewhere between the highs and the lows.
The point of it is not returns. It is that the decision is made once, in advance, so you are not deciding whether this Friday is a good Friday. Two properties define it: the amount is fixed, and the trigger is the calendar.
Most of them place safety orders. You open a position, and the bot places additional buys at set percentages below your entry price — often with each one larger than the last. As the price falls, the bot buys more, and the average price of the open position comes down with it.
Vendor documentation describes this as handling moves against the position. The structure has an older name: averaging down, and when each order is scaled up from the one before it, a martingale. Neither property of dollar cost averaging survives — the amount is not fixed, and the trigger is not the calendar. The trigger is being wrong.
Because the two have opposite risk profiles, and the shared name hides which one you bought.
On a schedule, your exposure grows at a rate you set. A month of bad news costs you a month of contributions. With safety orders, exposure grows as a function of how far the trade has gone against you: the position gets larger precisely as it gets worse, and the worst case is a full ladder of increasingly large buys into an asset that keeps falling. That can work for a long time and then not work once.
This is not an argument that safety orders are wrong. Traders use them deliberately, sized against an account they are prepared to lose. It is an argument that a product should say which one it is.
Three questions settle it for any product on the market:
A third shape, and the one Trade Leopard is: the schedule decides when a buy is allowed, and a condition decides whether it happens. You set a budget and a pace — daily, weekly, monthly, whatever you choose. You set target weights across a basket of assets, summing to 100%, and each asset's share of the budget is its weight.
Then each asset has to clear a gate before its share is spent. Trade Leopard reads RSI on four timeframes — 1h, 2h, 4h and 1d — and you choose how many of the four have to be under your threshold. An asset that qualifies is bought. An asset that does not is skipped, and the money it did not spend rolls into the next period rather than being forced into something that is not weak.
There is no entry price anywhere in that. Nothing is being defended, no order is larger because a previous one lost money, and each asset can buy at most once per period — a limit that survives a restart, so a long slide cannot drain a period's budget into one falling coin.
It is different, and the trade-off is easy to state. Waiting for weakness means you buy at lower prices than a fixed schedule would in a choppy market, and it means you sit in cash through a market that only goes up. Trade Leopard makes no claim to outperform a plain schedule, and does not publish backtests suggesting it does. What it claims is that the rule is yours, visible, and the same every period.
Usually not. Dollar cost averaging is a fixed amount bought at a fixed interval regardless of price. Most crypto products marketed as DCA bots place safety orders instead: extra buys triggered at set percentages below your entry price, sized to lower the average cost of an open position. The trigger is the loss, not the calendar.
A safety order is an additional buy placed automatically when the price falls a set percentage below your entry. Its purpose is to reduce the average price of a position that is currently losing. Many bots scale each successive safety order larger than the last, so the position grows fastest when the trade is going worst.
Averaging down becomes a martingale when each successive order is larger than the one before it. The structure recovers small losses reliably and concentrates the risk into a rare, large one — the case where the price keeps falling and the ladder of orders is fully spent.
No. Trade Leopard has no entry price to defend and never sizes an order based on a loss. It splits a budget you set across target weights you set, and buys each asset's share on your schedule only when that asset clears an RSI gate you configure. Each asset buys at most once per period.
It carries into the next period. If three of your seven assets clear the gate this week, the other four keep their share and the unspent amount is added to next period's budget, so the cash accumulates for the next time an asset is genuinely weak.
Set your weights, your budget and the gate. It buys on your schedule at Kraken, OKX or Coinbase, using an API key that cannot withdraw. $15 a month, cancel anytime.