Is GMGN safe? What it holds, and what is unknown

Updated 3 October 2026 · by AtroX · Belphor Research · the data behind this guide

Whether GMGN is safe depends first on which wallet a trader uses with it, and GMGN's own pages describe two. As of October 2026, GMGN's blog says a browser wallet such as Phantom connected to GMGN keeps its keys with the user, while other sign-ins put funds in a GMGN-managed wallet whose private keys, by GMGN's wallet guide, cannot be exported, although its sniper-bot guide describes export. How GMGN stores those keys is not described on any GMGN page read for this guide.

Two ways to use GMGN, and who holds the key in each

GMGN's own pages describe two kinds of wallet. Which one a trader uses decides what GMGN holds.

Sources: GMGN's documentation pages on wallets and the multi-wallet system, and GMGN's blog of 18 June 2026, read 3 October 2026; the links are listed at the end.

What GMGN says about moving funds

GMGN's safety page states that GMGN does not perform any operations on a user's wallet and does not have the ability to transfer a user's balance. Its terms of service (last updated 2 October 2026) say GMGN is not the user's custodian and cannot initiate a transfer of assets in a user's own web3 wallets, and describe the Telegram bot as an interface to the user's own wallet created by GMGN, over whose keys the user retains control.

Those statements sit beside the documentation's own words for the same wallet: a custodial account whose private keys, by the wallet guide, cannot be exported, although the sniper-bot guide describes export. The pages use different words for one arrangement, and none of them describes where or how the keys of a GMGN-created wallet are kept, whether in secure hardware, split among parties or otherwise. That is the open question, and GMGN's pages do not answer it.

The controls GMGN documents

What GMGN's terms say

Subject to the exceptions stated in its terms and applicable law, GMGN describes a liability cap at the greater of $1,000 or the remedy a statute imposes, and its terms say GMGN is not liable for hacks, stolen digital assets or other attacks on a blockchain. The service is controlled and offered from the British Virgin Islands, disputes go to arbitration there, and GMGN may suspend or end a user's access for any reason in its discretion, in which case, the terms say, the user may still reach the wallet directly or through services GMGN does not host. Users in Afghanistan, Cuba, Iran, North Korea and Syria, or on sanctions lists, are excluded.

What is unknown

• How the private keys of GMGN-created wallets are stored. No GMGN page read for this guide describes it.
• Whether any third party has audited GMGN's wallet system. None is documented, and no insurance or user-protection fund is described.
• How a suspended user reaches a GMGN-created wallet whose key cannot be exported. The terms say such a user may still access the wallet directly or through other services; the pages do not say how.
• How complete the contract checks are. GMGN's documentation says its honeypot detection relies on third-party data sources such as GoPlus and that the checks are for reference only, without a promise of full accuracy.
• Past incidents. GMGN's own pages report none; that says nothing about reports elsewhere, which this guide did not assess.

What a user can check

The address in the browser and the bot's exact handle against GMGN's contact page, since lookalike bots exist and GMGN's documentation warns about them. That 2FA and a withdrawal whitelist are set before funds arrive. That the fee on the confirmation matches the 1% GMGN states. And that a sell route exists before buying, the test in how to spot a honeypot token. Above all, a wallet that a service generates and whose key cannot be exported works as a trading float: it holds only what the trader can afford to lose, the structure described in Solana wallet safety for traders.