Gmgn is where a first Solana position starts with a funded wallet

From a funded wallet to a closed first position

The first Gmgn position follows one sequence: fund, identify, quote, buy, verify, sell, and withdraw.

The chosen wallet controls every state change. Deposit SOL to its Solana address, wait for the balance to appear, then search the exact token mint rather than a ticker alone. The token page must show an available pool and a manual Buy control. Enter the SOL input, inspect the expected token output, and submit. Once Solana confirms it, the Holding view should show the token units. The same wallet later supplies the Sell action and receives the SOL output. Withdrawal begins after that output appears.

1. Select Solana and make the intended trading wallet active.
2. Deposit SOL over the Solana network and confirm the balance.
3. Search the token mint and open its matching market page.
4. Choose manual Buy, enter the SOL amount, and review the quote.
5. Submit, then confirm the token units in Holding and Solscan.
6. Sell the intended fraction, confirm the SOL, and withdraw it.

Keep the first pass manual. Limit orders, copy trading, and automated strategies introduce separate state and aren't required to understand a single buy-to-sell cycle.

Each screen should name the same wallet and mint. If either changes, return to the selection step before signing another transaction, because a different address creates a separate on-chain position record.

The Solana wallet comes before the order

A first Gmgn order needs a selected Solana wallet with enough SOL to buy and complete later transactions.

Gmgn supports a Telegram wallet login and Phantom-based access, with the selected path determining the active trading account. A Solana public key is 32 bytes before base58 encoding, so the full displayed address matters. The multi-wallet manager lets an account create or import as many as 10 Solana wallets, yet a first position only needs one. Copy that active address for the deposit, choose Solana as the sending network, and leave part of the balance uncommitted for the eventual sell and withdrawal.

One SOL equals 1,000,000,000 lamports, giving native SOL nine decimal places of on-chain precision. A route may temporarily represent native SOL as Wrapped SOL, or WSOL, where 1 WSOL corresponds to 1 SOL. Deposit completion means the active Gmgn wallet shows spendable SOL; the reserve size changes with the later transactions the wallet must submit.

Which token market should a new Gmgn trader choose?

A first Gmgn trade should open the Solana token page matching the intended mint address and an available market route.

Use the full mint address in search because a ticker isn't a unique on-chain identifier. The resulting token page connects the chart, pool information, trading activity, and manual order panel to that mint. Raydium and Meteora are established Solana liquidity venues the page may identify for a market. A quote only exists when Gmgn finds an executable route through available liquidity, so a token appearing in search doesn't by itself establish a buyable market.

Solana defines two widely used token program families: the original SPL Token Program and Token-2022. A mint belongs to one program, and its token accounts follow that program's rules. Token-2022 extensions may change account size or transfer behavior, so route support belongs to the exact mint and pool, not to the ticker.

The manual buy is an exact-input swap

The manual Gmgn buy spends a chosen SOL amount and returns the token quantity produced by the selected route.

Next to that, Gmgn's Solana route format defines two swap modes, ExactIn and ExactOut, with ExactIn as the default. The first-position workflow uses ExactIn because the trader fixes the SOL input while the token output follows the quote. The underlying quote carries an expected output and a slippage-adjusted minimum. In basis-point notation, 100 basis points equal 1%, while 10,000 basis points equal 100%. Those units express the accepted boundary without changing the chosen SOL input.

Review the active wallet, input mint, output mint, SOL amount, quoted token amount, and route before pressing Buy. If the route refreshes, read the new output rather than relying on the previous preview. The signed transaction owns the final instruction set, and its confirmed balance owns the position.

What confirms the first buy on Gmgn?

A Gmgn buy is confirmed when Solana records the transaction and the selected wallet shows the resulting token balance.

The button response alone isn't the final record. Gmgn can show the transaction status and resulting holding, while the transaction signature opens the same event in Solscan. Solana RPC uses three commitment labels: processed, confirmed, and finalized. Processed means a node observed the transaction, confirmed adds cluster voting, and finalized places the block in the rooted ledger. For a first position, the signature, successful status, mint, token amount, and wallet address should agree across the terminal and explorer.

