HostNexFlow › Features › DCA Orders
DCA on Solana: the buy you don't have to time
A fixed SOL amount buys the token every N minutes for N buys — a schedule that runs server-side, with your device off and your emotions nowhere near the button.
Timing a memecoin is a coin flip wearing a strategy costume. Dollar-cost averaging trades the flip for a schedule: the same SOL amount buys the token every interval, so your entry becomes the average of a window instead of one lucky or unlucky print. On NexFlow a DCA order is a first-class resting order — set the amount, the interval, and the count once, and the engine does the buying.
What a DCA order actually is here
Three fields: how much SOL per buy, how many minutes between buys, and how many buys to run. The engine then fires each purchase through the same Jupiter-routed swap a manual buy would take — no special venue, no bundled mystery, just the same trade on a timer. The order book shows the schedule and the remaining count, and you can cancel the rest any time.
Why the schedule runs on the engine
A DCA that needs your phone awake isn't automation, it's a reminder. These orders live server-side against your account wallet — the buys execute at the interval whether you're asleep, on a plane, or deliberately not looking at the chart. That last part is the actual product: the strategy's whole point is removing the moment where you talk yourself out of the plan, and it can't work if it asks you first.
| Field | What it means | Example |
|---|---|---|
| Amount | SOL spent on each buy | 0.05 SOL per purchase |
| Interval | Minutes between buys | every 60 minutes |
| Count | Total buys in the schedule | 10 buys, then done |
What DCA is not: averaging down is still one asset's risk — spreading the entry does nothing about a token that goes to zero. Pick the token like the whole schedule depends on it, because it does: run the scanner first, and how much liquidity is enough is the read that decides if your size can ever come back out.
Scheduling buys on a token you haven't scanned?
A good schedule on a bad contract is a slow rug with your name on it. Scan first.
Frequently asked
How does DCA work on NexFlow?
Set a SOL amount per buy, the minutes between buys, and the total count — the engine then buys the token on that schedule through the same Jupiter-routed swap as a manual trade. The order book shows remaining buys and lets you cancel the rest.
Does the schedule run while I'm offline?
Yes — DCA orders are engine-watched server-side against your account wallet, so every buy fires on time with your device off. That is the point of the feature: the plan executes without asking you.
What does a DCA order cost?
The flat 1% platform fee applies to each executed buy — ten buys in a schedule each carry it, and buys after a cancel never happen. No extra fee for the automation itself.
Does DCA make a risky token safe?
No — it spreads your entry over time, which is a timing hedge, not a safety hedge. If the token rugs, every scheduled buy bought into it. Scan the contract first and size the schedule like one position.
Can I change or stop a running schedule?
Yes — the order book lists the schedule with its remaining count, and canceling stops every buy that hasn't fired yet.