Gmgn

Gmgn pricing is a 1% trade fee plus SOL priority and tip costs

Gmgn pricing is a 1% handling fee on each trade, plus Solana network costs and any priority or private-node tip the trader selects. A 1 SOL order therefore carries a 0.01 SOL GMGN charge before gas, tip, pool fees, token-level fees, and execution price impact. The fixed percentage matters most on repeated trades; the fixed SOL additions matter most on small orders.

This cost brief separates each recipient, shows a transparent calculation, and explains which quote fields belong in an all-in comparison. It stays on pricing rather than repeating GMGN's broader trading and wallet features.

The four charges inside a Solana trade

GMGN's 1% handling fee, Solana's base fee, the chosen priority fee, and the private-node tip decide the visible cost before route-specific execution effects enter the quote. Each line has a different recipient and scaling rule.

GMGN handling fee

The GMGN handling component scales with notional rather than compute work. At 1 SOL, 1% produces 0.01 SOL; at 0.1 SOL, it produces 0.001 SOL. GMGN calculates the charge per completed transaction, so a buy and later sell create two fee events. WSOL is wrapped SOL for token-program use, and 1 WSOL unwraps to 1 SOL. That equivalence removes exchange-rate ambiguity from the fee line, although the swap's output value still moves with pool execution. It also makes SOL-denominated reconciliation straightforward. No conversion into another settlement asset is required.

Priority fee

The priority fee raises scheduling priority for the Solana transaction. GMGN exposes it as a SOL-denominated control, with a documented minimum of 0.0001 SOL. It goes to validators rather than GMGN, and its absolute value doesn't shrink with the trade amount. A small order therefore carries a higher effective percentage at the same setting.

Tip and base fee

The tip pays the private-node path GMGN uses for faster submission, and its documented minimum is also 0.0001 SOL. Solana separately charges a base fee per signature. One SOL contains 1,000,000,000 lamports, so the 5,000-lamport charge for one signature equals 0.000005 SOL before any priority fee.

At GMGN's documented minima, priority and tip already total 0.0002 SOL before the Solana base fee.

What does the 1% GMGN fee cover?

When a trade executes through GMGN, the 1% charge directly pays the platform for that single transaction and excludes network, node, venue, and token-level costs. It isn't a prepaid gas bundle or a guaranteed execution price.

Across most deployments, GMGN charges a 1% handling fee on each single transaction, so a 1 SOL transaction produces a 0.01 SOL platform charge. One percent equals 100 basis points, and one basis point equals 0.01%. A buy and sale at equal notional therefore produce platform fees equal to 2% of one leg's notional; if market value changes, compute each leg separately. This per-leg rule is the central arithmetic in Gmgn pricing. It's cleaner than subtracting wallet balances, which also reflect token output, network charges, and account balances.

Priority and tip controls before submission

When confirmation speed matters, GMGN's priority fee and tip settings raise the fixed SOL cost, so the chosen values need a ceiling before the order leaves the interface. Automatic values deserve the same review as manual ones.

Priority fee floor

Put another way, GMGN sets the manual priority input at a minimum of 0.0001 SOL. Solana's protocol-level compute-unit price has a default of 0 micro-lamports, which would produce a 0-lamport priority fee, but GMGN's trading interface applies its own execution controls. The platform minimum and the protocol default answer different questions.

Tip range and private routing

The tip is a separate GMGN control for private-node submission, including protected routes associated with Jito infrastructure on Solana. GMGN documents a 0.0001 SOL minimum, while its priority-and-tip control shows a 2 SOL maximum. That upper bound is a setting limit, not a sensible target. A tip pays the selected routing path; it doesn't reduce GMGN's 1%, the Solana base fee, or an AMM pool charge. When a preset moves upward, the entire increase lands as a fixed SOL addition.

Protected submission threshold

Crucially, GMGN's protected Anti-MEV submission requires at least 0.002 SOL in its documented priority setting, making that threshold material for small orders.

Failed execution and irreversible network cost

When a submitted Solana transaction reaches runtime but doesn't complete the swap, network charges still leave the fee payer, while GMGN's handling transfer requires successful on-chain instructions. A timeout label alone doesn't prove failure, so transaction status comes before balance arithmetic.

Solana charges 5,000 lamports per signature as its base fee, splits that amount 50% to burning and 50% to the block-producing validator, and sends 100% of the priority fee to the validator. The runtime deducts base and priority charges before execution, so a failed instruction doesn't reverse them. With one signature, the base portion is 0.000005 SOL because 1 SOL contains 1,000,000,000 lamports. Solscan shows the settled fee and instruction outcome in the transaction record.

A notional check on a 0.25 SOL order

For a hypothetical 0.25 SOL order, fixed fees become material enough to change the decision before pool charges and output-token mechanics appear in the final quote. Use one signature, a 0.0002 SOL priority fee, and a 0.0001 SOL tip.

The 1% GMGN component is 0.0025 SOL. Add 0.0002 SOL priority, 0.0001 SOL tip, and the 0.000005 SOL one-signature base fee; the visible total beyond notional becomes 0.002805 SOL. Dividing 0.002805 by the 0.25 SOL order gives 1.122%. That percentage still excludes any AMM fee, Token-2022 transfer fee, account creation balance, and execution price impact.