Solana accepts a recent blockhash while its age is no more than 150, which creates 151 valid hash positions because age starts at zero. A transaction has two top-level fields, signatures and a message; each Ed25519 signature occupies 64 bytes, the recent blockhash occupies 32 bytes, and the serialized transaction has a 1,232-byte maximum. When the interface times out, the signature status and token account determine whether the position exists.

The position lives in a Solana token account

The purchased asset appears in a token account associated with the selected Solana wallet and mint.

Native SOL sits in a System Program wallet, while an SPL asset uses a dedicated token account. An Associated Token Account derives deterministically from the wallet owner, mint, and token program. A base account under the original SPL Token Program occupies 165 bytes; Token-2022 extensions can require more space. Solana accounts expose five core fields: lamports, data, owner, executable, and rent epoch. These mechanics explain why the main wallet address and the displayed token balance refer to related, yet distinct, on-chain accounts.

By contrast, Gmgn's Holding view links those accounts into one position record with bought amount, sold amount, average cost, realized value, and unrealized value. Confirm the mint and raw token quantity before using profit figures. A zero token balance may leave the empty token account present until a separate close-account instruction returns its stored lamports.

One worked first-position example

A worked unit example shows how the quote, confirmed balance, and exit fraction fit together.

All five changing inputs in this worked example are hypothetical: a 1.00 SOL starting wallet, a 0.25 SOL buy input, a quote for 250,000 token units, a confirmed receipt of 245,000 units, and a 40% exit selection. The confirmed receipt equals 98% of the quote, a difference of 5,000 units or 2%. Selling 40% of 245,000 units submits 98,000 units and leaves 147,000 units in the position. Those are the concrete position results; the wallet's actual SOL output comes from the sale confirmation.

Use the actual Gmgn confirmation for the acquired balance, the actual Sell preview for the selected amount, and the transaction signature for the receipt. Token decimal precision controls display rounding, so calculations should start from the units the position records.

Selling the intended fraction

The Gmgn Sell action applies a selected fraction to the token balance in the active wallet.

Open the token page, confirm the active wallet and mint, switch to Sell, and choose the intended percentage or amount. The preview reverses the trade direction: token units become the input, and SOL becomes the expected output. In multi-wallet mode, a 50% instruction sells half of each selected wallet's position separately rather than pooling their balances. That distinction matters whenever the same mint sits in more than one managed wallet.

A 100% selection targets the complete displayed token balance, but the position closes only after Solana confirms the sale and Holding reaches zero. A partial sale keeps the remaining units visible and moves the sold portion into realized position data. The final balance follows the percentage applied to each selected wallet.

Where does SOL go after the sale?

After a successful sale, the output SOL returns to the same selected Gmgn Solana trading wallet. The route may handle native SOL as WSOL, whose value maps 1:1 to SOL, before the wallet view presents the spendable balance. Holding updates the sold units and realized value. If the signed quote names a different active wallet or output mint, the transaction follows those fields.

A clean withdrawal finishes the workflow

At the other end, Gmgn completes the exit when the website sends the chosen balance to a whitelisted Solana wallet.

For a Gmgn-managed wallet, withdrawals run through the website rather than directly inside the Telegram bot. Open Deposit/Withdraw on Solana, confirm the current main wallet, and select the recipient saved in the withdrawal whitelist. Google Authenticator supplies the account's two-factor verification setup. The recipient should be a Solana System Program wallet capable of holding native SOL, and the transfer network must remain Solana from submission through receipt.

In the simplest case, Gmgn applies a 3-hour wait after a withdrawal whitelist address is created or changed and a 24-hour hold after Google Authenticator is rebound. Plan the whitelist before selling when the balance needs to move on a schedule.

The Max control doesn't send the entire displayed balance because the on-chain wallet retains an operational minimum for account storage and transfer execution. Read the executable amount, active wallet, recipient, and network on the final screen, then submit. The outgoing signature confirms the withdrawal left the selected wallet, and the receiving wallet confirms arrival. The available amount changes with the active wallet and the transactions still required. The related mechanics are detailed in Gmgn understanding comparison use cases.