HostHostDeFi › Features › Limit Orders
Limit orders on Solana: your price, not the market's
A resting order that buys when the price falls to your line — or sells a slice of the position when it reaches your target — watched by the engine around the clock.
Chasing candles is the worst way to enter a token, and watching them is the worst way to spend an evening. A resting order states the trade once — buy this much when the price crosses that line — and lets the engine watch for the cross instead of you. On HostDeFi that's a first-class order type, not a workaround: buys below a trigger, sells above or below one, all denominated in the USD price the chain actually trades at.
Entry orders and exit orders, same trigger line
The order box takes two shapes. A limit buy names a SOL amount and a USD trigger — the engine fills it when the token's price falls below (or rises above) your line, whichever direction you set. A limit sell names a percentage of the position and the same trigger — which is exactly what a take-profit is when the line sits above you and a stop-loss when it sits below. Every sniper fill arms its TP/SL exits into this same order book automatically, so a position you sniped can close itself.
| Order | You set | The engine does |
|---|---|---|
| Limit buy | SOL amount + a USD price, below or above | Buys the moment the price crosses your line |
| Take-profit sell | % of the position + a trigger above | Sells that slice when the target prints |
| Stop-loss sell | % of the position + a trigger below | Exits before the candle finishes falling |
It fires with your tab closed
Orders live server-side against your account wallet, so the watch doesn't die when your laptop does — the engine keeps reading the price and submits the transaction when the line crosses. Two honest caps keep the book clean: ten open orders per account and a thirty-day self-expiry, so a stale order can't fire months later into a market that forgot why you placed it.
The honest limit: a trigger is not a guaranteed fill — the engine submits your trade when the price crosses, and on a thin token the fill can slip past the line or route differently than the mark that triggered it. Slippage and liquidity still apply at execution; slippage settings covers what that means on memecoin books.
Place an order on a token you haven't scanned?
A trigger price doesn't check the contract. Scan the mint first, then set the line.
Frequently asked
How do limit orders work on HostDeFi?
Set a USD trigger price and a direction — buy a fixed SOL amount when the price crosses, or sell a percentage of your position when it does. The engine watches the price server-side and submits the trade on the cross, whether or not you're online.
Do take-profit and stop-loss orders exist?
Yes — a limit sell set above where the price sits is a take-profit, and one set below is a stop-loss. Every sniper fill also arms its TP/SL exits into the same order book automatically.
Do resting orders run while I'm offline?
Yes — orders are engine-watched server-side against your account wallet, so they fire with your device off. Caps: ten open orders per account and a thirty-day self-expiry.
Is a trigger price a guaranteed fill?
No — the engine submits your trade when the price crosses the line, and the fill follows the route liquidity gives it. On thin books the fill can slip past the trigger; the fee only applies to trades that actually execute.
What does a limit order cost?
The same flat 1% platform fee as every other trade lane, applied on executed fills only — an order that never triggers costs nothing.