Raising only the priority setting from 0.0002 SOL to 0.001 SOL lifts the same total to 0.003605 SOL, or 1.442% of notional. The extra 0.0008 SOL buys a higher scheduling bid; it doesn't enlarge the order or offset the 1% platform component. That is why quote comparisons must preserve the same input amount and fee settings, ending at 1.442%.

Route comparison beyond the displayed fee

When two interfaces quote the same token pair and input, compare expected output, fixed network additions, platform charges, and wallet control before choosing the cheaper route. A lower headline percentage can still return less output through a weaker route.

Route comparison beyond the displayed fee side by side
Execution option Durable distinction Custody or control model
GMGN Trade with Wallet Connected-wallet execution without hosted automation External wallet reviews and approves
GMGN hosted wallet Automation and multi-wallet execution GMGN-hosted account with web withdrawal controls
Jupiter Swap Metis route construction across Solana liquidity User wallet signs the transaction
Raydium Swap Direct access to permissionless AMM contracts Non-custodial; user wallet retains control

Jupiter's Metis engine builds routes across Solana liquidity, while Raydium exposes direct AMM execution and may also supply liquidity inside an aggregated route. Phantom adds an in-wallet swap surface with its own preview and routing. Normalize each quote against GMGN by recording input, minimum or expected output, network additions, and platform charge at the same moment. After settlement, Solscan separates transaction fees from token balance changes, making it the clearest reconciliation tool. This method separates interface convenience from net execution value.

Pool, token, and account-level additions

When a GMGN quote touches an AMM pool or a token with extra rules, the all-in cost extends beyond GMGN, priority, tip, and base fees. Three mechanisms account for most remaining differences.

Pool fee and price impact

Raydium AMM v4 applies a 0.25% swap fee, equal to 25 basis points, on its standard route. Other Raydium pool types expose their configured tier, and Jupiter may split an order across several venues. The pool fee is a rule of the selected liquidity venue; price impact comes from the order changing the reserve ratio. GMGN's 1% sits above those execution economics. Compare expected output rather than adding a guessed universal pool percentage to every route.

Token-2022 transfer rules

The original SPL Token program doesn't impose a universal token transfer charge. Token-2022 adds an optional transfer-fee extension whose mint configuration stores both a basis-point rate and a maximum fee. A configuration update becomes active two epochs later. GMGN doesn't receive this amount, and a quote involving such a mint needs the token-level deduction included alongside the venue and platform components.

Account state and wrapped SOL

A classic SPL token account occupies 165 bytes, while Token-2022 accounts grow when extensions require extra state. Creating an Associated Token Account locks a rent-exempt SOL balance; closing an eligible account returns its lamports to the chosen destination. That balance movement isn't a swap fee, even though it changes the wallet total during first and final interactions. WSOL uses nine decimal places and maintains a 1:1 relationship with native SOL inside the 165-byte token-account model.

How does Solana calculate the priority fee?

Solana calculates the priority fee from the requested compute-unit limit multiplied by the compute-unit price, rounded up after converting micro-lamports into lamports for the submitted transaction. The protocol divides the product by 1,000,000 micro-lamports per lamport. At a price of 0, priority cost is 0. Defaults allocate 200,000 compute units per non-built-in instruction and 3,000 per built-in instruction; a transaction tops out at 1,400,000. The requested limit, not actual work, sets the charge up to the 1,400,000-unit cap.

The all-in decision rule for small orders

When fixed SOL additions approach the 1% platform charge, the order is too small for percentage-only comparison, so evaluate expected output per SOL spent before submitting the transaction. With one signature, GMGN's 0.0001 SOL priority minimum, 0.0001 SOL tip minimum, and 0.000005 SOL base fee total 0.000205 SOL. That fixed amount equals 1% of a 0.0205 SOL order, giving a concrete crossover at 0.0205 SOL.

Questions and answers about Gmgn pricing

Does GMGN copy trading charge once per strategy or once per filled trade?

GMGN copy trading applies costs to each triggered transaction, not once to the strategy as a whole. Every completed copy buy or sell carries the 1% handling fee, while each submitted attempt has its own Solana and priority costs. Several fills therefore repeat percentage and fixed components. Set the buy size and fee ceiling together before enabling repeated triggers.

When does a GMGN limit order start consuming SOL fees?

A waiting GMGN limit order begins consuming Solana transaction fees only after its condition triggers and a transaction is submitted on-chain. An order sitting untriggered isn't an executed swap. Once submission occurs, base and priority charges apply even if runtime execution fails, and a private-node tip follows the selected route. The 1% GMGN handling charge belongs to a completed trade, so separate waiting, submission, and execution when reconciling costs. This distinction matters when several orders remain open for hours.

Can a custom RPC eliminate GMGN priority and tip charges?

Using a custom RPC doesn't remove GMGN's configured priority and tip inputs. GMGN treats the custom endpoint as a backup route and applies priority and tip at the same selected rate. RPC choice changes forwarding, not the platform's 1% calculation. Compare the settled record so parallel submissions aren't mistaken for separate completed trades. Review both fields before signing the transaction.

Why might one GMGN trade show more than 5,000 lamports in base fees?

A GMGN transaction can show more than 5,000 lamports of base fees when its message includes more than one chargeable signature. Solana prices the base component per signature, including Ed25519 and Secp256k1 signature-verification precompiles, rather than per interface click. The 1% GMGN handling calculation remains separate. Use the message's signature count and fee field instead of assuming every swap carries exactly one 5,000-lamport base charge.