Gmgn
Gmgn limit orders activate buy and sell instructions at configured price thresholds
Gmgn limit orders activate token buy or sell instructions when a configured price condition is met. A dip buy waits for a lower price; take-profit and stop-loss sells respond to rises and falls, respectively. The trigger sets the activation condition, while quantity, price mode, slippage, and available liquidity affect execution. An accepted order can remain open before any trade occurs. Completion requires a confirmed successful transaction, so a chart reaching the threshold does not establish a completed purchase or sale.
Open orders, completed trades, and timeouts
An open limit order records a price condition and an intended token trade, with execution still dependent on the selected wallet and trading settings. On the web, the token detail page has an Orders tab for that token's orders. In the app, Assets contains an Order tab with a Limit view.
Order creation, transaction submission, and confirmation describe different states. A timeout while retrieving transaction status can occur even after an on-chain trade succeeds. Before replacing the instruction or placing another trade, inspect the transaction status and resulting token balance. If the original transaction failed, address its reported cause before retrying. Changing the slippage allowance cannot repair an insufficient token balance or restore removed liquidity.
Price direction and the trigger reference
Price-triggered orders distinguish buying a dip, buying a rise, taking profit, and cutting a loss. The agent interface labels these buy_low, buy_high, take_profit, and stop_loss. A stop-loss sell responds to a downward threshold, while a take-profit sell responds to an upward threshold. Before saving an order, match the price rule to its token, selected wallet, and buy or sell action.
Telegram manual limit orders accept a price or a positive or negative percentage change. Percentage inputs require a reference price, so review the displayed target when the market moves during setup. For web take-profit and stop-loss presets, the relationships are P × (1 + r) and P × (1 - r), respectively. Here P is the current price used by the preset, and r is the magnitude of the chosen percentage change expressed as a decimal fraction.
The agent CLI accepts exact and slippage price modes through --limit-price-mode and defaults to slippage. A trigger in slippage mode does not promise execution at that exact price. Review the saved price mode with the trigger, especially when a strict price boundary matters.
Sell quantity when holdings change
Fixed-amount and holdings-percentage sells determine how much exposure a price trigger should remove. A fixed-amount order stores a token quantity. The Solana Telegram bot converts a selected sell percentage into a fixed token quantity when the order is created. A web holdings-percentage limit sell calculates its quantity from the holdings present when it triggers. Additional purchases can therefore increase the quantity covered by that percentage. A transfer or another sale can reduce the holdings available to it.
Agent strategies express a related distinction through buy_amount and hold_amount. The former uses a fixed token amount stored when the strategy is created. The latter applies a fixed percentage to the position held at trigger time. Purchase-based exits can therefore cover a different quantity from exits based on later holdings. Confirm which balance supplies the percentage denominator before attaching additional exits.
Auto Sell presets calculate exits separately for each purchase, so repeated buys can leave several active sell instructions for one token.
Slippage, liquidity, and transaction spending
Slippage is an execution tolerance that can permit a worse outcome than the price displayed when an order activates. An on-chain swap can fail if its output falls below the permitted minimum. Wider tolerance allows more adverse movement; it does not create liquidity. Platform charges and network fees also reduce net proceeds. For agent strategy creation, Solana requires priority and tip fee settings, while BNB Smart Chain requires a gas-price setting. These settings affect transaction spending, so include them in the order's cost assessment, particularly when the trade itself is small.
The same trigger with two sell quantities
A fixed allocation and a share of later holdings can produce different exits at the same trigger. All figures and account changes in this example are hypothetical.
Start with 186 tokens and a take-profit trigger called T. A planned sale of 37% initially corresponds to 186 × 0.37 = 68.82 tokens. Compare a fixed order for 68.82 tokens with a holdings-percentage order for 37%. Both use T, and the selected token supports the decimal precision shown.
Before the trigger, an additional purchase raises holdings to 286 tokens. Assume no competing order changes that balance, and enough fee currency remains available. After successful full execution, the fixed order leaves 286 - 68.82 = 217.18 tokens. The percentage order sells 286 × 0.37 = 105.82 tokens and leaves 180.18 tokens.
Fees and execution price determine proceeds separately from these token counts. The trigger alone supplies no cash-profit figure.
The fixed alternative preserves the originally chosen sale quantity. The percentage alternative removes the same share of the balance present at the trigger. These outcomes apply only while the stated balance and execution assumptions hold. The completed transaction and remaining balance identify the actual sale. Choose the quantity basis that matches the intended allocation before creating the order.
Web, bot, and agent trading access
Limit-order access differs between the Solana bot workflow and authenticated agent trading across supported networks. The web Buy Dip workflow uses a bound Telegram trading wallet; the bot offers manual limit buys and sells. Agent trading also covers Solana, BNB Smart Chain, Base, and Ethereum. Its source-wallet address must match the API key's bound wallet. Agent trading requests require IPv4 and an IP address on the API key's whitelist. Wallet tracking supplies another address's activity information, without authorizing spending from that address.
Immediate purchases, attached exits, and cancellation
An immediate purchase with preset exits and a pending limit buy differ at entry. Solana Auto Trading buys at market price and configures take-profit or stop-loss rules. The agent smart_trade path requires a buy trigger below its open price reference and at least one subsequent take-profit or stop-loss condition. Its exit percentages use the position's open price as their reference. That path requires sell-side transaction settings for the exits. A standalone limit order fits a single price condition; an attached strategy fits a planned entry plus related exit rules.
A successful purchase can coexist with a failed attempt to attach its exits. The agent swap response contains a strategy identifier when exit-strategy creation succeeds. Review the open strategy record and its configured conditions. The agent interface supports cancelling a strategy by its order identifier. A changed entry or intended sale quantity calls for reviewing any instructions that remain open.
Gmgn limit orders - your questions answered
Does a failed limit-order transaction still incur network fees?
A transaction that reaches the blockchain and fails during execution can still consume network and priority fees. A submission rejected before reaching the chain represents a different failure state. The transaction record identifies which occurred. Repeatedly submitting an order without correcting its execution error can therefore add costs without completing the intended trade.
What credentials authorize an agent-created limit order?
Agent-created limit orders require an API key and the matching locally generated signing private key. This signing key belongs to the authentication key pair whose public key was registered for the API key. It is distinct from a blockchain wallet's private key. Keep signing credentials out of chats, logs, screenshots, and shared repositories.
Can I choose a limit sell price by dragging its chart line?
The web limit-sell setup displays an order price line that you can drag to choose the desired sell price. This control applies when creating the order. The quantity, slippage, and other execution settings still need their own review; moving the line does not define how much of the token holding the order covers.
How does trailing take-profit differ from a fixed-price limit sell?
Trailing take-profit activates when its profit threshold is reached and then waits for the configured drawdown from the highest price reached since activation. A fixed take-profit limit sell uses its saved price threshold as the sell trigger. Trailing behavior can follow further rises, although a reversal after activation can reduce the eventual exit price.